[firebase_auth]: [firebase_auth/app-not-authorized] This app is not authorized to use Firebase Authentication. Please verify that the correct package name, SHA-1, and SHA-256 are configured in the Firebase Console. [ Invalid app info in play_integrity_token ] about flutterfire HOT 7 OPEN

Hello @Valent1, Thank you for reporting this issue. Could you please double-check that the SHA1 key you have entered is correct? Sometimes, incorrect SHA1 keys can lead to authentication issues. For more guidance, you might find these Stack Overflow links helpful:

1. This app is not authorized to use Firebase Authentication
2. Flutter Firebase Play Integrity Token Invalid App Info

These articles provide step-by-step solutions to similar problems and might help you resolve the issue. If the problem persists, please provide further details so we can assist you better.

from flutterfire.

Both SHA1 and SHA256 keys are correct. I verified them.

from flutterfire.

@Valent1 - SHA1 & SHA256 from play console into your Firebase console? Like this: https://stackoverflow.com/a/53513327/5681607

The error is saying something is misconfigured and specifically in the play integrity token.

from flutterfire.

Yes, exactly like that. See screenshot below.
Just to be clear, I have no issue with the Android app running in PRODUCTION mode, installed from the Google Play Store.
The issue arises when I am running the app from Android Studio or VSCode, in Debug, Profile or Release mode.
Those apps are not installed from the Play Store, so I don't see how the Google Play store app signing certificate plays any role here. You shouldn't use that certificate when the app runs locally in Debug, Profile or Release mode. Am I missing something here?

from flutterfire.

Any update on this? Any other debug steps that I should try?

from flutterfire.

Hi, even with the latest firebase_auth release, this will not work on Android emulator and on physical Android devices running in Debug, Profile or Release mode.

Do you need more information on my end? This is currently blocking my development,

from flutterfire.

Hello @Valent1,

I am currently experiencing the same issue. Although I have not yet identified the exact cause, I found that switching the emulator from Pixel 8 to Pixel 7 along with downgrading from Android 14 to Android 13, resolved the problem for me. This is just a temporary workaround, and I am still searching for the root cause and a more permanent solution.

Thanks

from flutterfire.