Connect Android with its Sentry SDK
Your Android 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.
io.sentry:sentry-androidAlready installed? Your code stays as it is – the DSN is the one change.
Start it
Put this in AndroidManifest.xml, inside <application>:
<!-- build.gradle: manifestPlaceholders["SENTRY_DSN"] = System.getenv("SENTRY_DSN") ?: "" --><meta-data android:name="io.sentry.dsn" android:value="${SENTRY_DSN}" />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 build.gradle, 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(RuntimeException("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
What Xovris has run
Driven with the real SDK: io.sentry:sentry 8.64.0 (the core sentry-android runs on) on an R8 9.5.32 release build, captured 2026-11-14 - every frame and the exception retraced through its mapping. Its own bytes are replayed into Xovris on every change.
Every option the SDK has is in its own documentation: docs.sentry.io/platforms/android/
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.