Skip to content
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
merged 44 commits into from
Aug 14, 2024

Conversation

krystofwoldrich
Copy link
Member

📢 Type of change

  • Bugfix

📜 Description

This PR removes the dependency of initializing tracing integrations like NativeFramesTracking and StallTracking before ReactNativeTracing 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

  • I reviewed submitted code
  • I added tests to verify changes
  • No new PII added or SDK only sends newly added PII if sendDefaultPII is enabled
  • All tests passing
  • No breaking changes

#skip-changelog

krystofwoldrich and others added 30 commits June 3, 2024 18:39
@krystofwoldrich 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
Copy link
Contributor

github-actions bot commented Aug 8, 2024

Android (legacy) Performance metrics 🚀

  Plain With Sentry Diff
Startup time 443.21 ms 485.47 ms 42.26 ms
Size 17.73 MiB 20.04 MiB 2.31 MiB

Copy link
Contributor

github-actions bot commented Aug 8, 2024

iOS (legacy) Performance metrics 🚀

  Plain With Sentry Diff
Startup time 1219.07 ms 1224.96 ms 5.89 ms
Size 2.36 MiB 3.06 MiB 714.01 KiB

Copy link
Contributor

github-actions bot commented Aug 8, 2024

iOS (new) Performance metrics 🚀

  Plain With Sentry Diff
Startup time 1237.57 ms 1241.16 ms 3.59 ms
Size 2.92 MiB 3.62 MiB 719.85 KiB

Copy link
Collaborator

@lucas-zimerman lucas-zimerman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@krystofwoldrich
Copy link
Member Author

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.

Base automatically changed from kw/rn-tracing-removed-deprecated-options to v6 August 13, 2024 08:38
Copy link
Collaborator

@lucas-zimerman lucas-zimerman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@krystofwoldrich krystofwoldrich merged commit eeb83da into v6 Aug 14, 2024
56 of 58 checks passed
@krystofwoldrich krystofwoldrich deleted the kw/tracing-integrations-independent-order branch August 14, 2024 07:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants