You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems like breadcrumbs logged with Bugsnag+leaveBreadcrumbWithMessage: is not included when logging uncaught nsexceptions.
Root cause seems to be that the breadcrumbs are only added to configuration.metaData in notify:withData:atSeverity:atDepth: which only seems to be used for manually reported exceptions.
When KSCrash calls serialize_bugsnag_data (as it's onCrash callback) for other exception types breadcrumbs will not be in the meta data struct.
Manually hacking the situation by calling [[Bugsnag performSelector:@selector(notifier)] performSelector:@selector(serializeBreadcrumbs)]; after each call to leaveBreadcrumbWithMessage seems to work around the issue.
The text was updated successfully, but these errors were encountered:
Thank you for the report, @anderscarling. You are correct that the latest release does not include breadcrumbs with uncaught exceptions. However this issue has been resolved per #86, which should be released later this week.
It seems like breadcrumbs logged with
Bugsnag+leaveBreadcrumbWithMessage:
is not included when logging uncaught nsexceptions.Root cause seems to be that the breadcrumbs are only added to
configuration.metaData
innotify:withData:atSeverity:atDepth:
which only seems to be used for manually reported exceptions.When KSCrash calls
serialize_bugsnag_data
(as it'sonCrash
callback) for other exception types breadcrumbs will not be in the meta data struct.Manually hacking the situation by calling
[[Bugsnag performSelector:@selector(notifier)] performSelector:@selector(serializeBreadcrumbs)];
after each call toleaveBreadcrumbWithMessage
seems to work around the issue.The text was updated successfully, but these errors were encountered: