-
Notifications
You must be signed in to change notification settings - Fork 4k
firebase_auth: "Invalid PlayIntegrity token; does not pass basic integrity." on debug builds #17382
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
Comments
I forgot to include we are trying to sign into physical Android devices, not emulators. My device is a Pixel 8 on Android 14. Thanks again! |
Hi @kirstenkoa, thanks for the report. Did this work well with debug builds before you distributed to internal testing? |
@SelaseKay
I've have correctly setup my Debug app check token and sha's in "Firebase App Check". |
And I'm using a real physical device too, |
Did you guys find a solution to this? |
I got that error yesterday too, and came out of the blue. It was working perfectly before. |
It was working with debug builds previously. We were distributing our Android app through Firebase App Distribution and I'd say 95% of our testers were able to log in using phone number. Maybe we had bad timing but I just set up release builds on Wednesday and distributed a version through Google Play. At that point, release builds are able to log in successfully and pass the check, but now our debug builds are all getting this error. Thanks for your help! |
We also had a couple testers in India who have not been able to sign in. They are hitting a slightly different error, so I think it might not be related to this.
|
We worked our way around this, might help someone if using phone authentication. We re-created the test credentials for phone authentication on the console. This error does not occur if you use the test phone and OTP specified on the console. We were able to develop on those test credentials as dummy users and given that this happens only on debug builds, our users are able to authenticate from play store downloaded versions. Not a fix, but helped us to push out fixes and get the wheel spinning temporarily. |
Is there an existing issue for this?
Which plugins are affected?
Auth
Which platforms are affected?
Android
Description
Hello, I recently set up my Flutter project to be distributed to internal testers on Google Play following these instructions.
The main changes to our build.gradle file were adding the release signing and build configs:
After these changes, we were able to distribute to internal testers through Google Play and login using Phone Number through those builds.
However, now we are getting the following error on Android debug builds:
"Invalid PlayIntegrity token; does not pass basic integrity."
Our individual debug SHA256 are still the same and included in our Firebase project. The package name matches as well. The SHAs are also included in App Check Settings.
Is this a bug or are we missing a key piece of setup?
Thank you!
Reproducing the issue
In our main.dart file, we are initializing Firebase along with other dependencies
During authentication, we are calling Firebase Auth
Firebase Core version
3.13.0
Flutter Version
3.29.2
Relevant Log Output
status: { code: 3 message: "INVALID_APP_CREDENTIAL : Invalid PlayIntegrity token; does not pass basic integrity." }
Flutter dependencies
Expand
Flutter dependencies
snippetAdditional context and comments
No response
The text was updated successfully, but these errors were encountered: