Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

React-native iOS stack trace needs symbolication #1082

Open
BethanyBerkowitz opened this issue Jun 2, 2023 · 0 comments
Open

React-native iOS stack trace needs symbolication #1082

BethanyBerkowitz opened this issue Jun 2, 2023 · 0 comments
Assignees
Labels
react-native @honeybadger-io/react-native

Comments

@BethanyBerkowitz
Copy link
Contributor

BethanyBerkowitz commented Jun 2, 2023

See #1069 (comment)

In the iosUtils.ts file, the backtrace generated does not match the BacktraceFrame type. This code parses the localizedDescription from the iOS error into something resembling a Honeybadger backtrace, however it doesn't make a lot of sense when passed in because the localizedDescription is not symbolicated... it doesn't contain lines or columns, or even file names. Instead it has a memory address, which needs to be translated.

This document from Andrey provides useful background on iOS symbolication.

I'm not sure how this was intended to work, but it may have to do with https://github.com/honeybadger-io/react-native-internal/tree/main/resolve_ios_backtrace.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
react-native @honeybadger-io/react-native
Projects
None yet
Development

No branches or pull requests

3 participants