Platform
Firebase fixes
Firestore rules and Auth checks that fail once the app is public.
8 fixes, most common first.
- Rank 68. Firestore request failed because security rules denied it
A Firestore read or write fails after deploy? Firebase says every client request is checked against security rules, and a denied path fails the whole request.
- Rank 88. Sign in with Google fails on a custom domain
Google sign-in works on localhost and fails on the real domain? Add the origin, not a path, to Authorized JavaScript origins, and authorize the live hostname in Supabase or Firebase.
- Rank 91. Firestore: Missing or insufficient permissions
Firestore says Missing or insufficient permissions on a read after login? Security rules rejected that operation for the current user and path. A signed-in user can still be denied.
- Rank 103. Firebase auth/operation-not-allowed
Firebase returns auth/operation-not-allowed? That sign-in provider is not enabled. Turn it on in the Firebase console, then save.
- Rank 111. Firestore: a compound query does not map to an index
Firestore rejects a compound query with a range clause? That query does not map to an existing index. The error includes a link that creates the missing index.
- Rank 112. Firebase auth/invalid-credential
signInWithEmailAndPassword returns auth/invalid-credential? With Email Enumeration Protection on, Firebase says the email and password are invalid.
Keep going on your own.
The guides stay free. A deep leak report is $15. Fix packs are $24, or $49 for all three. There is no done-for-you repair.