-
-
Notifications
You must be signed in to change notification settings - Fork 359
Open
Labels
Description
Problem Statement
Both native SDKs now provide APIs to check if the previous app session ended in a crash:
- iOS (Cocoa SDK 9.8.0+):
SentrySDK.lastRunStatus— returns unknown, no-crash, or crash - Android:
Sentry.isCrashedLastRun()— returns a boolean
There is currently no way to access this information from the React Native (JavaScript) layer.
Use Cases
- Show a recovery UI (e.g., "Sorry, the app crashed") after restarting from a crash
- Disable experimental features that may have caused a crash
- Send custom analytics or breadcrumbs about crash recovery
- Implement progressive rollout logic that backs off after crashes
Proposed Solution
Expose a unified JS API, e.g.:
import * as Sentry from '@sentry/react-native';
const status = Sentry.lastRunStatus();
// Returns: 'unknown' | 'no-crash' | 'crash'Implementation Notes
- Bridge
SentrySDK.lastRunStatuson iOS andSentry.isCrashedLastRun()on Android through the native modules - Normalize the return value across platforms (iOS has 3 states, Android has a boolean — need to decide on a unified shape)
- Should be callable after
Sentry.init()
References
- Cocoa SDK PR: feat: Add
SentrySDK.lastRunStatusto distinguish unknown, no-crash and crash sentry-cocoa#7469 - Cocoa SDK bump to 9.8.0: chore(deps): update Cocoa SDK to v9.8.0 #5847
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
Fields
Give feedbackNo fields configured for issues without a type.