This guide lists common error codes and descriptions related to Credential
Manager, and provides some information about their causes.

> [!NOTE]
> **Note:** The exceptions on this page apply to emulators as well. For additional error descriptions, see [androidx.credentials.exceptions](https://developer.android.com/reference/androidx/credentials/exceptions/package-summary).

| Error code and description | Cause |
|---|---|
| **android.os.TransactionTooLargeException** | This is caused by a [known issue](https://b.corp.google.com/issues/341690734) where the `credentialManager.getCredential()` API on Android 14 and higher fails to display the sign-in dialog when multiple Google Accounts are present on the device. This issue is specifically seen with `GetGoogleIdOption` and not `GetSignInWithGoogleOption`. This issue is fixed in Google Play services version 24.40.XX and higher. |
| **CreateCredentialCancellationException** Passkey registration or retrieval was canceled by the user. | The user has chosen not to create or use a credential. You can now adjust your UI to offer an alternative sign-in method or move on to the next steps in your process. |
| **GetCredentialCancellationException** | The credential retrieval process was terminated because the necessary user authorization was not obtained. While this most commonly occurs when a user manually cancels the sign-in flow, it can also signal that the request was not authorized due to technical constraints. Because this error indicates a lack of consent, don't automatically retry the request, as this creates a disruptive user experience. However, developers should monitor the frequency of this exception. A high volume of "cancellations" may actually indicate a misconfiguration---such as a missing or incorrect scope---that prevents the authorization UI from completing successfully. If you notice unexpected trends, review your request parameters and \[relying party\]\[2\] configuration. Note: The error message can differ based on the type of credential: - For passkeys, the error message can be "Passkey registration or retrieval was canceled by the user". - For Sign in with Google, the error message can be "Activity is cancelled by the user". |
| **CreateCredentialCustomException** or **GetCredentialCustomException** | When using a 3rd-party SDK to make API calls with a request object that subclasses `CreateCustomCredentialRequest` or `GetCustomCredentialOption`, you may encounter errors. If this occurs, check the SDK for custom exception type constants that match e.type. If no match is found, it is safe to either drop or log the exception. |
| **CreateCredentialInterruptedException** or **GetCredentialInterruptedException** | The operation may have been interrupted because the user navigated to settings to reconfigure password managers. Other reasons may also have contributed to the interruption. Please try the call again. |
| **CreateCredentialUnknownException** During save password, found password failure response from one tap 16: \[28431\] Skipping password saving since the user is likely prompted with Android Autofill. | This error only impacts Android 13 and earlier versions when Google is the designated Autofill provider. In such cases, users will receive a save prompt from Autofill, and the password will be stored in Google Password Manager. Importantly, credentials saved using Autofill with Google are bi-directionally synced with the Credential Manager API. Therefore, this error can be safely disregarded. |
| **CreatePublicKeyCredentialDomException \& GetPublicKeyCredentialDomException** | It's likely that the DOM exception contains a more specific `domError`. You can map it to a WebAuthn [`DomException`](https://w3c.github.io/webauthn/#sctn-dependencies) for further details. |
| **CreatePublicKeyCredentialDomException \& GetPublicKeyCredentialDomException** The incoming request cannot be validated. | The password manager's server doesn't recognize the app's package ID. This points to a potential issue with your server-side integration, specifically the [digital asset link setup](https://developer.android.com/identity/sign-in/credential-manager#add-support-dal). Double-check the accuracy of the package ID and SHA within your asset link file. |
| **CreatePublicKeyCredentialDomException**: Unable to create key during registration | This issue can arise when a user dismisses the screen lock dialog during registration. |
| **CreateCredentialNoCreateOptionException** | This specific exception indicates that the user does not have a valid password manager configured. This error is not user initiated manual cancellow flow but a separate failure. |
| **CreatePublicKeyDomException \& GetPublicKeyCredentialDomException** Passkey **registration** was canceled by the user. Passkey **retrieval** was canceled by the user. | This issue can arise when a user dismisses the fingerprint dialog during registration / retrieval of a passkey. |
| **GetCredentialProviderConfigurationException \& CreateCredentialProviderConfigurationException** **getCredentialAsync** no provider dependencies found **createCredentialAsync** no provider dependencies found | The `androidx.credentials:credentials-play-services-auth:<latest-version>` dependency is missing. |
| **GetCredentialUnsupportedException** or **CreateCredentialUnsupportedException** Your device doesn't support credential manager | Ensure your credentials library is updated to version 1.2.1 or higher. |
| **GetPublicKeyCredentialException** Failed to decrypt credential | This issue occurs when trying to use a passkey after logging out and back into Google Accounts. Instruct your user to sign back into their Google Account on their device. |
| **NoCreateOptionException** | This exception is expected behavior when a user does not have any passkey credentials set up on their device, or if they don't have a password manager configured. |
| **NoCredentialException** No matching credentials found | This exception is caused in the following situations: - `setFilterByAuthorizedAccounts` is set to true without authorized accounts on the device. - There are no signed-in accounts on the device (no accounts have been added or the accounts need reauthentication). - The bottomsheet UI does not appear if Sign-in prompts are disabled for any account on the device. This global setting, found under **Google Account Settings \> Sign in with Google**, must be enabled for the bottomsheet UI to display for any account. This does not impact the button flow. |
| Not able to create passkey due to encrypted data being locked | The user needs to reset their Chrome server side data. This data includes bookmarks and Chrome settings in addition to the saved passwords and passkeys. For more info on what data Chrome stores, go to [Chrome data in your account](https://chrome.google.com/sync). 1. Go to [chrome.google.com/sync](http://chrome.google.com/sync). 2. At the bottom, select **Clear Data**. 3. On the device, [turn Sync on in Chrome](https://support.google.com/chrome/answer/185277). |
| **On Begin Sign In Failure: 8**: Unknown internal error. | The device may not be set up properly with the Google Account. There might be an issue with how the passkey JSON is being created. Double-check the implementation for accuracy. |
| Unable to get sync account | Google Play services version 24.40.XX and later will provide more informative error codes. For example, instead of "Unable to get sync account", callers will now receive a cancellation error message. |