Connect React Native with its Sentry SDK
Your React Native app keeps its Sentry SDK. Xovris gives it your project’s DSN, and every error it sends becomes a Xovris issue with its stack and release.
npm install @sentry/react-nativeAlready installed? Your code stays as it is – the DSN is the one change.
Start it
Put this in your app's entry file:
import * as Sentry from '@sentry/react-native';
// Expo builds EXPO_PUBLIC_ variables into the appSentry.init({ dsn: process.env.EXPO_PUBLIC_SENTRY_DSN });
export default Sentry.wrap(App);It takes SENTRY_DSN from your app’s build settings, so your project’s address never sits in your code.
Your project’s DSN
Xovris finds the SDK in your package.json, creates your project’s address and writes it as SENTRY_DSN in your env file, after showing you the change. It then sends a test event and waits until it is stored. In the project, run:
npx xovris@latest initpnpm dlx xovris@latest inityarn dlx xovris@latest initbunx xovris@latest initSee the first error
Send one from anywhere your app runs:
Sentry.captureException(new Error('first error for Xovris'));Capture one error with the SDK’s own call and it appears as a Xovris issue:
- Errors and their stack traces, grouped into issues
- Messages you capture
- The release each event names
Its frameworks
The same DSN covers every framework this SDK’s own integrations reach:
Expo.
What Xovris has run
Driven with the real SDK: @sentry/react-native 8.28.0 in an Expo app on Android 15 (Expo Go, Expo 58.0.25, React Native 0.88.1), captured 2026-11-14 - an uncaught crash, every frame the line it was written on. Its own bytes are replayed into Xovris on every change.
Every option the SDK has is in its own documentation: docs.sentry.io/platforms/react-native/
Your data is never used to train our AI. How your data is kept
A problem is called fixed only once it works again. How each fix is checked
XOVRIS LTD, registered in England and Wales, company number 17499910. Registered office: 66 Paul Street, London EC2A 4NA.