Error codes

New: Play Integrity API now has two options for requesting verdicts. Standard API requests, new and in beta, are low latency and can be used on demand. Classic API requests take longer and should be made less frequently. You can decide whether your app makes standard requests, classic requests, or both.

This page lists some common error codes, what they represent, and how your app or game can respond to them.

Error code	Description	Your action
API_NOT_AVAILABLE	Integrity API is not available. Integrity API is not enabled, or the Play Store version might be old.	1) Make sure that the Play Integrity API is enabled in Google Play Console. 2) Ask the user to update Google Play Store.
NETWORK_ERROR	No available network was found.	Ask the user to check for network connectivity.
PLAY_STORE_NOT_FOUND	No official Play Store app was found on the device.	Ask the user to install or enable Google Play Store.
PLAY_STORE_VERSION_OUTDATED	Play Store app needs to be updated.	Ask the user to update Google Play Store.
PLAY_STORE_ACCOUNT_NOT_FOUND	No Play Store account is found on the device. Note that the Play Integrity API now supports unauthenticated requests. This error code is used only for older Play Store versions that lack support.	Ask the user to sign in to the Google Play Store.
CANNOT_BIND_TO_SERVICE	Binding to the service in the Play Store has failed. This can be due to having an old Play Store version installed on the device.	Ask the user to update the Google Play Store.
APP_NOT_INSTALLED	The calling app is not installed.	Something is wrong; possibly an attack. Non-actionable.
PLAY_SERVICES_NOT_FOUND	Play services is unavailable or needs to be updated.	Ask the user to install or enable Play Services.
PLAY_SERVICES_VERSION_OUTDATED	Play services needs to be updated.	Ask the user to update Google Play services.
TOO_MANY_REQUESTS	The calling app is making too many requests to the API and has been throttled.	Request to increase your daily maximum number of requests Retry with an exponential backoff.
REQUEST_HASH_TOO_LONG	The provided requestHash is too long. The requestHash length must be less than 500 characters.	Retry with a shorter requestHash.
GOOGLE_SERVER_UNAVAILABLE	Unknown internal Google server error.	Retry with an exponential backoff.
CLIENT_TRANSIENT_ERROR	Transient error has occurred on the client device. Supported as of library version 1.1.0 for the Kotlin and Java programming languages, Google Play Integrity Plugin for Unity 1.1.0 or higher and Play Core Native SDK 1.12.1 or higher.	Retry with an exponential backoff.
INTERNAL_ERROR	Unknown internal error.	Retry with an exponential backoff.
NONCE_TOO_SHORT	Nonce length is too short. The nonce must be a minimum of 16 bytes (before base64 encoding).	Retry with a longer nonce.
NONCE_TOO_LONG	Nonce length is too long. The nonce must be less than 500 bytes before base64 encoding.	Retry with a shorter nonce.
NONCE_IS_NOT_BASE64	Nonce is not of base64 web-safe no-wrap form.	Retry with correct nonce format.
CLOUD_PROJECT_NUMBER_IS_INVALID	The provided cloud project number is invalid.	Use the Cloud project number for the Cloud project for which you enabled Play Integrity API.
APP_UID_MISMATCH	The calling app UID (user ID) does not match the one from Package Manager.	Something is wrong; possibly an attack. Non-actionable.

Native-specific error codes

The INTEGRITY_ prefix is prepended to native error codes to avoid potential naming conflicts. Apart from the error codes listed above, the native API also includes the following error codes:

Error code	Description	Your action
INTEGRITY_INITIALIZATION_NEEDED	IntegrityManager is not initialized.	Invoke IntegrityManager_init() first.
INTEGRITY_INITIALIZATION_FAILED	There was an error initializing the Integrity API.	Retry with an exponential backoff. Consider filing a bug.
INTEGRITY_INVALID_ARGUMENT	Invalid argument passed to the Integrity API.	Retry with correct argument.

Retry logic on error

An app should retry API calls in case of certain error codes. Review all error codes, and check that the application retries when necessary with exponential backoff. The recommended retry strategy is:

1. After the first failure, start with an initial delay of 5 seconds before retrying.
2. Retry for a total of three attempts, increasing the delay exponentially each time (10s, 20s).

While performing these retry attempts, check for a network connection and don't overload the device.

If you continue to see errors after three attempts, treat the outcome as if the client has failed all integrity checks. The error can be for several reasons, including (but not limited to): an overloaded device, network connection issues, or an attempt by an attacker.