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

Sentry not sending errors in release #631

Closed
calebmer opened this issue Jun 28, 2016 · 1 comment
Closed

Sentry not sending errors in release #631

calebmer opened this issue Jun 28, 2016 · 1 comment

Comments

@calebmer
Copy link

It looks like Sentry is not sending crash errors in React Native releases, but these errors are getting sent in debug builds. I switched the order of these two lines and everything worked fine. My theory is that in releases the default error handler (defaultHandler) stops the JS thread. Here’s the React Native code that leads me to that assumption. So if the JS thread is stopping after defaultHandler, Raven.captureException will not run. Switching the order of the two, again, appears to work fine.

@benvinegar
Copy link
Contributor

benvinegar commented Jun 28, 2016

Hey @calebmer – we're aware of this situation. There's a number of issues already open tackling this subject, including a PR #626.

Closing as duplicate.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants