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

AppCheck decks are not specific about required Apple / Firebase configuration requirements

Open mikehardy opened this issue 2 years ago • 1 comments

I don't recall seeing this in the setup documentation (https://rnfirebase.io/app-check/usage). Is those something I need to implement? If so, my team ID in Xcode changes and it doesn't match the team ID in my App Store Connect account.

This wording is not strong enough in our docs:

The official Firebase App Check documentation has more information, including about the iOS AppAttest provider, and testing/ CI integration, it is worth a read.

There are a few steps to do in order to get it working, where the steps are configuration on the Apple site and then taking the key from apple site to Firebase config site --> https://firebase.google.com/docs/app-check/ios/devicecheck-provider#project-setup

I'll peel this to an issue to make the docs more explicit, sorry for the confusion

If your team changes I suppose you'll need to work out some sort of multi-team configuration or similar. I personally use Fastlane for this sort of thing, and have a production config, and a development config with fully separate firestore apps they connect to, and I have the development firestore backend set to non-enforcing so the config isn't truly correct but I can test fine. Unfortunately I cannot really provide advice here - configuration of Xcode teams etc is definitely project specific, We could work together though to share whatever you learn in the form of better/updated docs here on the rnfirebase.io docs site

Originally posted by @mikehardy in https://github.com/invertase/react-native-firebase/discussions/6251#discussioncomment-2756255

mikehardy avatar May 16 '22 02:05 mikehardy

further comment in thread has explicit steps that worked: https://github.com/invertase/react-native-firebase/discussions/6251#discussioncomment-2763280

mikehardy avatar May 17 '22 03:05 mikehardy

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]

Not sure why the needs review tag isn't preventing stale but this needs review

mikehardy avatar Dec 05 '22 21:12 mikehardy

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 Jan 02 '23 22:01 github-actions[bot]