Describe the bug
What's Wrong
For certain utilities in plugins like trackGlobalErrors, we use React Native deep imports. See
However, in a recent build, I have noticed this deep symbol stack trace is now broken.
When we get a 500 response in the Ignite Podcast demo screen, Reactotron is not able to parse the stack trace.
We are hitting this error:
|
client.error("Unable to parse stack trace from error object", []) |
How to reproduce
npx ignite-cli@latest new PizzaApp, keep the demo code
- Install packages, run prebuild, build an iOS or Android build
- Open Reactotron
- Go to the Podcast tab.
- Change the url to be something that is broken, like an invalid url
- Load the page.
- See the logs in the Reactotron timeline.
Reactotron version
5.1.16
Describe the bug
What's Wrong
For certain utilities in plugins like trackGlobalErrors, we use React Native deep imports. See
reactotron/lib/reactotron-react-native/src/plugins/trackGlobalErrors.ts
Line 74 in 6a48477
However, in a recent build, I have noticed this deep symbol stack trace is now broken.
When we get a 500 response in the Ignite Podcast demo screen, Reactotron is not able to parse the stack trace.
We are hitting this error:
reactotron/lib/reactotron-react-native/src/plugins/trackGlobalErrors.ts
Line 98 in 6a48477
How to reproduce
npx ignite-cli@latest new PizzaApp, keep the demo codeReactotron version
5.1.16