-
-
Notifications
You must be signed in to change notification settings - Fork 342
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
(6) fix(tracing): ReactNativeTracing and initial navigation spans have to be created after integrations setup #4000
Merged
krystofwoldrich
merged 44 commits into
v6
from
kw/tracing-integrations-independent-order
Aug 14, 2024
Merged
(6) fix(tracing): ReactNativeTracing and initial navigation spans have to be created after integrations setup #4000
krystofwoldrich
merged 44 commits into
v6
from
kw/tracing-integrations-independent-order
Aug 14, 2024
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Co-authored-by: LucasZF <[email protected]>
krystofwoldrich
changed the title
fix(tracing): ReactNativeTracing and initial navigation spans have to be created after integrations setup
(6) fix(tracing): ReactNativeTracing and initial navigation spans have to be created after integrations setup
Aug 8, 2024
Android (legacy) Performance metrics 🚀
|
iOS (legacy) Performance metrics 🚀
|
iOS (new) Performance metrics 🚀
|
lucas-zimerman
approved these changes
Aug 9, 2024
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!
lucas-zimerman
requested changes
Aug 9, 2024
I've fixed the JS tests. The e2e fails due to #4004 unrelated to this PR, it will be fixed when I merge main to v6. |
Closed
Base automatically changed from
kw/rn-tracing-removed-deprecated-options
to
v6
August 13, 2024 08:38
lucas-zimerman
approved these changes
Aug 13, 2024
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!
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
📢 Type of change
📜 Description
This PR removes the dependency of initializing tracing integrations like
NativeFramesTracking
andStallTracking
beforeReactNativeTracing
integration.This dependency was introduced in #3996 and #3997 when extracting the mentioned into standalone integration.
The cause of the dependency was that ReactNativeTracing start initiali navigation span during the integrations setup, but should do it after all integrations are setup.
💚 How did you test it?
integration tests, sample app
📝 Checklist
sendDefaultPII
is enabled#skip-changelog