Welcome to ShenZhenJia Knowledge Sharing Community for programmer and developer-Open, Learning and Share
menu search
person
Welcome To Ask or Share your Answers For Others

Categories

I have gone through numerous questions on SO about this issue but I am unable to figure out what my issue is. I have take the following steps:

  1. Created a key/keystore in Android Studio
  2. Signed the aab file with the key
  3. Upload the app to Play Store - opted in for app signing
  4. Retrieved the generated SHA-1 and SHA-256 values and pasted them in Firebase console
  5. Verified the values through signingReport in Android Studio

I've also added signingConfigs into my gradle build file. I confirmed that the keys in Firebase are for the release build.

Everything seems to be in order but I am not able to get into the OTP screen for the Phone Auth. Its been mightily frustrating. Any pointers would be much appreciated!


与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…
thumb_up_alt 0 like thumb_down_alt 0 dislike
292 views
Welcome To Ask or Share your Answers For Others

1 Answer

So, apart from updating the SHA-1 fingerprints in Firebase, you might have to update it in your Google Cloud API settings as well. This should apply in the event you have created restricted API keys. Just add the additional keys with the same package names and it should work.

I spent the good part of 1 day figuring this out.


与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…
thumb_up_alt 0 like thumb_down_alt 0 dislike
Welcome to ShenZhenJia Knowledge Sharing Community for programmer and developer-Open, Learning and Share
...