RobertoSmartBear
commented
2 months ago Hi @Kabeer-Haseja 👋🏻,
It looks like the code in your app could be obfuscated or minified, so to get a full readable stacktrace you’d need to upload source maps to your BugSnag project. Our recommendation is to use the BugSnag CLI for these uploads, but you can check the full instructions in our docs: https://docs.bugsnag.com/platforms/react-native/react-native/showing-full-stacktraces/
If you are already uploading source maps and have fully symbolicated stacktraces, or you’re having issues with uploading source maps, could you please provide more details? Sharing some links to errors in your dashboard which display the difference between the incomplete stacktraces and the more detailed ones would be particularly helpful for further investigation.
As this is a public thread, please feel free to open a support ticket with us directly by contacting support@bugsnag.com with any additional information you can provide, and we’d be happy to look into this more.
clr182
When the app crashes or logs an error, the React component stack trace on the Bugsnag dashboard appears incomplete or ambiguous. The stack trace looks like this on Bugsnag:
componentStack in RCTView in Unknown in Unknown in Connect(Component) in Unknown in Unknown in Unknown in RCTView in Unknown in RCTView in UnknownHowever, when running the app on a local simulator, the same error provides a much more detailed and correct stack trace, such as:
componentStack in RCTView (at View.js:34) in View (at ClientDetailsPage.js:903) in ClientDetailsPage (created by Connect(ClientDetailsPage)) in Connect(ClientDetailsPage) (at SceneView.tsx:130) in StaticContainer in EnsureSingleNavigator (at SceneView.tsx:122) in SceneView (at useDescriptors.tsx:181) in RCTView (at View.js:34) in View (at CardContainer.tsx:245)version is "@bugsnag/react-native": "^7.6.3", react native version is 0.64.0