-
-
Notifications
You must be signed in to change notification settings - Fork 355
Missing device info on watchdog_termination events #5182
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
Comments
I can easily reproduce this. When I trigger an OOM crash in the sample app, it also misses device info: https://sentry-sdks.sentry.io/issues/3808632822/events/672779b675c146649bad521c960a74f4/?project=5428557 I think this is related to fixing wrongly applying the scope: #4969. So the device previously could have been wrong. We need to sync the scope here sentry-cocoa/Sources/Sentry/SentryWatchdogTerminationScopeObserver.m Lines 129 to 172 in 5546c67
|
Thanks @gabriellanata for the comparison! @kahest @philipphofmann we might have to bump the priority from high to urgent. |
Couple of insights from my investigation:
Working on a draft PR now. |
Platform
iOS
Environment
Production
Installed
Swift Package Manager
Version
8.48
Xcode Version
16.2
Did it work on previous versions?
No response
Steps to Reproduce
Since approximately April 14, 2025, Sentry has stopped capturing device context (e.g. OS, model, OS version) on
watchdog_termination
events in a particular project of the customer. All other event types for the same device continue to show full device information as expected.Additional details can be found in the internal Jira ticket.
Expected Result
Device context should be populated as it did before.
Actual Result
The Device section is completely empty for watchdog_termination events.
Are you willing to submit a PR?
No response
The text was updated successfully, but these errors were encountered: