Verification Checklist

Before you ship any project to production, run through this checklist. Every item here represents something that, if missed, will silently reduce Sentry's effectiveness — you'll think it's working when it isn't.

This checklist takes about 10 minutes the first time. After doing it once, most items become habits and take 2 minutes to confirm.

---

Account & Project

• Sentry account created at sentry.io — you can log in successfully
• Organisation slug noted — found in Settings → Organisation → "Organisation Slug". Write it here: _______________
• Sentry project created for this specific app — not reusing a project from another app
• Platform selected correctly — React for Vite apps, Next.js for Next.js apps, React Native for mobile
• Project slug noted — found in Settings → Projects → click your project → "Project Slug". Write it here: _______________
• Alert rule active — Settings → Alerts → at least one rule that emails you on new issues

---

DSN Configuration

• DSN copied from Sentry — Settings → Projects → Client Keys (DSN)
• DSN added to .env — VITE_SENTRY_DSN=https://... (Vite projects) or NEXT_PUBLIC_SENTRY_DSN=https://... (Next.js projects)
• .env is in .gitignore — the DSN must never be committed to GitHub as a hardcoded value in the env file (it can be in code via import.meta.env.VITE_SENTRY_DSN)
• DSN added to Vercel — Settings → Environment Variables in your Vercel project, with Environment set to "Production"
• DSN saved to VaultMate — under this project's entry, category "API Key", title "Sentry DSN"

---

SDK Installation

• @sentry/react installed — check package.json for "@sentry/react" in dependencies
• src/lib/instrument.ts created — with Sentry.init() configured correctly
• enabled: import.meta.env.PROD — Sentry only runs in production, not development
• instrument.ts is the first import in main.tsx — before React, before anything else. Open main.tsx and verify line 1 is import './lib/instrument'
• Sentry.setUser() called after login — in your auth context or auth state handler
• Sentry.setUser(null) called after logout — clears user context so errors aren't attributed to the wrong person

---

Live Error Capture Test

This is the critical test. Do not skip it.

• Test error thrown in a production build — temporarily added throw new Error("Test Sentry error") to a component, ran npm run build && npm run preview (or deployed to Vercel preview URL)
• Error appears in Sentry Issues within 60 seconds — go to your Sentry project → Issues tab and confirm the test error is visible
• Test error removed and production redeployed — the test throw line has been deleted, a clean build deployed

---

User Context

• Log into your app in a browser
• Trigger the test error again (or trigger a real error)
• Check the Sentry issue — open the issue detail and look for "User" in the right panel. It should show your email address or user ID, not "Anonymous"
• If user shows as Anonymous: check that Sentry.setUser() is being called after the login completes, and that the call happens after Sentry has initialised (i.e., instrument.ts was already loaded)

---

Source Maps (Complete the Auth Tokens section first)

• @sentry/vite-plugin installed — check package.json
• .env.sentry-build-plugin created with SENTRY_ORG, SENTRY_PROJECT, SENTRY_AUTH_TOKEN
• .env.sentry-build-plugin in .gitignore — this file contains an auth token and must never be committed
• vite.config.ts updated — build.sourcemap: "hidden" and sentryVitePlugin() added
• Production build run — npm run build completed without errors
• Build output confirms upload — terminal shows Sentry plugin messages confirming source maps were uploaded and deleted from dist/
• Stack trace shows readable code — open any Sentry issue captured after this build. The stack trace should show file names like src/components/FeePaymentForm.tsx:112, not minified names

---

Auth Tokens

• Source Maps Token created in Sentry — Settings → Auth Tokens, with permissions project:releases and org:read
• Source Maps Token saved to VaultMate — title "Sentry Auth Token — Source Maps", category "API Key"
• Source Maps Token added as GitHub Secret — repository → Settings → Secrets → SENTRY_AUTH_TOKEN
• Read Token created in Sentry — separate token with permissions event:read and project:read
• Read Token saved to VaultMate — title "Sentry Read Token — Admin Dashboard", category "API Key"
• Read Token added as Supabase secret — supabase secrets set SENTRY_READ_TOKEN=sntrys_...

---

Final Confirmation

When every item above is checked, answer these three questions:

1. If your app crashes at 3am tonight, will you know about it? Yes — if the alert rule is active and your email is the action target.

2. When you open the Sentry issue tomorrow morning, will you know which file and line caused the crash? Yes — if source maps are configured and the Vite plugin uploaded them during the build.

3. Will you know which user was affected? Yes — if Sentry.setUser() is called after login with the user's ID and email.

If the answer to all three is yes, Sentry is fully operational. Ship with confidence.

---

What to Do When an Error Arrives

Once Sentry is live, you'll receive email alerts for new errors. Here is the process to handle them efficiently: