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
When using Bugsnag in an iOS project using Kotlin Native we use the Bugsnag.notify method to record unhandled NSExceptions (which are created from the unhandled Kotlin exceptions).
Up until v6.26.2 this has been working quite well. However since v6.26.2 the unhandled property on the event no longer controls whether the event is stored to disk (#1549). This results in the exceptions being lost since the app immediately terminates after the notify call.
Describe the solution you'd like
I would like to request a parameter or a method that will force the exception to be written to disk.
So something like Bugsnag.notifyFatal or event.isFatal = true would be great.
P.S. I can create a PR for this, just let me know what API best fits the Bugsnag Cocoa library.
Describe alternatives you've considered
I am currently "overriding" the originalUnhandledValue to return the modified unhandled value. Which obviously isn't ideal.
The text was updated successfully, but these errors were encountered:
Description
When using Bugsnag in an iOS project using Kotlin Native we use the
Bugsnag.notify
method to record unhandledNSException
s (which are created from the unhandled Kotlin exceptions).Up until v6.26.2 this has been working quite well. However since v6.26.2 the
unhandled
property on the event no longer controls whether the event is stored to disk (#1549). This results in the exceptions being lost since the app immediately terminates after thenotify
call.Describe the solution you'd like
I would like to request a parameter or a method that will force the exception to be written to disk.
So something like
Bugsnag.notifyFatal
orevent.isFatal = true
would be great.P.S. I can create a PR for this, just let me know what API best fits the Bugsnag Cocoa library.
Describe alternatives you've considered
I am currently "overriding" the
originalUnhandledValue
to return the modifiedunhandled
value. Which obviously isn't ideal.The text was updated successfully, but these errors were encountered: