Skip to content

Sentry not sending errors in release #631

Closed

Description

@calebmer

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.

Activity

  1. benvinegar commented on Jun 28, 2016

    @benvinegar
    Contributor

    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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions