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

| 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** or **GetCredentialCancellationException** 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. |
| **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. |
| **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. |
| **NoCredentialException** No matching credentials found | No matching credentials were found on the device. This is expected if the user has not previously saved any credentials. |
| 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. |