-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
chore: Remove navigation instrumentation #12174
chore: Remove navigation instrumentation #12174
Conversation
CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes. |
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
…onsistently we get in android and IOS the same outputs
Bitrise🔄🔄🔄 Commit hash: 68d6962 Note
|
Bitrise✅✅✅ Commit hash: b841b3d Note
|
Bitrise✅✅✅ Commit hash: 26ceb41 Note
|
Quality Gate passedIssues Measures |
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 <3
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
Description
This PR removes navigation instrumentation of Sentry configuration.
The reason why we are removing navigation instrumentation is that transaction.durations were not showing accurate values, since if a user backgrounded the app and opened, that time would be added to the transaction.duration, creating issues on our measurements.
Related issues
Fixes: #12165
Manual testing steps
Screenshots/Recordings
Before
After
Pre-merge author checklist
Pre-merge reviewer checklist