Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

After signed apk google plus login not working in Android? Is there any proguard option?

Before signing APK, Google Login was working fine. After signing APK, it's not working, always failure.

For that, are there any proguard settings that I have to do?

My SHA1 and all credentials are fine but still not working how to solve?

like image 544
Rakul Avatar asked Jun 17 '16 18:06

Rakul


3 Answers

  1. Go to the Google live play store account.
  2. Select your app.
  3. Select App signing tab in left side
  4. Copy both App signing certificate and Upload certificate's SHA 1 key.
  5. Then go to google Api console or firebase developer console --> then select your project.

FireBase: 1.Project over view --> project settings(setting icon right side) 2.Click on the Project settings then add your fingerPrint(SHA 1 Key which you had copied from Google live play store account).

Google Api Developer Console: Select your project. Click credentials tab on left side bar. Then select your api Key then click edit icon right side. Then add your SHA1 key. That's all.

like image 118
Mainak Devsinha Avatar answered Sep 28 '22 01:09

Mainak Devsinha


Finally i was created new key based on release SHA1, now google login and maps working fine after signed apk , no need to run keytool commands, in android studio takes care of everything. you have to follow steps that it.

Android Studio2.1.1 File->Project Structure->app(Left hand side)

->Signing(on top side)->(Click on green color + button and add your release keystore details) ->Build Types(next to the signing tap) and select release on left hand side then right hand side you will see the some fileds in that choose signing config to release then click ok.

Finally click Gradle tap right hand side, then Project name->project name->Tasks->android->singingReport(click on that) now your debug key and Release key was ready On RUN console check it

like image 31
Rakul Avatar answered Sep 28 '22 00:09

Rakul


That might be because you've added SHA1 of only debug keystore.

Add another SHA1 of production keystore and it will start working.
If you're using Linux of Mac OS, generate SHA1 like this.

keytool -list -v -keystore YOUR_PRODUCTION_KEYSTORE_PATH -alias androidproductionkey -storepass password -keypass password

For windows following should work.

keytool -list -v -keystore "YOUR_PRODUCTION_KEYSTORE_PATH" -alias androidproductionkey -storepass password -keypass password
like image 37
Alok Patel Avatar answered Sep 28 '22 02:09

Alok Patel