[skill-drift] update(sentry-react-native-sdk): NavigationContainer wrapper + disableAutoUpload + Kotlin DSL#146
Merged
HazAT merged 1 commit intoMay 29, 2026
Conversation
…apper + disableAutoUpload + Kotlin DSL Automated drift-fix run. Co-Authored-By: Claude (claude-sonnet-4-5) <noreply@anthropic.com>
| navigationIntegration.registerNavigationContainer(navigationRef); | ||
| }} | ||
| > | ||
| <Sentry.NavigationContainer> |
There was a problem hiding this comment.
Bug: Documentation suggests using <Sentry.NavigationContainer>, which will crash on supported SDK versions older than 8.13.0 where the component doesn't exist.
Severity: HIGH
Suggested Fix
Add a version caveat (e.g., "SDK ≥8.13.0 only") directly in the main setup examples where <Sentry.NavigationContainer> is used. Alternatively, use the manual <NavigationContainer ref={...}> approach in the main examples and present <Sentry.NavigationContainer> as a version-specific alternative.
Prompt for AI Agent
Review the code at the location below. A potential bug has been identified by an AI
agent. Verify if this is a real issue. If it is, propose a fix; if not, explain why it's
not valid.
Location: skills/sentry-react-native-sdk/SKILL.md#L270
Potential issue: The setup guide in `SKILL.md` recommends using
`<Sentry.NavigationContainer>` in its main examples for both standard Expo and bare
React Native. However, the documentation's minimum recommended SDK is `≥8.0.0`, while
the `<Sentry.NavigationContainer>` component only exists in SDK versions `≥8.13.0`.
Developers on SDK versions between 8.0.0 and 8.12.x who follow these setup instructions
will encounter a runtime `TypeError` crash because the component will be undefined.
While a version caveat exists in a separate section, its absence from the main setup
paths creates a trap for users.
Did we get this right? 👍 / 👎 to inform future reviews.
This file contains hidden or 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
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.
Warning
Auto-generated from external SDK content. Review all links and code suggestions before acting on them.
Summary
Updates
sentry-react-native-sdkskill to reflect three new features from the upstream SDK:New
Sentry.NavigationContainerwrapper (PR #6199, SDK ≥8.13.0) — Drop-in replacement for React Navigation'sNavigationContainerthat automatically wires up navigation tracking without manual ref management. Updated all React Navigation setup examples to show this as the recommended approach.disableAutoUploadExpo plugin option (PR #6195, SDK ≥8.13.0) — New config option to skip source map and dSYM uploads during local development builds. Documented in Expo plugin reference with usage examples.Kotlin DSL migration (PR #6119, SDK ≥8.13.0) — Android setup now uses
sentry.gradle.kts(Kotlin DSL) instead ofsentry.gradle(Groovy). The old.gradlefile remains as a shim for backward compatibility. Updated Android setup instructions and troubleshooting.Changes Made
Sentry.NavigationContaineras the primary/recommended approachdisableAutoUploadoption to Expo plugin configuration reference with examplessentry.gradle.ktswith backward-compatibility noteVerification
All three changes are mechanical documentation updates:
No breaking changes — all existing code continues to work.
Source PRs
disableAutoUploadoption to Expo plugin