0

I am able to run my app fine using the debug keystore - but when I attempt to run with the production version with a generated keystore - no map.

I have verified that everything is as it should be - API key - check! Keysrore SHA1 - check!

Log follows:

Authorization failure. Please see https://developers.google.com/maps/documentation/android/start for how to correctly set up the map.

In the Google Developer Console (https://console.developers.google.com)

Ensure that the "Google Maps Android API v2" is enabled.

Ensure that the following Android Key exists:

API Key: xxxxxxxxxxxxxxxxx-xxxxxxxx

Android Application (;): xxxxxxxxxxxxxxxxxxxxxx;xx.xxx

Androiderson
  • 16,865
  • 6
  • 62
  • 72
Jason Van Anden
  • 879
  • 8
  • 18
  • 1
    If you used a wizard to create your project or your Activity, this might be the issue: http://stackoverflow.com/questions/30559602/android-studio-google-map-still-blank-on-real-android-device – Daniel Nugent Oct 31 '15 at 00:37
  • Thanks but - no. I have this set in both places - properly. – Jason Van Anden Oct 31 '15 at 00:41
  • 1
    Are you using one API key that has both debug and release SHA1 values, or are you using separate API keys for debug and release? – Daniel Nugent Oct 31 '15 at 00:43
  • Tried both ways - grouped them and did as separate entries. I even tried two different Google Developer accounts as a sanity check. Wondering if this could have something to do with the keystore. – Jason Van Anden Oct 31 '15 at 00:44
  • 1
    Try putting the release API key directly in the AndroidManifest and then create the signed apk. If that doesn't work, then there is an issue with the API key itself. If it does work, then there is an issue getting the correct value for the release build. – Daniel Nugent Oct 31 '15 at 00:47
  • 1
    One more thing to check as well, is the SHA1 value you have in the API key exactly as it shows in the logs after `Android Application`? – Daniel Nugent Oct 31 '15 at 00:51
  • Unclear why - but the release build now shows a map. May have been a matter of retracing steps one more time. Dunno - but thx for your help. – Jason Van Anden Oct 31 '15 at 01:27
  • Nice! One last thing, whenever you make a change to the API key, be sure to fully uninstall the app and reinstall, that could have been the issue as well. – Daniel Nugent Oct 31 '15 at 01:34

0 Answers0