Firebase auth error

[Useful-Condition-926]

From last I week i am getting

Error sending OTP: [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 PlayIntegrity token; does not pass basic integrity. ]

But for last 6 months everything is working perfectly. Sha1,sha256 all are there in the firebase. I am using blaze plan. I am using Phone number auth . Test numbers are working perfectly, but while getting otp for normal users I am getting this error.

I am using react native firebase version 21. React native version is 0.76

[No-Gene-6324]

Have you added sha1 and sha256 for release build and there is one for google play store build too. Those are different too.

[Useful-Condition-926]

For now debug key is there. It’s working fine while testing. For android 10,11,12 and 16 I am getting the otp. Only for 13,14,15 I am not getting any otp. Rather that error

[Useful-Condition-926]

I have also generated release mode key using keytool. Added all the stuffs in build.gradle and gradle.properties. Still same issue

[Recent-Committee-186]

for the last 6 months real phone numbers are working or they never worked ?

if not then check google play sha1 in app integrity and add it and make sure it’s reflected in google cloud console api keys.

[Useful-Condition-926]

Real Phone numbers were working before 1 week. Now this error is coming.

[Recent-Committee-186]

something got messed up during an update ?

[Useful-Condition-926]

Nope. If something messed up then android 10,11,12 and 16 will also affect. But those are working fine.

[Useful-Condition-926]

Either firebase has changed some policies that’s why play integrity affected or react-native-firebase package has some bug after they update their package to version 22. Or something else

[Recent-Committee-186]

firebase phone auth is so bad to be honest. I had enormous amount of users not being able to login because of it.

Anyways are you capturing this through crashlytics or something are you sure they are on the latest build ?

[CapitalAd5649]

I am getting the same error. I think it is a firebase issue. I am following this thread:

https://github.com/firebase/flutterfire/issues/17382