Introdução ao App Check com o App Attest em plataformas Apple
Mantenha tudo organizado com as coleções
Salve e categorize o conteúdo com base nas suas preferências.
Esta página mostra como ativar App Check em um app da Apple usando o
provedor integrado do App Attest. Ao ativar o App Check, você ajuda a garantir
que apenas seu app possa acessar os recursos do Firebase do seu projeto. Consulte a
Visão geral desse recurso.
O App Check usa o App Attest
para verificar se as solicitações para os serviços do Firebase são provenientes do seu aplicativo autêntico.
No momento, o App Check não usa o App Attest para
analisar riscos de fraude.
Registre seus apps para usar App Check com o provedor do App Attest na seção
App Check do
console Firebase.
Geralmente, é necessário registrar todos os apps do projeto porque, depois de ativar
a aplicação de um produto do Firebase, somente apps registrados poderão
acessar os recursos de back-end do produto.
Opcional: nas configurações de registro do aplicativo, defina um time to live (TTL) personalizado para os tokens do App Check emitidos pelo provedor. É possível definir o TTL
como qualquer valor entre 30 minutos e 7 dias. Ao mudar esse valor, esteja
ciente das seguintes compensações:
Segurança: os TTLs mais curtos oferecem maior segurança, porque reduzem a
janela em que um token vazado ou interceptado pode ser usado por um
invasor.
Desempenho: TTLs mais curtos significam que seu app realizará atestados com mais
frequência. Como o processo de atestado do app adiciona latência às solicitações
de rede sempre que é executado, um TTL curto pode afetar o desempenho
do app.
Cota e custo: TTLs mais curtos e novos atestados frequentes esgotam sua
cota mais rapidamente e, para serviços pagos, podem custar mais.
Consulte Cotas e limites.
O TTL padrão de
uma hora
é razoável para a maioria dos apps. A biblioteca App Check atualiza
os tokens em aproximadamente metade da duração do TTL.
2. Adicionar a biblioteca App Check ao app
Adicione a dependência de App Check ao Podfile do projeto:
Depois que a biblioteca App Check estiver instalada no seu app, comece a distribuir o
app atualizado para os usuários.
O app cliente atualizado vai começar a enviar tokens do App Check em todas
as solicitações feitas ao Firebase, mas os produtos dessa plataforma não exigirão que os tokens
sejam válidos até que você ative a aplicação obrigatória na seção App Check do
Console do Firebase.
Monitorar métricas e ativar a aplicação obrigatória
Antes de ativar a aplicação obrigatória, verifique se isso não
vai afetar seus usuários legítimos. Por outro lado, se você perceber um
uso suspeito dos recursos do seu app, convém ativar a aplicação obrigatória antes do previsto.
Para tomar essa decisão, analise as métricas do App Check nos
serviços usados:
Monitore as métricas de solicitação App Check para
Firebase AI Logic, Data Connect, Realtime Database, Cloud Firestore, Cloud Storage, Authentication, Google Identity para iOS, API Maps JavaScript e API Places (novo).
Assim que você entender como o App Check vai afetar seus usuários e estiver tudo pronto para
prosseguir, ative a aplicação obrigatória do App Check:
Ativar a aplicação de App Check para
Firebase AI Logic, Data Connect, Realtime Database, Cloud Firestore, Cloud Storage, Authentication, Google Identity para iOS, API Maps JavaScript e API Places (novo).
Se depois de registrar seu aplicativo no App Check você quiser executá-lo
em um ambiente que o App Check normalmente não classificaria como válido,
como um simulador durante o desenvolvimento ou em uma integração contínua (CI), crie um build de depuração do seu app que use o provedor de depuração do App Check em vez de um provedor de atestado real.
[[["Fácil de entender","easyToUnderstand","thumb-up"],["Meu problema foi resolvido","solvedMyProblem","thumb-up"],["Outro","otherUp","thumb-up"]],[["Não contém as informações de que eu preciso","missingTheInformationINeed","thumb-down"],["Muito complicado / etapas demais","tooComplicatedTooManySteps","thumb-down"],["Desatualizado","outOfDate","thumb-down"],["Problema na tradução","translationIssue","thumb-down"],["Problema com as amostras / o código","samplesCodeIssue","thumb-down"],["Outro","otherDown","thumb-down"]],["Última atualização 2025-09-05 UTC."],[],[],null,["This page shows you how to enable App Check in an Apple app, using the\nbuilt-in App Attest 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\nApp Check uses [App Attest](https://developer.apple.com/documentation/devicecheck/establishing_your_app_s_integrity)\nto verify that requests to Firebase services are coming from your authentic app.\nApp Check currently does not use App Attest to\n[analyze fraud risk](https://developer.apple.com/documentation/devicecheck/assessing_fraud_risk).\n\nIf you want to use App Check with your own custom provider, see\n[Implement a custom App Check provider](/docs/app-check/ios/custom-provider).\n| **Note:** If you are adding App Attest to a production app with a large active user base, Apple recommends [gradually onboarding users](https://developer.apple.com/documentation/devicecheck/preparing-to-use-the-app-attest-service#Onboard-users-gradually) to avoid encountering quota limits.\n\n1. Set up your Firebase project\n\n1. You will need Xcode 12.5+ to use App Attest.\n\n2. [Add Firebase to your Apple project](/docs/ios/setup) if you haven't already\n done so.\n\n3. Register your apps to use App Check with the App Attest provider in the\n [**App Check**](//console.firebase.google.com/project/_/appcheck) section of the\n Firebase console.\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\n\n1. Add the dependency for App Check to your project's `Podfile`:\n\n ```\n pod 'FirebaseAppCheck'\n ```\n\n Or, alternatively, you can use [Swift Package\n Manager](/docs/ios/swift-package-manager) instead.\n\n Make sure you're also using the latest version of any other Firebase SDKs\n you depend on.\n2. Run `pod install` and open the created `.xcworkspace` file.\n\n3. In Xcode, add the **App Attest** capability to your app.\n\n4. In your project's `.entitlements` file, set the App Attest environment to\n `production`.\n\n | **Note:** The App Check beta currently doesn't accept tokens generated in the App Attest sandbox environment.\n\n3. Initialize App Check\n\nYou will need to initialize App Check before you use any other Firebase\nSDKs.\n\nFirst, write an implementation of `AppCheckProviderFactory`. The specifics of\nyour implementation will depend on your use case.\n\nFor example, If you only have users on iOS 14 and later, you can simply always\ncreate `AppAttestProvider` objects: \n\nSwift\n\n\n**Note:** This Firebase product is not available on watchOS targets. \n\n```swift\nclass YourSimpleAppCheckProviderFactory: NSObject, AppCheckProviderFactory {\n func createProvider(with app: FirebaseApp) -\u003e AppCheckProvider? {\n return AppAttestProvider(app: app)\n }\n}\n```\n\n\u003cbr /\u003e\n\nObjective-C\n\n\n**Note:** This Firebase product is not available on watchOS targets. \n\n```objective-c\n@interface YourSimpleAppCheckProviderFactory : NSObject \u003cFIRAppCheckProviderFactory\u003e\n@end\n\n@implementation YourSimpleAppCheckProviderFactory\n\n- (nullable id\u003cFIRAppCheckProvider\u003e)createProviderWithApp:(nonnull FIRApp *)app {\n return [[FIRAppAttestProvider alloc] initWithApp:app];\n}\n\n@end\n```\n\nOr, you can create `AppAttestProvider` objects on iOS 14 and later, and fall\nback to `DeviceCheckProvider` on earlier versions: \n\nSwift\n\n\n**Note:** This Firebase product is not available on watchOS targets. \n\n```swift\nclass YourAppCheckProviderFactory: NSObject, AppCheckProviderFactory {\n func createProvider(with app: FirebaseApp) -\u003e AppCheckProvider? {\n if #available(iOS 14.0, *) {\n return AppAttestProvider(app: app)\n } else {\n return DeviceCheckProvider(app: app)\n }\n }\n}\n```\n\n\u003cbr /\u003e\n\nObjective-C\n\n\n**Note:** This Firebase product is not available on watchOS targets. \n\n```objective-c\n@interface YourAppCheckProviderFactory : NSObject \u003cFIRAppCheckProviderFactory\u003e\n@end\n\n@implementation YourAppCheckProviderFactory\n\n- (nullable id\u003cFIRAppCheckProvider\u003e)createProviderWithApp:(nonnull FIRApp *)app {\n if (@available(iOS 14.0, *)) {\n return [[FIRAppAttestProvider alloc] initWithApp:app];\n } else {\n return [[FIRDeviceCheckProvider alloc] initWithApp:app];\n }\n}\n\n@end\n```\n\n\u003cbr /\u003e\n\nAfter you have implemented a `AppCheckProviderFactory` class, configure\nApp Check to use it: \n\nSwift\n\n\n**Note:** This Firebase product is not available on watchOS targets. \n\n```swift\nlet providerFactory = YourAppCheckProviderFactory()\nAppCheck.setAppCheckProviderFactory(providerFactory)\n\nFirebaseApp.configure()\n```\n\n\u003cbr /\u003e\n\nObjective-C\n\n\n**Note:** This Firebase product is not available on watchOS targets. \n\n```objective-c\nYourAppCheckProviderFactory *providerFactory =\n [[YourAppCheckProviderFactory alloc] init];\n[FIRAppCheck setAppCheckProviderFactory:providerFactory];\n\n[FIRApp configure];\n```\n\n\u003cbr /\u003e\n\nNext steps\n\nOnce the App Check library is installed in your app, start distributing the\nupdated app to your users.\n| **Note:** If you are adding App Attest to a production app with a large active user base, Apple recommends [gradually onboarding users](https://developer.apple.com/documentation/devicecheck/preparing-to-use-the-app-attest-service#Onboard-users-gradually) to avoid encountering quota limits.\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 a simulator 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 Apple platforms](/docs/app-check/ios/debug-provider)."]]