Firebase phone authentication is not working after upload app on playstore

Question

I have no idea why it is happening. My app works fine with debug apk and signed apk. I have added the SHA1 key to firebase console also. But when i uploaded my app and installed it from Play Store then it is not sending the OTP to my phone number. Please help!

Thanks in advance

Answer 1

Did you just enrolled for Google Play App Signing ? In that case your key has changed. You can get SHA1 of the key used to sign your apk from Play Store Console.

Answer 2

Use this steps you have successfully resolve all issues -:

1. Go to google play console
2. Release Management -> App Signing
3. copy SHA-1 certificate fingerprint in (App signing certificate) but no include (SHA1: )
4. Open Firebase console -> Project settings -> Add fingerprint
5. Paste your SHA-1 key
6. Now Reinstall your app from play

Answer 3

@HandyPawan's mentioned answer completely right here but as Google Console updated now the steps are -

1. Go to google play console
2. Release -> Setup -> App Integrity
3. copy SHA-1 certificate fingerprint in (App signing certificate) but no include (SHA1: )
4. Open Firebase console -> Project settings -> Add fingerprint
5. Paste your SHA-1 key
6. Now Reinstall your app from play

Answer 4

In my case, SHA-1 alone didn't work until I pasted my SHA-256.

Answer 5

复制SHA1密钥后，您是否在项目中下载了google-services.json ？

Answer 6

In my situation I uploaded to the Play Store signed with my existing SHAs, which have been set in my Firebase App fingerprints for a long time with SMS autocomplete working fine. I also see the same SHA keys listed in the Play Store for my app.

However now the SMS outbound txt looks different and shows my package name with "(unverified)", and no 11 digit hash at the end as before. Needless to say, the autocomplete is no longer working.

Can you confirm you are seeing the 11 char hash at the end of the SMS messages being received? There have been reports that long package names, along with the "(unverified)" appended, may be causing the message to truncate, thereby removing the ending hash.

In which case once verified the package name will be replaced with the app name, the "(unverified)" removed, which should shorten the overall message to include the end hash again.