Google Maps not loading after publishing on play store even after updating SHA 1 fingerprint for release key

Question

A newbie here to google maps api and android app development. I am facing some strange issue and struggling with this from two days. I have developed an app in which I have used Google maps. I have launched the app to play store. The google map loads perfectly fine when I install the signed apk directly to mobile but not when I install through play store.

I have updated google maps api console with release key SHA 1 fingerprint. I am not able to find any solutions online also and did not get any support from google support team also. Somebody please help!

Ventricle

Probably you're using the fingerpint for debuggin. Please check this link – Neddra

Adding the SHA-1 fingerprint from App Signing certificate in play console to the credentials in google developers console should work. – Footboard

Answer 1

If u have enabled the App Signing Feature in the Developer Console, then it's clearly written in the documentation that the Upload Certificate is only needed by Google for authentication and that upload certificate is removed before installing the application on the user's phone. So, u also need to give the App Signing Certificate SHA under the key which you have enabled for Google Maps API. The App Signing Page is as I have attached the screenshot for your convenience... In the image I have marked which you need to give as additional credentials

Framing

Thank you Chandan Suri. I also figured out the same and it worked. – Ventricle

Your Welcome... Happy to help. – Framing

this valid answer!! – Subastral

Issue remains :( – Hugo

where to use this sh1 key ? – Hindoo

this key has to be used in a file present in the maps activity related file, there you need to paste your SSH key, then it would run in the release mode as well... – Framing

@ChandanSuri bro can u help me out where to put SHA-1 certificate fingerprint..?? – Player

Answer 2

Regarding the accepted answer: In the good old days you would create 2 API keys, one for debug and one for release. Each one used the relevant keystore SHA1 you have created. But due to "Google Play App Signing" the SHA1 you have used for your release version is not valid anymore (Google removes the release certificate including your SHA1 before uploading). So the easy solution is to get back in Play Store Console, copy SHA1 from App Signing Certificate (NOT from the Upload Certificate in the bottom!) and put it in the release Google Maps Android API, save and it will refresh without creating a new key.

Milreis

i can't find where to put the copied sha1 from app signing certificate – Swingeing

Answer 3

When you upload and publish the app play console uses your key for upload purpose only. To sign and publish each releases it uses different key certificates that you can find under

Setup -> App Integrity section

Just copy SHA-1 key from there and update it with google map api key. After that your map will start working.

Guido

Answer 4

You can paste the copied sha1 in " restrict usage to your android apps " in restrict and rename Api key

Crelin

This looks like it should've been a comment on Brian K.'s answer. – Tripp

Answer 5

If you don't have any restriction and you are getting this error; make sure your debug/main key and release key are the same or release key is valid.

Kultur