Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Uncaught errors are not captured on React Native
See original GitHub issueWhen using Raven in ReactNative, any error that is thrown outside of a try-catch block is not captured. It looks like there was an attempt to capture by calling ErrorUtils.setGlobalHandler. Unfortunately, in production the errors are never captured because the app crashes before the request is complete.
One option is to skip the defaultHandler, which is what causes the app to crash. However, the best behaviour is application-specific.
Perhaps the best solution is to avoid attempting calling ErrorUtils.setGlobalHandler at all in the React Native plugin, and instead to provide documentation for users to do it themselves?
Issue Analytics
- State:
- Created 7 years ago
- Reactions:1
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Hey, Check out our official client for react-native -> https://github.com/getsentry/react-native-sentry Closing this here since it’s obsolete. If you’re still having troubles, please create an issue there. Thanks
Thanks. I still have some troubles with CodePush and Sentry. Can you help me? I reached you on Twitter 😃 Thanks!