Release 2.2 (GA Performance with auto instrumentation)

[bruno-garcia]

This issue will track the release of v2.2 with auto instrumentation of React Navigation v4, v5, fetch/xhr and react profiler.

• Merged the JS blocking PR: feat: Expose required things for React Native auto tracing sentry-javascript#3144
• Update master with the latest JavaScript SDK.
• Investigate a way to handle blank navigation transactions
• Get a Docs Draft PR ready for auto instrumentation, early so @PeloWriter have a chance to review it.
• Merged the main PR with integrations feat: Auto performance tracing with XHR/fetch, and routing instrumentation #1230
• Review the manual API docs - Make sure they are up to date with API and behavior
• Merge auto instrumentation API.
• craft publish
• Wait for Android device context Get device context on Performance on Android #1291
• Migrate to using beforeNavigate feat: Use beforeNavigate in routing instrumentation to match behavior on JS #1313
• Fix issue regarding the initial transaction on app start fix: React Navigation Instrumentation starts initial transaction before navigator mount #1315
• Document updated beforeNavigate
• Prepare wizard PR for the docs (will be merged N days after GA)
• Merge Context updating methods from JS: feat(tracing): Add context update methods to Span and Transaction sentry-javascript#3192

[marandaneto]

I'd say we could go ahead without #1291 and iterate later

[marandaneto]

@jennmueng mind explaining what's the issue with the beforeNavigate? not sure what this is about

[jennmueng]

@marandaneto beforeNavigate (to be passed to the ReactNativeTracing integration) currently wasn't used in RN due to the limitation with the V5 instrumentation but I found a workaround that allows it to be used. This way we match the API on JS and get rid of the redundant shouldSendTransaction option passed to the instrumentation.

[marandaneto]

@jennmueng cool thanks, should we create its own issue for that. so we could track it down and link to the PR? this also would require docs?

[PeloWriter]

Yes, please, on the Docs. Here's the WIP for Performance Docs - getsentry/sentry-docs#2970

[marandaneto]

@jennmueng cool thanks, should we create its own issue for that. so we could track it down and link to the PR? this also would require docs?

@jennmueng I guess this issue is ready to be closed, do we need to update docs?

[jennmueng]

@marandaneto Yes we need docs

[marandaneto]

ok now we have its own issue for docs getsentry/sentry-docs#2995 and we can close this issue