google signIn not working in release mode apk android

Question

In release mode, my google sign-in is not working, but it works fine in debug mode. I got a similar question from SO here, but I didn't get perfect solutions.

My handleSignInResult is coming false - How can this be fixed?

Go to Google console >> Select the Project >> Select Credentials from left menu >>Select OAuth client for Android type >> You can see the SHA1 key written over there, that may be the development one >> Replace it with release SHA1 >> Save. That's it!! — Sunit Kumar Samanta, Jan 17 '19 at 11:59

score 153 · Answer 1 · edited Jun 20 '20 at 09:12

153

Yesterday same problem occurred to me.

Google has released a new signing service in playstore publish console in which google will signin your app with his keystore. After signing , it will give you a new SHA which you have to add in your firebase account.

edited Jun 20 '20 at 09:12

Community

1
1

answered Jun 01 '17 at 12:15

HarshitG

2,449
2
15
13

4

This is perfect solution. you have to add app SHA1 and Play store also. – Asesha George Jul 17 '17 at 06:58
3

I just copied all SHA-1 keys to the Firebase Console from the page above, downloaded the google-services.json, compiled and works fine. – Péter Aradi Nov 12 '17 at 22:12
@HarshitG pls check my issue at https://stackoverflow.com/questions/55235295/google-signin-working-in-release-apk-but-not-on-play-store – Shikhar Mar 19 '19 at 07:05
4

Which SH1 needs to be added in firebase App signing or Upload certificate? Is it needed to download the google-service.json file, build release app and upload updated app to playstore again? – Nabin Dhakal May 16 '19 at 09:53
1

@Nbn Add both SHA1 – HarshitG Aug 05 '19 at 07:20
1

Ughh you just saved me so much trouble; thank you... So there's a separate SHA for adding an app and one for playstore? Interesting. Thank you – Brian Mahecha Jun 05 '20 at 05:18
1

I wish I could vote this one up like a hundred times!!! Thank you! I now understand ... there is an upload certificate and google manages the signing certificate for the store. Gradle's signingReport task of course doesn't give you the latter. – kristof.taveirne Nov 19 '20 at 06:37
do we need to upload again after adding play store sha1 on firebase? – user3219477 Dec 07 '20 at 19:27
@Oush I will send you my address... :-P – HarshitG Jan 26 '21 at 17:37
@HarshitG have u experienced invalid google token issue after all this steps? – Richa Shah May 10 '21 at 07:31
It is strange how google has not made easy access to App Signing page. I had to google for the specific link and could not find normally from the play-store developer console. Also, i don't think their doc regarding google sign in mentions the above step. Very misleading i would have thought from google's side. – Yogesh Aug 23 '21 at 09:40
1

For anyone looking in 2021+, it's now on Play console -> setup -> App integrity – Graciela Carrillo Oct 16 '21 at 20:17

Keshav Gera · Answer 2 · 2019-10-10T05:04:39.793

55

When you upload app on play store

After signing , it will give you a new SHA which you have to add in your firebase account.

Its Working HAPPY Coding Cheers

Add new SHA1 in https://console.firebase.google.com

Create Release SHA1 using Command Line

keytool -list -v -keystore "E:\Jsk_file\healthNickel" -alias healthNickel

keytool -list -v -keystore "E:\Jsk_file\YOUR_JKS_FILE_NAME" -alias YOUR_JKS_ALIAS_NAME

Enter keystore Password :- YOUR_KEYSTORE_PASSWORD

edited Oct 10 '19 at 05:04

answered Apr 05 '19 at 07:18

Keshav Gera

9,806
1
67
48

1

Thank you very much Keshav. I was using my signing key SHA-1 as the docs say. – Simão Garcia Nov 14 '19 at 12:17
1

Thank you Keshav adding google play SHA1 in firebase console solved the problem. I was using my keystore SHA1 before which was giving error. – Asad35Waheed Dec 12 '19 at 10:43
1

Working Perfect. Thanks a lot for this solution provided Step by Step – Satyam Gondhale Jun 16 '20 at 06:21
1

This is the solution that I need. – Braulio Soncco Jul 04 '20 at 14:31
1

I was missed a copy SHA1 from the Playstore console and add in Firebase console. – Anup Gupta Sep 03 '20 at 19:15
1

Finally, this solved this issue for me. Nowhere this critical piece of information is documented. – zeeshan Sep 22 '20 at 17:42
1

Passionate Android Learner. Like to Learn New Technical Stuff Everyday and share with world. – Keshav Gera Nov 05 '20 at 13:06
1

Thank you!. This worked for me. I added the SHA-1 and SHA-256 from the Google Play Console into my Firebase project. – Saad Zahoor May 30 '21 at 09:23
1

You saved my day! Thanks, Keshav. – Rubi Jun 01 '21 at 17:52

Janardhan R · Answer 3 · 2017-03-23T07:04:49.983

I had same problem, i did read some posts and was able to get work done by following below steps

Step 1) Please go to https://console.developers.google.com/apis/credentials?

Step 2) Click on create credentials ->select OAuth client ID ->select application type as Android

Step 3) then generate Signing-certificate fingerprint by writing below command in command prompt before that you should have keystore and its path

     keytool -exportcert -keystore "D:\PlayStore_keystore\myproject.jks" -list -v

Step 4) after click on enter you will be asked for

     Enter keystore password : 
     Enter password which you have used for creating keystore

Step 5) then it will give details regarding keystore like SHA1,SHA256,MD5 etc.

Step 6) Enter SHA1 as fingerprint and give packagename which is in manifest file

step 7) Click create you will get new OAuth client ID

step 8) now you have got client id you will need to get google-services.json file.

step 9) please goto https://console.firebase.google.com

step 10) if you already have project with that packagename ->go to overview ->click on menu icon where packagne name is written

step 11) select settings goto-> tab General-> there will be option called Add fingerprint

step 12) in step 5 you have got SHA1 paste that in certificate fingerprint and save it

step 13) now download new google-services.json file (as it conatins new client id ,certificate_hash etc)

step 14) paste that google-services.json file in app folder in your android project.

step 15) You are good to go...

what i did was go to the dashboard console and activated app signing with google, then uploaded my certificate and it signed it but generated a new set of has code values that i then used in the firebase console. This worked for me. so your answer provided me a hint since i understood what was wrong — Akah, Sep 06 '17 at 15:30

score 31 · Accepted Answer · answered May 03 '16 at 11:31

31

Make sure you follow all the steps specified in the Guide

. If need be, create a new OAuth Client, new configuration file (the google-services.json) file and do everything step-by-step.

Also try adding a Web Client giving the same credentials. And for Android as well as Web client give both the SHA1 for debug as well as the release keystores. In Android Studio, at extreme left you will see a tab saying "Build Variants". Select the release mode there and do everything after that.

answered May 03 '16 at 11:31

huskygrad

975
1
7
21

1

it worked...i created new OAuth Client where i used release apk SHA1 key. – Elizabeth May 04 '16 at 05:09
1

I have a doubt...if i want to edit my code like add new features i will convert it to debug mode..then what happen to my OAuth Client...which was made using release SHA1 key right??? – Elizabeth May 04 '16 at 05:11
You can add multiple SHA1 in the console. And If it worked earlier in debug mode, it should work again. – huskygrad May 04 '16 at 05:13
I keep coming back to this answer. I have to use the Web key instead of the Android key. – joe May 02 '17 at 01:23
1

@Sanket I could not understand your second para "Also try adding a Web...". Could you please elaborate – Shikhar Mar 19 '19 at 06:58
@ShikharJaiswal I meant the Type as Web Application. But please check the steps for the newer app signing service. – huskygrad Apr 19 '19 at 07:39
Thanks, i just copy the SHA-1 from google console and i paste it in the firebase project settings and then it worked!, thanks again – GSepetadelis May 20 '21 at 14:04

score 6 · Answer 5 · answered Aug 08 '18 at 05:27

6

Because you are asking about release version of android so I assume you already have signed your application with keystore. So in order to obtain the SHA1 of your release app.

Go to your /bin in JDK directory.
And run the following command in your cmd.

keytool -list -v -keystore "key store path" -alias "key alias"

This command will give you all the required details of your release version. Copy the SHA1 string and add it to your firebase console.

You are good to go.

answered Aug 08 '18 at 05:27

Zankrut Parmar

1,652
1
11
25

1

https://stackoverflow.com/questions/6211919/errorkeytool-is-not-recognized-as-an-internal-or-external-command-operable-p If keytool is not recognized – user3156040 Oct 04 '19 at 01:33
1

thanks a ton man, I had my key.jks file I ran this command and got the sha1 and added to firebase console and that worked like charm – Mahesh Jamdade Dec 29 '19 at 04:58
also it is important to remember that when we release a new version to the playstore the new hash has to be added to the firebase console – Mahesh Jamdade Dec 29 '19 at 09:09

Makarand · Answer 6 · 2020-05-01T06:47:27.923

3

Ok I struggled with this and finally I found the solution here it is:

First of all there are three SHA1 keys

Debug SHA1 key
Release SHA1 key
SHA1 key when you google play sign your app

Here you can get debug and release keys and for third key check HarshitG's answer. There is App signing certificate, this is that key.

Gather those three keys and add them in firebase console under SHA certificate fingerprints

Then Download the google-services.json file and add it in your YOUR_PROJECT_NAME/project/app/ [you'll see it if you change the view to Project from Android]

Rebuild, generate release apk and enjoy :)

edited May 01 '20 at 06:47

answered Apr 26 '20 at 03:28

Makarand

827
8
18

That helped, thank you! Good thing is we need to add keys in Firebase console only, we don't need to add them to Google Cloud Console. In the Cloud Console, they are propagated automatically by and from Firebase. – Liker777 Jun 12 '21 at 02:43

Adeel Turk · Answer 7 · 2020-06-27T13:32:55.737

2

Whenever you are using any google api you must add your release hash key on the app you generated in google developer console if you have added hash key for debug.

edited Jun 27 '20 at 13:32

answered May 03 '16 at 08:58

Adeel Turk

887
8
23

u need to create pass your keystore path instead of debug keystore this is tutorial https://www.youtube.com/watch?v=cWDM0lZl_C0 – Adeel Turk May 03 '16 at 09:40
i created SHA1 key for my release apk using this https://developers.google.com/android/guides/client-auth then added to developer console..where i already iave a SHA1 key..whether i should delete that?? or just add this one too??? – Elizabeth May 03 '16 at 09:44
u can add new it does'nt matter – Adeel Turk May 03 '16 at 09:44
when you hit api using debug apk then that specif hash key wil be used and vice versa for released or signed apk – Adeel Turk May 03 '16 at 09:45
yeah i did everything like that..but still handleSignInResult is coming false :( – Elizabeth May 03 '16 at 09:50
hmmmmm i tried my best .well I think you should share your code as well. May be some one could help you more – Adeel Turk May 03 '16 at 09:52
:( shoo... what to do :( now – Elizabeth May 03 '16 at 10:06

Gene Bo · Answer 8 · 2018-05-04T23:57:25.147

For a Release (aka, Signed) APK - if you are only deploying to Firebase, you need to add the SHA1 for the same keystore file you used to sign the app.

After successfully adding the SHA1 into the Firebase Project console , get the latest google-services.json and update your project's module local copy.

I didn't see any docs on this so far (seems it's something you have to dig for); found it to be tricky stuff. Lot's of answers on SO. Found the Firebase deployment solt. thanks to:

Answer in this thread to update SHA1 on Google Play, it gave me the idea maybe I need to fix something with SHA1: https://stackoverflow.com/a/44307293/2162226
How to get the SHA1 for a signed APK: https://stackoverflow.com/a/34933381/2162226

score 1 · Answer 9 · answered Jun 12 '20 at 04:52

1

in the terminal go to the project folder->android-> paste this command and hit enter ./gradlew signingReport . this will generate set of keys for you .
Then copy the SHA1 and SHA256 keys under release release label.
add them in to your Firebase settings keys section.
Download the googleServices.json and replace your existing googleServices.json with the new one and build the apk again.

hope this helped.

answered Jun 12 '20 at 04:52

CHANDUKA SAMARASINGHE.

195
2
8

Thank you so much! – mahesh Feb 11 '21 at 17:40

score 0 · Answer 10 · answered Sep 29 '19 at 02:23

0

If you have two or more firebase projects or the google cloud project, there may be a duplicate SHA1. If such conditions have been explained in this link.

https://support.google.com/firebase/answer/6401008?authuser=0

answered Sep 29 '19 at 02:23

Latief Anwar

1,533
14
26

score 0 · Answer 11 · answered Jan 14 '22 at 10:01

Best And fastest way to fix login social media by flutter application using firebase after upload the app in google play to solve problem go to google play console than setup > app integrity > from App signing key certificate copy sha1& sha256 and past in firebase account in android app add new sha1 and sha256 . for facebook error login also copy sha1 from App signing key certificate in google play console go to this website : http://tomeko.net/online_tools/hex_to_base64.php past in hex string and click covert than copy output base 64 and past inside app setting in facebook development

that's all

score 0 · Answer 12 · answered Feb 25 '22 at 12:50

CAUTION

If exist you put more than one identifier for the same 'signingReport' (copy SHA1 and SHA256 from the same report object) this isn't work, keep this im mind.

This works for me:

Remove all SHA1 in firebase
Run ./gradlew signingReport in android folder and get SHA1 from debug mode.
Run this commmand with your data: keytool -list -v -keystore your_absolute_path_to_keystore -alias your_alias_from_keystore

(After that you will be promped to digit the password of key and it wil generate your SHA1 + SHA256 and other infos.)

Copy only SHA1 and paste it in firebase.
Download google-services.json again and move it to your android/app

google signIn not working in release mode apk android

12 Answers12

Linked