-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Not reporting issues in production on Android, React Native #755
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
Comments
From my understanding this should have been fixed by #626 but a relaunch doesn't send any stashed reports either. |
Just tested on iOS and the problem seems to be the same there |
Experiencing the same issue |
Any update on this? I am trying this out and have only been able to get errors working in DEV on iOS |
What version of React Native are you all using? And, did this just start occurring? Or are you new Sentry users and this has never worked? |
Confirmed to occur on React Native v0.35.0 for me. New to Sentry. |
I think it's relative with this one #731 |
New to sentry as well, using raven-js 3.8.1, RN 0.27.2 |
@Looveh are you able to catch exceptions and report them to Raven this way? const onReportToSentry = () => {
try {
throw new Error('This exception should be captured and sent to Raven manually!')
} catch (e) {
Raven.captureException(e)
}
} I have found that the above works for me, but UNCAUGHT exceptions cause the app to close and are not tracked. This is a huge issue. |
Hey, |
Do you want to request a feature or report a bug?
bug
What is the current behavior?
Error reports are sent when running app in development mode on Android using React Native, but not in production. Only tested on Android, not iOS.
What is the expected behavior?
For error reports to be sent in both development and production mode.
The text was updated successfully, but these errors were encountered: