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

冷暖自知 提交于 2019-11-27 20:50:59
Chandan Suri

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

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.

易学教程内所有资源均来自网络或用户发布的内容,如有违反法律规定的内容欢迎反馈
该文章没有解决你所遇到的问题?点击提问,说说你的问题,让更多的人一起探讨吧!