Skip to main content

React Native crash reporting

Your React Native app broke on a phone in another country. Native crash or JavaScript error, the stack still reaches you.

BugSplat's Expo module captures native crashes on iOS and Android and JavaScript errors from your React code, symbolicates both against the build you shipped, and shows you the faulting line.

Why BugSplat for React Native

One Expo module captures native iOS and Android crashes and JavaScript errors, symbolicated against the dSYMs, .so files, and source maps from your release build.

01 · It lands

Something breaks in your React Native build. You find out first.

Add the Expo module, initialize it with your database, app, and version, and native crashes on iOS and Android report automatically. Wrap your tree in the error boundary to catch React render errors, or post caught errors yourself with the chain of causes intact. If it is the companion app to a game, it reports into the same dashboard as the game.

  • Native crashes on iOS and Android plus JavaScript errors, one module
  • React render errors caught by the ErrorBoundary, with the chain of causes
  • dSYMs and .so files uploaded automatically from release builds
A crash report in BugSplat with application, group, exception, platform, and the user's feedback - how React Native crashes and errors arrive

02 · It groups and resolves

A report count is not a bug count.

BugSplat groups React Native crashes and errors your way: your rules decide which call stacks count as the same bug, and the list is ranked by how many people each one hit. Native frames symbolicate against the dSYMs and .so files from your release build, and JavaScript frames resolve against the source maps you export, so both read with file and line.

  • Thousands of reports collapse into a short list of distinct bugs
  • Your own file and line from the source map, not an offset into a minified bundle
  • OS, hardware, and build on every report
A symbolicated active thread in BugSplat with the faulting frame expanded to its file, line, arguments, and locals

03 · It tells you

Stay ahead of the next one.

Alerting for React Native crashes and errors hits Slack, Discord, or Teams the moment something spikes. Version-over-version analytics show whether each release is more stable than the last.

  • Regressions flagged when a fixed crash comes back
  • Daily and weekly digests with the highlights
A BugSplat new group alert in Discord with the crash group and stack trace

What makes BugSplat different

Crash reporting that covers the native half of React Native.

JavaScript errors are the easy half. Native crashes on iOS and Android are the half we have always done.

Native from the start

BugSplat has been turning minidumps into readable stacks since 2005. Symbols, PDBs, and native crashes are the core of the product.

A bill that holds still

Flat monthly plans with fixed limits. A spike in crash volume after a release doesn't change your bill.

Answered by the people who build it

Email support with a React Native question and you'll hear back from an engineer who builds BugSplat, usually the same day.

React Native setup

Wire up React Native and read a real stack the same day.

Add the SDK and upload symbols and source maps with each build. If you get stuck, contact support and you'll reach the engineers who build BugSplat.

By clicking "Accept", you agree to the storing of cookies on your device. View our Privacy Policy .