Play Integrity API Library release notes

This page explains what's in the recent updates to the Maven repository for the Play Integrity API.

1.6.0 (2025-11-20)

• Documentation updates for methods and constants.
• Added webViewRequestMode parameter in PrepareIntegrityTokenRequest. This parameter is only used for advanced system use cases, such as for WebView implementations, and must be left unspecified by app, game, and SDK developers.

1.5.0 (2025-08-28)

• Added new Play remediation dialog codes, GET_INTEGRITY and GET_STRONG_INTEGRITY, that you can trigger in your app to help users fix MEETS_DEVICE_INTEGRITY, MEETS_STRONG_INTEGRITY and other verdict issues. The new dialogs can also resolve some exceptions encountered during Integrity API requests.
• Introduced new showDialog method in IntegrityManager and StandardIntegrityManager for triggering all types of remediation dialogs. The showDialog method in IntegrityTokenResponse and StandardIntegrityToken has been deprecated.
• Increased minimum required Android API level to 23 for Standard and Classic requests.

1.4.0 (2024-07-29)

• Added new dialog codes for Play remediation dialog that you can trigger when app access risk detects capturing or controlling apps.
• Added support for app access risk signal in Standard API requests and an option to opt out from app access risk on a per-request basis.
• Improved detection of PLAY_STORE_VERSION_OUTDATED errors.
• Increased minimum required Android API level to 21 for Standard and Classic requests.

1.3.0 (2023-11-14)

• Added support for Play remediation dialog that you can trigger when the user is unlicensed for your app.
• New error codes for Standard API requests:
  • CLIENT_TRANSIENT_ERROR. This indicates that a transient error has occurred on the device while preparing an integrity token provider. Developers should retry with exponential backoff.
  • INTEGRITY_TOKEN_PROVIDER_INVALID. This indicates that a prepared integrity token has become invalid. Developers should prepare a new integrity token provider.

1.2.0 (2023-07-31)

• Added support for Standard API requests.

1.1.0 (2023-01-25)

• New Error Code: CLIENT_TRANSIENT_ERROR. This indicates that a transient error has occurred on the device. Developers should retry with exponential backoff.
• Internal request generated by the library now contains the library version. This allows for customized responses based on the version in use.

1.0.2 (2022-09-27)

• Documentation updates for API methods and error codes.
• Added request timestamp for internal latency measurement purposes.

1.0.1 (2022-03-09)

• Improvements to error handling.
• Minor change to simplify Unity client library integration.

1.0.0 (2022-02-14)

• Initial release.