Connect Unity with its Sentry SDK
Your Unity 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.
Package Manager: https://github.com/getsentry/unity.git#3.0.0Already installed? Your code stays as it is – the DSN is the one change.
Start it
No code: the SDK starts itself. Give it the DSN in the Unity editor: Tools, then Sentry - paste the DSN into its DSN field.
The DSN lives in the SDK’s own settings, saved with your project.
Your project’s DSN
Xovris finds the SDK in your Packages/manifest.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:
SentrySdk.CaptureException(new System.Exception("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
Read through the Sentry protocol every Sentry SDK speaks. Xovris has not yet driven this SDK itself, so its own bytes are not in the tests yet.
Every option the SDK has is in its own documentation: docs.sentry.io/platforms/unity/
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.