Firebase App Check: requests rejected (403 / app-check-token-is-invalid / attestation failed)
With App Check enforced, calls without a valid attestation token are blocked.
App Check token is invalidfirebase app check 403Firebase App Check token is invalid. Meaning
Register the app with a provider (reCAPTCHA v3/Enterprise, Play Integrity, DeviceCheck/App Attest), initialise App Check before other Firebase calls, use a debug token for emulators/CI (self.FIREBASE_APPCHECK_DEBUG_TOKEN = true and register the token), and check "Unenforced" vs "Enforced" modes.
Common causes
- App Check enforced but SDK not initialised
- Wrong provider/site key
- Debug token not registered
- Emulator/simulator without attestation
- Domain not allowed for reCAPTCHA
⚡ Quick fix
- Initialise App Check before using services
- Register a debug token for dev/CI
- Verify provider keys and allowed domains
Detailed fix by platform
JavaScript
initializeAppCheck(app, { provider: new ReCaptchaV3Provider("SITE_KEY"), isTokenAutoRefreshEnabled: true });
How to diagnose
- Enforcement — On?
- Provider — Configured?
- Debug token — Registered?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
- 15281 SQL Server Msg 15281: SQL Server blocked access to procedure 'sys.xp_cmdshell' (component 'xp_cmdshell' turned off)
- AADSTS50053 AADSTS50053: Your account is locked (Smart Lockout) / sign-in blocked due to suspicious activity
- APNs FCM: THIRD_PARTY_AUTH_ERROR — APNs credentials missing or invalid (iOS push not delivered)
Most viewed in Google Cloud / Firebase
- Container failed to start Cloud Run: The user-provided container failed to start and listen on the port defined provided by the PORT=8080 environment variable
- 409: The resource already exists Compute Engine: ERROR: (gcloud.compute.instances.create) Could not fetch resource: The resource 'projects/p/zones/z/instances/vm-1' already exists
- BigQuery: Unrecognized name BigQuery: Syntax error / Unrecognized name: customer_id at [3:8] (Did you mean customerId?)
Other ways to find it
Where this error sits
Origin: Platform & cloud. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Report a correction or suggest an improvement
Last updated 18 Nov 2026