Home » Android » android – Google Maps are not showing in signed apk

android – Google Maps are not showing in signed apk

Posted by: admin April 23, 2020 Leave a comment

Questions:

I know this is a common question and usually the solution is to generate a separate key for release. I’ve done it several times and my API key in developers console contains two different SHA1-fingerprints: one for debug from AndroidStudio and on for release from my own keystore. I have signed the app with the same keystore and enabled Google Maps Android API v2 in the console. But still the maps activity shows just the white screen with ‘Google’ in the left bottom corner.

Are there any suggestions how to solve the problem?

How to&Answers:

It sounds like you only have the API key entered in the debug google_maps_api.xml. Also, it sounds like you’re using the same API key for debug and release, but you still need to enter it in the google_maps_api.xml under the release folder as well as the one in the debug folder.

It’s a little confusing, because when the project is in Android view, you can only see the debug file (although it should have (debug) in parenthesis next to it in that view).

In order to modify the release version, switch to Project view by using the dropdown in the upper left of the Project Explorer. Then, expand app/src/, and you will see subfolders debug and release. Under there, you should see two separate google_maps_api.xml files under debug/res/values and release/res/values.

Make sure that the API key is populated in the google_maps_api.xml file under the release/res/values folder, since this is the one that will be used for the signed release apk.

enter image description here

Answer:

If you chose Google Play App Signing then your App’s SHA-1 will be different one when it will be released.

Because Google remove your uploaded certificate and then sign the App with a new one,

So you have to know the new SHA-1 key.

(You don’t have to follow the log for release and track the new SHA-1 generated)

enter image description here


You can compare the 2 SHA-1 keys.

Origin answer

Answer:

I did a lot of things to fix these but any solution not fix my problem
to fix these issue I did these things

  1. Create signed apk with new keystore file make sure that the you will create that in release mode
  2. After creating the signed apk you should note the keystore path where you save your keystore file.
  3. You also need to use your google map API key with your release mode and debug mode both, you can use same API key with both but make sure that you should add two different sha keys for your single api key on google console.
  4. You should go to use the path of bin folder of java from c drive because keystore tool is inside bin folder so
    suppose your file is like C:\Program Files\Java\jdk1.8.0_11\bin
    so you should follow this path to your android studio terminal
    change the path to C:\Program Files\Java\jdk1.8.0_11\bin
    and then type this command:

    keytool -list -v -keystore "/Users/NT/Desktop/generalkey.jks"(adress of your keystore file)
    
  5. Now by doing these you will get the sha key copy that key

  6. Go to google console/credentials
  7. Now go to your api you will see edit option go to edit and past your sha key into it and save it .
  8. Run your code.

Answer:

you are using a version of sha1. you need to again generate SHA1 using command prompt after making you apk signed.

Steps to regenerate SHA1 is go to cmd and give the command like below:

C:\Program Files\Java\jre1.8.0_91\bin>keytool -list -v -keystore 

“C:\Your key store path\keystores\android.jks”

1)go to your java in program file open java version like jre1.8.0

2)open bin folder and run command like above follwed by your key store path that you have generated when you generated the signed apk
after running this command on cmd you need to provide password of signed app and your SHA1 will be gerarated.

3)copy the sha1 and paste into console.developer with your package name within your api key.

Answer:

It’s too late to answer but may be helpful for others if they phase the same issue.

If adding key in the release did not work then please check your SHA key in your jks file and add the same key in google play google api console

To get released SHA open your terminal and type

Asad-MacBook-Air:~ asad$ keytool -list -v -keystore /your/path/keystore.jks

and then check SHA, it should be the same as it is used in google api console.