In the logcat I could only see next error message 'Unexpected response code 400 for ' that probably was indicating some problem with the Google Maps API access. I had a similar problem: after creating a couple of new variants builds with same type ('release') but some new flavors ('free' and 'premium'), the Google Maps fragment did not show anymore the maps and the screen appeared totally blank. Īfter that use that new API key in Android Manifest as the previous one and you are done.ġ) Create apk file using 'Use the export Wizard' in 'Android Manifest' file of your project.Ģ) After inserting key and before finishing, MD5 and SHA1 keys are shown as shown is this given pic- ( )ģ) Create new API Key for Android project in for new SHA1 which is retrieved in point 2).Ĥ)Use that API key in manifest file as shown belowĥ)Clean your project and build APK file again as per point 1).Ħ) You can see google maps now in that apk. We have to create new API key for that SHA-1.Īccording to solution How to obtain Signing certificate fingerprint (SHA1) for OAuth 2.0 on Android? we can get SHA-1 for the exported apk file. When we build apk file to upload on Play store new SHA-1 key is made so we have to make new debug.keystore for that.

When we are using Google maps while developing, a default debug.keystore is used which has no password. I use this solution to solve same problem There's no limit of how many certificate fingerprints and package names are assigned to single Google Maps key, so unless you need this separated is's perfectly fine to have both development and production builds using the same key. You need to add both to your Google Maps key entry in your API console as seaparate row - each with the same packageId, but naturally different SHA1 hash. Debug certificate is different from your production certificate.

Install google maps apk