react-native-firebase icon indicating copy to clipboard operation
react-native-firebase copied to clipboard

[Firebase/Firestore][I-FST000001] AppCheck failed - debug token

Open jadonhansen opened this issue 3 years ago • 1 comments

Discussed in https://github.com/invertase/react-native-firebase/discussions/6442

Originally posted by jadonhansen August 2, 2022 I am trying to obtain my AppCheck debug token from the Xcode logs and from the adb command output but I am getting the following error: [Firebase/Firestore][I-FST000001] AppCheck failed: 'The operation couldn’t be completed. (com.apple.devicecheck.error error 0.)'.

I am seeing the traffic appear in the firebase console App Check section under: "Unverified: Invalid requests", which proves that the AppCheck package is installed correctly. Note: I have not enforced the App Check yet via the console.

I have done the following:

  1. Installed AppCheck package
  2. Added AppAttest to Signing & Capabilities in Xcode.
  3. From my Apple developer account I added a new key (with devicecheck) enabled and its relevant ID and team ID to the firebase console. (So this enabled DeviceCheck and App Attest on firebase console for me)
  4. For Android I registered both my sha-256 for production and debug builds. (Enabling both SafetyNet and Play Integrity for me)
  5. In GCP I have 'Firebase App Check API' enabled for both my iOS and Android keys. And "Google Play Integrity API" enabled for Android key.

For iOS however, I do have a different team ID for debug signing (yes, this is a thing from Apple) which may be a reason why it is not working on iOS. Unfortunately I can only register one team ID on firebase console.

But I am unsure as to why it is not working for Android..?

jadonhansen avatar Aug 05 '22 07:08 jadonhansen

Moved this to an issue since I wasn't getting any responses in the discussion

jadonhansen avatar Aug 05 '22 07:08 jadonhansen

Hello 👋, to help manage issues we automatically close stale issues.

This issue has been automatically marked as stale because it has not had activity for quite some time.Has this issue been fixed, or does it still require attention?

This issue will be closed in 15 days if no further activity occurs.

Thank you for your contributions.

github-actions[bot] avatar Dec 05 '22 19:12 github-actions[bot]