What does the Firebase error auth/user-not-found mean?

auth/user-not-found means there is no user record matching the supplied identifier, typically during email/password sign-in. For security you should show a generic 'invalid email or password' message rather than revealing whether the account exists, since auth/wrong-password leaks the same information.

How do I fix a Firestore permission-denied error?

permission-denied means your Firestore Security Rules rejected the read or write. Check the rules in the Firebase console against the authenticated user's claims and the document path. Test with the Rules Playground; the error is intentional and the fix is almost always in the rules, not the client code.

What causes auth/email-already-in-use?

auth/email-already-in-use occurs when you call createUserWithEmailAndPassword for an email that already has an account. Either route the user to sign-in instead, or use account linking if they are adding an email/password credential to an existing provider-based account.

What is the difference between storage/unauthorized and storage/object-not-found?

storage/unauthorized means Cloud Storage Security Rules denied access to the path for the current user. storage/object-not-found means the rules allowed access but no file exists at that path. Fix the first by adjusting rules or auth; fix the second by checking the path or uploading the object.

Is anything I search uploaded?

No. The full error index and the search run entirely in your browser. Nothing you type is sent to any server.

Firebase Error Codes Reference

This is a searchable reference for Firebase SDK error codes across the four products you hit most — Authentication (auth/*), Cloud Firestore, Cloud Storage (storage/*), and the Realtime Database. Each entry names the product, explains the meaning, and gives the fix, so you can turn a cryptic code into a clear next step.

How it works

Firebase SDK errors throw a FirebaseError with a string code and a human message. The code is namespaced by product:

auth/...      Authentication (e.g. auth/wrong-password)
storage/...   Cloud Storage (e.g. storage/unauthorized)
permission-denied / unavailable / not-found   Firestore (gRPC status names)
PERMISSION_DENIED / disconnected               Realtime Database

Branch on error.code, not the localized message, because the message text changes between SDK versions and locales while the code is stable. Auth errors are the most common in client apps; many of them — auth/user-not-found, auth/wrong-password, auth/invalid-credential — should be collapsed into a single generic UI message so you never reveal whether an account exists.

Tips and example

Most Firestore and Storage failures are rules problems, not bugs — the SDK is correctly enforcing the access you configured:

permission-denied   → fix Firestore Security Rules / user claims
storage/unauthorized → fix Storage Security Rules for the path
auth/too-many-requests → back off; the device is temporarily blocked
auth/email-already-in-use → send the user to sign-in or link accounts
unavailable (Firestore) → transient; retry with backoff (offline ok)

Wrap auth calls in a try/catch and switch on the code to produce friendly copy. For Firestore, the unavailable code is transient (often offline) and safe to retry, whereas permission-denied is terminal until the rules change. Everything runs in your browser; nothing is uploaded.

Firebase Error Codes Reference

Email me this result

How it works

Tips and example