-
Notifications
You must be signed in to change notification settings - Fork 4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
🚀 [firebase_app_check] Support passing debugToken
as parameter similar to React Native App Check library
#11719
Comments
I'm willing to complete this issue myself and submit a PR for it. I just want to first make sure that this feature would actually be accepted by the Firebase / FlutterFire core maintainers, given the security implications. |
It's also useful for tests in CI. |
We really need this for debug tokens to be useful and maintainable. We're generating and updating our debug tokens via Terraform, but currently we can't use these in the Flutter apps as there is no method to supply our own token. @thedalelakes did you ever get to work on a PR for this? |
@josh-burton unfortunately I don't have the time to work on this at the moment. I ended up just turning off App Check enforcement in my dev environment. |
I think on IOS you can use point 4 from guideline |
What feature would you like to see?
In the React Native package for Firebase App Check, they created their own custom provider that essentially overrides the debug provider token. This allows a developer to specify a static, generated debug token in their code to use.
This is very convenient because, in the case where the developer must uninstall / reinstall the app, they can use the same debug token. Currently, a Flutter developer that installs a new version of the app must manually copy and paste the debug token from XCode / Logcat console output into their Firebase web console (and delete the old token), which becomes tedious when testing certain functionality that requires fresh installations of the application.
Relevant links & code:
The text was updated successfully, but these errors were encountered: