이 페이지에서는 Android 앱에서 기본 제공되는 Play Integrity 제공자로 App Check를 사용 설정하는 방법을 설명합니다. App Check를 사용 설정하면 사용자의 앱만 프로젝트의 Firebase 리소스에 액세스할 수 있습니다. 이 기능의 개요를 참조하세요.
현재 기본 제공되는 Play Integrity 제공 업체는 Google Play에서 배포된 Android 앱만 지원합니다. Play Integrity의 Play 외 기능을 사용하거나 자체 커스텀 제공자로 App Check를 사용하려면 커스텀 App Check 제공자 구현을 참조하세요.
페이지의 Play Integrity API 섹션으로 이동하여 Cloud 프로젝트 연결을 클릭한 후 Google Cloud 프로젝트 목록에서 Firebase 프로젝트를 선택합니다.
여기에서 선택하는 프로젝트는 앱을 등록하는 것과 동일한 Firebase 프로젝트여야 합니다(다음 단계 참고).
Firebase 제품에 적용을 사용 설정하면 등록된 앱만 제품의 백엔드 리소스에 액세스할 수 있으므로 일반적으로 프로젝트의 모든 앱을 등록해야 합니다.
선택사항: 앱 등록 설정에서 제공자가 발급한 App Check 토큰의 커스텀 TTL(수명)을 설정합니다. TTL은 30분에서 7일 사이의 값으로 설정할 수 있습니다. 이 값을 변경할 때는 다음 장단점을 고려하세요.
보안: TTL이 짧을수록 유출되거나 가로채인 토큰이 공격자에 의해 악용될 수 있는 기간이 줄어들므로 보안이 강화됩니다.
성능: TTL이 짧을수록 앱에서 증명을 더 자주 수행합니다. 앱 증명 프로세스는 실행될 때마다 네트워크 요청에 지연 시간이 추가되므로 짧은 TTL은 앱 성능에 영향을 줄 수 있습니다.
할당량 및 비용: 더 짧은 TTL과 빈번한 재증명으로 인해 할당량이 더 빨리 소진되며, 유료 서비스의 경우 더 많은 비용이 발생할 수 있습니다.
할당량 및 한도를 참조하세요.
대부분의 앱에 기본 TTL인 1시간이 적합합니다. App Check 라이브러리는 TTL 기간의 약 절반이 지났을 때 토큰을 새로고침합니다.
2. 앱에 App Check 라이브러리 추가
모듈(앱 수준) Gradle 파일(일반적으로 <project>/<app-module>/build.gradle.kts 또는 <project>/<app-module>/build.gradle)에서 Android용 App Check 라이브러리의 종속 항목을 추가합니다. 라이브러리 버전 관리 제어에는 Firebase Android BoM을 사용하는 것이 좋습니다.
dependencies{// Import the BoM for the Firebase platformimplementation(platform("com.google.firebase:firebase-bom:34.1.0"))// Add the dependencies for the App Check libraries// When using the BoM, you don't specify versions in Firebase library dependenciesimplementation("com.google.firebase:firebase-appcheck-playintegrity")}
Firebase BoM을 사용하지 않도록 선택한 경우에는 종속 항목 줄에 각 Firebase 라이브러리 버전을 지정해야 합니다.
앱에서 여러 Firebase 라이브러리를 사용하는 경우 모든 버전이 호환되도록 BoM을 사용하여 라이브러리 버전을 관리하는 것이 좋습니다.
dependencies{// Add the dependencies for the App Check libraries// When NOT using the BoM, you must specify versions in Firebase library dependenciesimplementation("com.google.firebase:firebase-appcheck-playintegrity:19.0.0")}
3. App Check 초기화
다른 Firebase SDK를 사용하기 전에 초기화 코드가 실행되도록 다음 초기화 코드를 앱에 추가합니다.
App Check에 앱을 등록한 후 App Check에서 일반적으로 유효한 것으로 분류하지 않는 환경에서 앱을 실행하려면(예: 개발 시 에뮬레이터 또는 지속적 통합(CI) 환경) 실제 증명 제공자 대신 App Check 디버그 제공자를 사용하는 앱의 디버그 빌드를 만들면 됩니다.
[null,null,["최종 업데이트: 2025-08-24(UTC)"],[],[],null,["This page shows you how to enable App Check in an Android app, using the\nbuilt-in Play Integrity provider. When you enable App Check, you help ensure\nthat only your app can access your project's Firebase resources. See an\n[Overview](/docs/app-check) of this feature.\n\nCurrently, the built-in Play Integrity provider only supports Android apps\ndistributed by Google Play. To use Play Integrity's off-Play features, or to use\nApp Check with your own custom provider, see\n[Implement a custom App Check provider](/docs/app-check/android/custom-provider).\n\n1. Set up your Firebase project\n\n1. [Add Firebase to your Android project](/docs/android/setup) if you haven't\n already done so.\n\n2. Enable the Play Integrity API:\n\n 1. In the [Google Play Console](https://play.google.com/console/developers/),\n select your app, or add it if you haven't already done so.\n\n 2. In the **Release** section, click **App integrity**.\n\n 3. Go to the **Play Integrity API** section of the page, click **Link Cloud project**,\n then select your Firebase project from the list of Google Cloud projects.\n The project you select here must be the same Firebase project as the one\n in which you register your app (see the next step).\n\n \u003cbr /\u003e\n\n | You must be an **Owner** of the project you want to link. Note that being a member of a group that has been assigned the Owner role is insufficient.\n\n \u003cbr /\u003e\n\n3. Register your apps to use App Check with the Play Integrity provider in\n the [**App Check**](//console.firebase.google.com/project/_/appcheck) section of\n the Firebase console. You will need to [provide the SHA-256 fingerprint](https://developers.google.com/android/guides/client-auth)\n of your app's signing certificate.\n\n You usually need to register all of your project's apps, because once you\n enable enforcement for a Firebase product, only registered apps will be able\n to access the product's backend resources.\n4. \u003cbr /\u003e\n\n \u003cbr /\u003e\n\n **Optional** : In the app registration settings, set a custom time-to-live\n (TTL) for App Check tokens issued by the provider. You can set the TTL\n to any value between 30 minutes and 7 days. When changing this value, be\n aware of the following tradeoffs:\n - Security: Shorter TTLs provide stronger security, because it reduces the window in which a leaked or intercepted token can be abused by an attacker.\n - 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.\n - Quota and cost: Shorter TTLs and frequent re-attestation deplete your quota faster, and for paid services, potentially cost more. See [Quotas \\& limits](/docs/app-check#quotas_limits).\n\n The default TTL of\n **1 hour**\n is reasonable for most apps. Note that the App Check library refreshes\n tokens at approximately half the TTL duration.\n\n \u003cbr /\u003e\n\n \u003cbr /\u003e\n\n2. Add the App Check library to your app In your **module (app-level) Gradle file** (usually `\u003cproject\u003e/\u003capp-module\u003e/build.gradle.kts` or `\u003cproject\u003e/\u003capp-module\u003e/build.gradle`), add the dependency for the App Check library for Android. We recommend using the [Firebase Android BoM](/docs/android/learn-more#bom) to control library versioning.\n\n\u003cbr /\u003e\n\n```carbon\ndependencies {\n // Import the BoM for the Firebase platform\n implementation(platform(\"com.google.firebase:firebase-bom:34.1.0\"))\n\n // Add the dependencies for the App Check libraries\n // When using the BoM, you don't specify versions in Firebase library dependencies\n implementation(\"com.google.firebase:firebase-appcheck-playintegrity\")\n}\n```\n\nBy using the [Firebase Android BoM](/docs/android/learn-more#bom),\nyour app will always use compatible versions of Firebase Android libraries.\n*(Alternative)*\nAdd Firebase library dependencies *without* using the BoM\n\nIf you choose not to use the Firebase BoM, you must specify each Firebase library version\nin its dependency line.\n\n**Note that if you use *multiple* Firebase libraries in your app, we strongly\nrecommend using the BoM to manage library versions, which ensures that all versions are\ncompatible.** \n\n```groovy\ndependencies {\n // Add the dependencies for the App Check libraries\n // When NOT using the BoM, you must specify versions in Firebase library dependencies\n implementation(\"com.google.firebase:firebase-appcheck-playintegrity:19.0.0\")\n}\n```\n\n\u003cbr /\u003e\n\n3. Initialize App Check\n\nAdd the following initialization code to your app so that it runs before you use\nany other Firebase SDKs: \n\nKotlin \n\n```kotlin\nFirebase.initialize(context = this)\nFirebase.appCheck.installAppCheckProviderFactory(\n PlayIntegrityAppCheckProviderFactory.getInstance(),\n)https://github.com/firebase/snippets-android/blob/391c1646eacf44d2aab3f76bcfa60dfc6c14acf1/appcheck/app/src/main/java/com/google/firebase/example/appcheck/kotlin/MainActivity.kt#L20-L23\n```\n\nJava \n\n```java\nFirebaseApp.initializeApp(/*context=*/ this);\nFirebaseAppCheck firebaseAppCheck = FirebaseAppCheck.getInstance();\nfirebaseAppCheck.installAppCheckProviderFactory(\n PlayIntegrityAppCheckProviderFactory.getInstance());https://github.com/firebase/snippets-android/blob/391c1646eacf44d2aab3f76bcfa60dfc6c14acf1/appcheck/app/src/main/java/com/google/firebase/example/appcheck/MainActivity.java#L22-L25\n```\n\nNext steps\n\nOnce the App Check library is installed in your app, start distributing the\nupdated app to your users.\n\nThe updated client app will begin sending App Check tokens along with every\nrequest it makes to Firebase, but Firebase products will not require the tokens\nto be valid until you enable enforcement in the App Check section of the\nFirebase console.\n\nMonitor metrics and enable enforcement\n\nBefore you enable enforcement, however, you should make sure that doing so won't\ndisrupt your existing legitimate users. On the other hand, if you're seeing\nsuspicious use of your app resources, you might want to enable enforcement\nsooner.\n\nTo help make this decision, you can look at App Check metrics for the\nservices you use:\n\n- [Monitor App Check request metrics](/docs/app-check/monitor-metrics) for Firebase AI Logic, Data Connect, Realtime Database, Cloud Firestore, Cloud Storage, Authentication, Google Identity for iOS, Maps JavaScript API, and Places API (New).\n- [Monitor App Check request metrics for Cloud Functions](/docs/app-check/monitor-functions-metrics).\n\nEnable App Check enforcement\n\nWhen you understand how App Check will affect your users and you're ready to\nproceed, you can enable App Check enforcement:\n\n- [Enable App Check enforcement](/docs/app-check/enable-enforcement) for Firebase AI Logic, Data Connect, Realtime Database, Cloud Firestore, Cloud Storage, Authentication, Google Identity for iOS, Maps JavaScript API, and Places API (New).\n- [Enable App Check enforcement for Cloud Functions](/docs/app-check/cloud-functions).\n\nUse App Check in debug environments\n\nIf, after you have registered your app for App Check, you want to run your\napp in an environment that App Check would normally not classify as valid,\nsuch as an emulator during development, or from a continuous integration (CI)\nenvironment, you can create a debug build of your app that uses the\nApp Check debug provider instead of a real attestation provider.\n\nSee [Use App Check with the debug provider on Android](/docs/app-check/android/debug-provider)."]]
