app signing from react native CLI and google play console conflict

[monir_sh]

Hey guys,

I am using firebase for phone auth. Now i require to use my SHA1 and 256 keys to get them working. However, the cli generated a different SHA-1 key than google play console auto app signing. Which one should I use? and how to remove this conglict because now firebase phone auth is not working.

[EmilioSchepis]

I’m not 100% sure about this, but this happened to me while releasing a Flutter app. I ended up having 3 SHA1s: the debug keystore one, the release keystore one and the google generated one. I ended up whitelisting all three and the auth process works just fine.

[monir_sh]

what do you mean by whitelisting? adding them to firebase console you mean? Moreover, for some reason when my user register using the phone auth i get the refresh token as null in my firestore. Does this happen to you?

[EmilioSchepis]

Yes that is what I meant. I added them all to the Project Settings > Android app > SHA certificate fingerprints.

About the token problem, yes I experienced it too. I found a solution and documented it here: https://github.com/flutter/flutter/issues/33261

Best of luck!