Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Firebase phone auth failing on app already in production with status code 17028

We are using firebase phone authentication to authenticate our users. We've been using it for over a year now.

Today at 13:00 GMT, new users are receiving 17028 An invalid safety_net_token was passed after entering their phone number.

I tried to verify each of the causes I found on the firebase docs:

  1. Verifying the SHA1 and SHA256 on the firebase console (We use the fingerprints that are on the play store console)
  2. Verifying the package name

The last app update was on October 1st and since then thousands of users created an account with Firebase Auth and there were no configuration changes on the firebase console.

Upon looking at other StackOverflow questions, the error we are getting is not the same as 17028 A safety_net_token was passed, but no matching SHA-256 was registered in the Firebase console. Please make sure that this application's packageName/SHA256 pair is registered in the Firebase Console Even though it is the same error code, in our case, it says an invalid token was passed.

We are using firebase with react-native-firebase module.

EDIT: After disabling Android device verification API from Google Cloud Console the verification is now working but with no device verification. (Users have to verify they're not robots with a CAPTCHA).

like image 568
Reda Avatar asked Oct 17 '21 14:10

Reda


People also ask

What is phone authentication Firebase?

You can use Firebase Authentication to sign in a user by sending an SMS message to the user's phone. The user signs in using a one-time code contained in the SMS message.

How do I remove Captcha verification from Firebase phone auth using Android?

Don't forget to go in Firebase Project Settings > App check > and Register firebase project in SafetyNet and Play Integrity register with default time token 1 hour and u will remove reCaptcha from phone auth OTP!


1 Answers

Update: It is working fine now, and the outage has been fixed.

enter image description here

It looks to be a firebase internal issue, and the only solution now is to disable "Android Device Verification" and all your users will see the Recaptcha page.

check https://status.firebase.google.com/ https://status.firebase.google.com/incidents/TYeQBVB4kkzyk2kE8vbP

enter image description here

enter image description here

like image 126
humazed Avatar answered Oct 13 '22 14:10

humazed