sentry-cocoa: Xcode organizer reports crash on `writeBinaryImage`
Platform
iOS
Installed
CocoaPods
Version
7.16.0
Steps to Reproduce
Add sentry to app and start reporting issues.
SentrySDK.start { (options) in
options.dsn = dsn
options.debug = false
options.enableAutoSessionTracking = false
options.attachStacktrace = false
options.maxBreadcrumbs = 25
options.beforeSend = { event in
// Some data is removed to make reports lighter
event.debugMeta = nil
return event
}
}
Expected Result
Crashes should be seen in sentry as well as in XCode organizer.
Actual Result
XCode organizer starts showing a lot of different crashes as one, where Sentrys writeBinaryImage is shown as the cause for the crash.

About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 31 (20 by maintainers)
Commits related to this issue
- Disable sentry Waiting for https://github.com/getsentry/sentry-cocoa/issues/1892 to be fixed — committed to ProtonVPN/ios-mac-app by jaroslavas 2 years ago
Yes, we definitely plan to fix this. We had a minor set back that delayed this, but we’re working to have it fixed.
This could be related to https://github.com/getsentry/sentry-cocoa/issues/1864.
@jaroslavas Could you provide a full crash report for some of these examples? There should be a thread that is indicated as the “Crashed thread”, and maybe other info like an exception type or backtrace.
My guess is that since our symbols show up in crash reports (which is normal; our crash handler logic is running to collect crash info) Xcode sees us as a common element amongst the reports and is blaming us. In practice, automatically choosing a frame to blame for a crash report is an inexact art.