-
-
Notifications
You must be signed in to change notification settings - Fork 448
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
Add crashedLastRun #1125
Comments
related to #911 |
We discussed that an update to the docs is due first: https://develop.sentry.dev/sdk/features/#user-facing-platforms And that this callback will be taken via the public, static API so the user can call when they are ready to get their callback invoked/get the UI shown to the user. |
We dropped the idea of using a callback here. Copying for #1569
|
Add
a callbackcrashedLastRun to SentryOptions that is called by the SDK passing the eventwhen Sentry is initialized and the last program execution terminated with a crash.
PR in Cocoa: getsentry/sentry-cocoa#808
Docs in Cocoa: https://docs.sentry.io/platforms/apple/enriching-events/user-feedback/
On Cocoa, we have the advantage that crashes get written to disk by SentryCrash and then the SDK processes them the next time the app starts. So we can check in the
prepareEvent
of theClient
if the current event is a crash and call the callback.On Java, this is a bit more tricky, because the crash event could be sent before the app shuts down. Therefore we need to store the eventID of the crash somewhere, so it is still there when the app starts the next time.
The text was updated successfully, but these errors were encountered: