-
-
Notifications
You must be signed in to change notification settings - Fork 340
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
App, Culture Context for Crashes #2524
Labels
Comments
5 tasks
Here’s the original pr that attached the context: #2036 |
brustolin
changed the title
App, Permission and Culture Context for Crashes
App, Culture Context for Crashes
Dec 14, 2022
This was fixed with #3699. |
github-project-automation
bot
moved this from Backlog
to Done
in Mobile & Cross Platform SDK
Apr 30, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
Before #2523, the SentryClient attached out-of-date context data to crashes. Instead of attaching the data in the SentryClient, we should put that data in the scope of the global hub, which automatically syncs the data to the scope of SentryCrash by using
SentrySDK.currentHub configureScope
.The SDK already adds similar data to the scope in the
SentryCrashIntegration
, but this has the downside of having less context when disabling theSentryCrashIntegration
. We could create an extra integration calledSentryEventContextEnricher
or something like that, and move the code form the SentryClient to this integration.The text was updated successfully, but these errors were encountered: