Allow JS stack traces for iOS projects

[gtchance]

Description

We have an iOS project that makes use of shared JS code. We used to have a sort of hack for JS stack traces before attachCustomStacktrace was removed a few years ago.

attachCustomStacktrace(stackTrace, withType: "nodejs")

Is there another way to achieve JS stack traces for an iOS project without forking bugsnag-cocoa and exposing attachCustomStacktrace again?

[hannah-smartbear]

Hi @gtchance,

Just to clarify your question and understand what you are looking for, are you looking to report JS exceptions to your iOS project in BugSnag? If not, what sort of errors are you looking to attach the JS stacktrace to?

Can you let us know a little bit more about how your iOS project uses/integrates the shared JS code?

Please feel free to write in to us at [email protected] if you do not want to share these details about your project publicly.

[gtchance]

Thanks @hannah-smartbear! I will email support with more details.

[mclack]

Thanks for raising the support ticket with us, @gtchance

In the interest of visibility for other users, we have added a task to our backlog to publicly expose BugsnagStackframe properties, which would allow you to access and change stack frame properties such as file, columnNumber and lineNumber.

We do not have an ETA on when this might be implemented, but we will make sure to post any updates on this thread.