iOS: Uncaught exception reason missing in Sentry.io

#1

Hi,

We’re are switching to Sentry for our iOS app. We noticed some of the crash reports on Sentry.io are missing critical information like exception reason and even the stack trace at times.

Here’s an example.

When the app crashes while connected to the debugger, we’d see the info below in XCode’s console log.

 Terminating app due to uncaught exception 'NSObjectInaccessibleException', reason: 'CoreData could not fulfill a fault for '0xcb0d97569971f453 <x-coredata://9051DDD5-2F6C-49CD-BDBC-BF674B4C7B9D/Order/p3>''

However, when we check the same crash in Sentry.io, we’d just see

C++ Exception
_NSCoreDataException

With an error

exception.values.0.stacktrace.frames: Discarded invalid value Collapse
Reason	
expected a non-empty value

We’ve seen a couple more crashes that has this issue. There’s one crash where we got the message “-[__NSCFDictionary setObject:forKey:]: attempt to insert nil key” in XCode’s console log but Sentry didn’t show this message at all.

Is there something we can do to ensure that the complete crash information are sent to Sentry?

#2

Hey, so this PR should fix the reason error

#3

Cool, thanks Daniel! Appreciate the quick turnaround!