Error tracking
Activate lazy, scrubbed Sentry reporting and production source maps.
The Sentry adapter stays unloaded in mock mode. When selected, it uses a pseudonymous user ID, disables default PII, scrubs request data, and conditionally adds the Expo source-map plugin.
Prompt
Read agent-skills/wire-error-tracking.md. Activate the included Sentry adapter
for separate development and production projects. Keep SENTRY_AUTH_TOKEN in EAS
secrets, start trace sampling at 0, inspect a complete deliberate test event,
and verify production source maps before choosing a conservative sample rate.Never attach
Prompts, meal names, email, tokens, image/local/signed URLs, voice files, request bodies, cookies, or headers do not belong in an error event.
Expected cancellation, permission denial, offline state, and ordinary form validation are product states—not crashes.
Verify
Send deliberate development and release errors, confirm the correct environment, release, and symbolicated stack frames, then inspect the whole payload. Confirm identity clears on sign-out/deletion and mock mode starts no Sentry timers or network calls.