-
Notifications
You must be signed in to change notification settings - Fork 252
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
onUnhandledRejection missing from React Native #1816
Comments
Hi @shamilovtim - we mark uncaught promise rejections as That said, I'm going to pass your feedback onto our product team to see if there's anything we can do to make these types of error identifiable via a callback 👍 |
Hi @shamilovtim, following some internal discussion we have added an item on the roadmap to expose the event type in a callback as way for you to achieve this. At the moment we don't have an ETA for this but we will keep you updated. |
Description
Unhandled promises are warnings. They are not crashes or exceptions. Bugsnag is treating them like "unhandled exceptions" which affects our stability score and makes it inaccurate. We care that the app is crashing, not that Promises haven't resolved successfully.
Describe the solution you'd like
To make unhandled promises be considered "handled" exceptions we require the
onUnhandledRejection
callback. It is not available to us neither in the JS nor on the native platforms.Describe alternatives you've considered
The API surface on React Native is too minimal and does not provide us with many options to accomplish this a different way.
Additional context
Please consider enlarging the React Native JS API. It does not have many options like the JS API does and leaves us having to make feature requests on this repo.
The text was updated successfully, but these errors were encountered: