You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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 afterdefaultHandler
,Raven.captureException
will not run. Switching the order of the two, again, appears to work fine.The text was updated successfully, but these errors were encountered: