Error code search

The provided next page token in listUsers() is invalid. It must be a valid non-empty string.

The provided value for the password user property is invalid. It must be a string with at least six characters.

The password hash must be a valid byte buffer.

The password salt must be a valid byte buffer

The provided value for the phoneNumber is invalid. It must be a non-empty E.164 standard compliant identifier string.

The provided value for the photoURL user property is invalid. It must be a string URL.

The providerData must be a valid array of UserInfo objects.

The providerId must be a valid supported provider identifier string.

The session cookie duration must be a valid number in milliseconds between 5 minutes and 2 weeks.

The provided uid must be a non-empty string with at most 128 characters.

The user record to import is invalid.

The maximum allowed number of users to import has been exceeded.

An Android Package Name must be provided if the Android App is required to be installed.

A valid continue URL must be provided in the request.

Importing users with password hashes requires that the hashing algorithm and its parameters be provided.

The request is missing a Bundle ID.

The OAuth configuration client secret is required to enable OIDC code flow.

A uid identifier is required for the current operation.

The provided sign-in provider is disabled for your Firebase project. Enable it in the Security > Authentication > Sign-in method tab of the Firebase console.

The provided phoneNumber is already in use by an existing user. Each user must have a unique phoneNumber.

No Firebase project was found for the credential used to initialize the Admin SDKs. Refer to Set up a Firebase project for documentation on how to generate a credential for your project and use it to authenticate the Admin SDKs.

One or more custom user claims provided to setCustomUserClaims() are reserved. For example, OIDC specific claims such as (sub, iat, iss, exp, aud, auth_time, etc.) should not be used as keys for custom claims.

The provided Firebase session cookie is expired.

The Firebase session cookie has been revoked.

The number of requests exceeds the maximum allowed.

The provided uid is already in use by an existing user. Each user must have a unique uid.

The domain of the continue URL is not whitelisted. Whitelist the domain in the Firebase Console.

The user account has been disabled by an administrator.

There is no existing user record corresponding to the provided identifier.

The operation was aborted, typically due to a concurrency issue such as a sequencer check failure or transaction abort. See the guidelines above for deciding between `FAILED_PRECONDITION`, `ABORTED`, and `UNAVAILABLE`. HTTP Mapping: 409 Conflict

The entity that a client attempted to create (e.g., file or directory) already exists. HTTP Mapping: 409 Conflict

The operation was cancelled, typically by the caller. HTTP Mapping: 499 Client Closed Request

Unrecoverable data loss or corruption. HTTP Mapping: 500 Internal Server Error

The deadline expired before the operation could complete. For operations that change the state of the system, this error may be returned even if the operation has completed successfully. For example, a successful response from a server could have been delayed long enough for the deadline to expire. HTTP Mapping: 504 Gateway Timeout

The operation was rejected because the system is not in a state required for the operation's execution. For example, the directory to be deleted is non-empty, an rmdir operation is applied to a non-directory, etc. Service implementors can use the following guidelines to decide between `FAILED_PRECONDITION`, `ABORTED`, and `UNAVAILABLE`: (a) Use `UNAVAILABLE` if the client can retry just the failing call. (b) Use `ABORTED` if the client should retry at a higher level. For example, when a client-specified test-and-set fails, indicating the client should restart a read-modify-write sequence. (c) Use `FAILED_PRECONDITION` if the client should not retry until the system state has been explicitly fixed. For example, if an "rmdir" fails because the directory is non-empty, `FAILED_PRECONDITION` should be returned since the client should not retry unless the files are deleted from the directory. HTTP Mapping: 400 Bad Request

Internal errors. This means that some invariants expected by the underlying system have been broken. This error code is reserved for serious errors. HTTP Mapping: 500 Internal Server Error

The client specified an invalid argument. Note that this differs from `FAILED_PRECONDITION`. `INVALID_ARGUMENT` indicates arguments that are problematic regardless of the state of the system (e.g., a malformed file name). HTTP Mapping: 400 Bad Request

Some requested entity (e.g., file or directory) was not found. Note to server developers: if a request is denied for an entire class of users, such as gradual feature rollout or undocumented allowlist, `NOT_FOUND` may be used. If a request is denied for some users within a class of users, such as user-based access control, `PERMISSION_DENIED` must be used. HTTP Mapping: 404 Not Found

Not an error; returned on success. HTTP Mapping: 200 OK

The operation was attempted past the valid range. E.g., seeking or reading past end-of-file. Unlike `INVALID_ARGUMENT`, this error indicates a problem that may be fixed if the system state changes. For example, a 32-bit file system will generate `INVALID_ARGUMENT` if asked to read at an offset that is not in the range [0,2^32-1], but it will generate `OUT_OF_RANGE` if asked to read from an offset past the current file size. There is a fair bit of overlap between `FAILED_PRECONDITION` and `OUT_OF_RANGE`. We recommend using `OUT_OF_RANGE` (the more specific error) when it applies so that callers who are iterating through a space can easily look for an `OUT_OF_RANGE` error to detect when they are done. HTTP Mapping: 400 Bad Request