Hi - I’ve been working on a ‘plugin’ for NativeScript that consumes the android and iOS SDKs. Everything is working perfectly except the iOS uncaught exception logs aren’t very useful within the NativeScript framework. If you’re not familiar with NativeScript, it’s somewhat similar to React-Native but without the bridging mechanism so the consumption of native SDKs is much more direct.
The issue I’m facing lies within the actual exception that is caught and logged on the Sentry site for reviewing the crash. I’ve been in contact with the NativeScript iOS runtime team and they’re open and trying to assist in making the log provide the stack trace in the exception. Currently this is what we have logged (https://sentry.io/share/issue/2963994779d5441a9c91ab38e87d261f/) for an uncaught iOS exception. The actual stack trace is in the
exception in the
breadcrumbs which would be perfectly fine as this is reporting where in the JS stack the crash occurred. However it’s trimmed in the
breadcrumb section so I can’t view all of it.
The developer who recently worked on throwing the exception had mentioned here (https://github.com/NativeScript/ios-runtime/pull/964#issuecomment-409501607) to see if Sentry iOS can display the
reason of the exception in the logs as that would work well with how the exception is currently thrown.
Any help from the Sentry team on how to improve the log for uncaught exceptions with iOS are greatly appreciated and the NS team I imagine would be responsive enough to collaborate on how best to make this work with the framework.