|
| 1 | +# @nativescript/firebase-app-check-debug |
| 2 | + |
| 3 | +```cli |
| 4 | +ns plugin add @nativescript/firebase-app-check-debug |
| 5 | +``` |
| 6 | + |
| 7 | +> **Warning**: The debug provider allows access to your Firebase resources from unverified devices. Don't use the debug provider in production builds of your app, and don't share your debug builds with untrusted parties. |
| 8 | +
|
| 9 | + |
| 10 | + |
| 11 | +> **Note**: (iOS) App Check requires you set the minimum iOS Deployment version in ios/Podfile to 11.0 or greater. |
| 12 | +
|
| 13 | + |
| 14 | +### What does it do |
| 15 | + |
| 16 | +App Check works alongside other Firebase services to help protect your backend resources from abuse, such as billing fraud or phishing. With App Check, devices running your app will use an app or device attestation provider that attests to one or both of the following: |
| 17 | + |
| 18 | +Requests originate from your authentic app |
| 19 | +Requests originate from an authentic, untampered device |
| 20 | +This attestation is attached to every request your app makes to your Firebase backend resources. |
| 21 | + |
| 22 | +[](https://www.youtube.com/watch?v=Fjj4fmr2t04) |
| 23 | + |
| 24 | +This App Check module has built-in support for using the following services as attestation providers: |
| 25 | + |
| 26 | +DeviceCheck on iOS |
| 27 | +SafetyNet on Android |
| 28 | +App Check currently works with the following Firebase products: |
| 29 | + |
| 30 | +Realtime Database |
| 31 | +Cloud Storage |
| 32 | +Cloud Functions (callable functions) |
| 33 | +The [official Firebase App Check documentation](https://firebase.google.com/docs/app-check) has more information, including about the iOS AppAttest provider, and testing/ CI integration, it is worth a read. |
| 34 | + |
| 35 | +## Usage |
| 36 | + |
| 37 | +### Activate |
| 38 | + |
| 39 | + |
| 40 | + |
| 41 | +```ts |
| 42 | +import { firebase } from '@nativescript/firebase-core'; |
| 43 | +import { AppCheck } from '@nativescript/firebase-app-check-debug'; |
| 44 | + |
| 45 | +AppCheck.setProviderFactory(); // call before the fb app is initialized |
| 46 | +firebase.initializeApp() |
| 47 | +.then(app =>{ |
| 48 | + firebase().appCheck().activate(true); |
| 49 | +}) |
| 50 | + |
| 51 | + |
| 52 | +``` |
| 53 | + |
| 54 | + The only configuration possible is the token auto refresh. When you call activate, the provider stays the same but the token auto refresh setting will be changed based on the argument provided. |
| 55 | + |
| 56 | +You must call activate prior to calling any firebase back-end services for App Check to function. |
| 57 | + |
| 58 | + |
| 59 | +### Automatic Data Collection |
| 60 | + |
| 61 | +App Check has an "tokenAutoRefreshEnabled" setting. This may cause App Check to attempt a remote App Check token fetch prior to user consent. In certain scenarios, like those that exist in GDPR-compliant apps running for the first time, this may be unwanted. |
| 62 | + |
| 63 | +If unset, the "tokenAutoRefreshEnabled" setting will defer to the app's "automatic data collection" setting, which may be set in the Info.plist or AndroidManifest.xml |
| 64 | + |
| 65 | + |
| 66 | +### Using App Check tokens for non-firebase services |
| 67 | + |
| 68 | +The [official documentation](https://firebase.google.com/docs/app-check/web/custom-resource) shows how to use getToken to access the current App Check token and then verify it in external services. |
| 69 | + |
| 70 | +## License |
| 71 | + |
| 72 | +Apache License Version 2.0 |
0 commit comments