Get started using App Check with Play Integrity on Android

This page shows you how to enable App Check in an Android app, using the built-in Play Integrity provider. When you enable App Check , you help ensure that only your app can access your project's backend resources. See an Overview of this feature.

The Play Integrity provider supports Android apps that are published on Google Play, outside Google Play, or both. If your use case requires Play Integrity features not implemented by App Check , or if you want to use App Check with your own custom provider, see Implement a custom App Check provider .

1. Set up your Firebase project

1. Add Firebase to your Android project if you haven't already done so.

2. Enable the Play Integrity API:

   1. In the Google Play Console , select your app, or add it if you haven't already done so.

   2. In the Releasesection, click App integrity.

   3. Go to the Play Integrity APIsection of the page, click Link Cloud project, then select your Firebase project from the list of Google Cloud projects. The project you select here must be the same Firebase project as the one in which you register your app (see the next step).

3. Register your apps to use App Check with the Play Integrity provider in the App Check section of the Firebase console. You will need to provide the SHA-256 fingerprint of your app's signing certificate.

   You usually need to register all of your project's apps, because once you enable enforcement for a Firebase product, only registered apps will be able to access the product's backend resources.

4. Optional: In the app registration settings, set a custom time-to-live (TTL) for App Check tokens issued by the provider. You can set the TTL to any value between 30 minutes and 7 days. When changing this value, be aware of the following tradeoffs:

   • Security: Shorter TTLs provide stronger security, because it reduces the window in which a leaked or intercepted token can be abused by an attacker.
   • Performance: Shorter TTLs mean your app will perform attestation more frequently. Because the app attestation process adds latency to network requests every time it's performed, a short TTL can impact the performance of your app.
   • Quota and cost: Shorter TTLs and frequent re-attestation deplete your quota faster, and for paid services, potentially cost more. See Quotas & limits .

   The default TTL of 1 hour is reasonable for most apps. Note that the App Check library refreshes tokens at approximately half the TTL duration.