[skill-drift] update(sentry-react-native-sdk): document enableHistoricalTombstoneReporting#294
Open
github-actions[bot] wants to merge 1 commit into
Conversation
…calTombstoneReporting Automated drift-fix run. Co-Authored-By: Claude (claude-sonnet-5) <noreply@anthropic.com>
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.
PR #6450 (released in v8.19.0) adds a new Android-only
enableHistoricalTombstoneReportinginit option. When enabled, the SDK reports historical tombstones from Android'sApplicationExitInfoAPI (not just the tombstone from the latest app run). Historical events omit current scope data (breadcrumbs, etc.) since the app state at the time they occurred can't be reconstructed. It only takes effect whenenableTombstoneis alsotrue.Added the option next to the existing
enableTombstoneoption in both places it's documented inerror-monitoring.md: the "Native Configuration Options" snippet and the full-options kitchen-sink example.Other drift noticed but not addressed here (mention only, needs more judgment): PR #6377 adds an internal TurboModule call-count/latency aggregator (
turboModuleAggregator) exported from the package's public entrypoint alongside the existingwrapTurboModuleAPI — it's unclear yet whether this is meant to be user-facing or purely internal instrumentation, so it may warrant a follow-up review rather than a mechanical doc edit.Source PRs