Sentry
Sentry watches your app once it's in real users' hands. When something throws, it captures the crash with a full stack trace, the device and OS, and the steps that led there, then groups similar errors together so you fix the cause once. It also tracks performance, so you can see which screens and calls are slow. In an app you build with Appsanic, you use it to know about crashes before your users tell you about them.
What you get by connecting it
Connect Sentry inside the project and the agent can:
- Add a small JavaScript reporter and error boundary for preview-visible failures.
- Generate native SDK, release, privacy, and tagging setup for you to complete after export.
- Generates source-map setup instructions for exported builds. Source-map upload is not an automatic connector action.
You describe what you want monitored in plain English. The agent handles the wiring.
Connecting it
You need your DSN. An optional auth token enables only a read-only connection probe; it is not transferred to a build or used for source-map uploads.
- In Sentry, open Project settings then Client Keys (DSN) and copy the DSN. It's a URL that's public by design and safe to embed.
- For readable stack traces in an exported build, follow Sentry's Expo or React Native release setup. The connector does not currently run
sentry-clifor you. - Open the Appsanic project build, select Connectors, choose Sentry, and enter the DSN. Add an optional token only if you want the read-only probe. The connection applies only to that project and requires a paid Appsanic plan.
The publishable DSN remains visible. An optional auth token shows as dots and never returns to browser JavaScript. Use Test now to re-check the connection and Disconnect to remove it from the project.
Keys and security
Sentry is a just connect connector. The DSN is publishable by design, so the agent embeds it where the minimal preview reporter needs it. There is no Account access toggle. Full native monitoring and source-map upload remain manual exported-build steps; provision a separate scoped build token directly in the EAS/build environment.
The DSN is approved public connector metadata. An optional auth token is encrypted at rest with AES-256-GCM and represented outside trusted server code only by a presence flag. The model prompt never receives the token, and the agent never asks you for one in chat.
Useful links
- Sentry documentation: https://docs.sentry.io
- Appsanic guide: Error Monitoring
Next
Read Error Monitoring for how crash reporting and alerting fit together across the apps you build.