Add Sentry to your Expo app with readable stack traces, catch real user crashes, and get the top issues explained in plain English.
Users say the app crashes. Set up crash reports so I can see why
How it works
- Create a Sentry project: Vovy opens Sentry, creates a React Native project, and copies the DSN, the address your app sends crash reports to.
- Install the Sentry SDK: Vovy asks Claude Code to add @sentry/react-native, its Expo config plugin, and Sentry.init at your app's entry point.
- Upload source maps: Vovy adds the Sentry auth token as an EAS secret so builds and updates upload source maps. Without them, crash traces are unreadable minified code.
- Trigger a test crash: Vovy adds a temporary test button, taps it in a build, and confirms the error lands in Sentry with the right file and line.
- Explain your top crashes: Vovy reads your Issues list and shows a table: each crash, how many users it hit, the device and OS, and a likely fix.
What you provide
- A Sentry account (free tier works)
- Your Expo project
What you get
- Crash reporting in your app
- Readable stack traces
- A ranked table of real crashes
FAQ
Does App Store Connect not show crashes already?
It shows some crash reports, but they are delayed and hard to read. Sentry shows the exact line and the steps before the crash.
Will this slow my app down?
Not noticeably. Sentry sends reports in the background.
Is Sentry free?
Sentry has a free Developer plan with a monthly error quota that is plenty for an early app.
Related tasks
All tasks