-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
feat: 2.11 Sentry error integration cp-7.52.0 #17160
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
remove unwanted lint changes
- Added OnboardingSheet component for user onboarding options. - Integrated AccountStatus component to handle existing account scenarios. - Updated navigation routes to include new onboarding flows. - Enhanced ChoosePassword component to support OAuth login success handling. - Updated localization files to include new strings for onboarding and account status. - Added tests for new components and updated existing tests for integration. This commit enhances the user experience during onboarding and account management by providing clear options and feedback for existing users.
…nd Authentication components
…ion and restoration
…s onboarding behavior
parity with extension
|
|
|
|
|
hieu-w
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
|
Missing release label release-7.52.0 on PR. Adding release label release-7.52.0 on PR and removing other release labels(release-7.53.0), as PR was cherry-picked in branch 7.52.0. |



Description
This PR implements user-consent-based error reporting functionality that allows users to opt-in to sending error reports to Sentry even when Sentry tracking is not globally enabled. When critical errors occur in authentication flows, users will be prompted to consent to sharing the error report to help improve the app.
Key improvements:
What is the reason for the change?
To provide users with the option to contribute to app improvement by sharing error reports when they encounter issues, while maintaining full control over their data sharing preferences.
What is the improvement/solution?
Implementation of a consent-based error reporting system that prompts users to voluntarily share error information when critical issues occur, enabling better debugging and app improvement without compromising user privacy.
Changelog
CHANGELOG entry: Added optional error reporting with user consent to help improve app stability
Related issues
Fixes:
Manual testing steps
<prerequisite: disable authentication API>
UI :