An overview of different error-handling techniques available.
This guide details a few strategies for reporting and recovering from errors in your project.
If your app encounters a fatal JavaScript error, native runtime will report the error differently depending on whether your app is in development or production.
In Development: If you're serving your app from Expo CLI, the fatal JavaScript error will be reported to the React Native RedBox API and no other action will be taken.
In Production: If your published app encounters a fatal JavaScript error, the native app will immediately reload your JavaScript bundle. If the error happens very quickly after reloading, your native app will crash.
We recommend using Sentry to track JavaScript errors in production and configuring a post-publish hook to keep your exported source maps up to date.
You can compile your project locally to use first-party native debuggers (Xcode/Android Studio). See native debugging guide for more information.
Unlike the browser, there are a few circumstances where it's possible to crash the native app by writing invalid JavaScript. Usually, these are in areas where it would be performance-prohibitive to add native validation to your code, e.g. the part of the React Native bridge that converts JS objects into typed native values. If you encounter an inexplicable native crash, double check that your parameters are of the right type. These types of issues can be mitigated by using TypeScript.