7

google maps api key not working v2

view full story
linux-howto

http://stackoverflow.com – I had an android application that utilizes google maps. I have followed the instuctions and made the app working in debug mode using the debug key. I have retrieved my SHA-1 key from the debug.keystore found here. c:\Users\myself\.android\debug.keystore using c:\Program Files\Java\jdk1.7.0_03\bin>keytool -list -v -keystore c:\debug.keystore The map was showing fine whenever I used tethered debug by running the app from eclipse on my test phone (which ran android 2.3.6). However, after finishing the app, in the published app the map did not show. What was visible were only grey til (HowTos)

linuxletgo's picture
Submitted by linuxletgo on 02/23/2013 – Made popular on 02/23/2013

Stories similar to google maps api key not working v2

Well i was working on an Android project which uses Google Maps.The application works well using Eclipse(Debug) but when i released the app on the market, It showed Grey Tiles.After few searches i got to know i had to get a release API KEY for maps using the same keystore that i use to sign the APK file.

I DID that and now the Maps appear but there seems to another problem, the functions i am usi

I know there are a number of questions about using a Google Maps API key, but none of them have been answered since V1 went extinct. I am having trouble loading in the map tiles on my MapView. I am using an API key derived from the debug keystore and I am debugging using a Nexus 7 tethered via USB.

I got the google cloud endpoints working with an android app and backend written in python app engine. When I uninstalled my and re-installed my app during development, I started running into a 401 error from the backend. This is without any changes in backend after I got it to work the first time.

Ok I am trying to follow the steps on google's website on how to prepare an app for putting on their market. My problem is when I am trying to use keytool....

I have tried

keytool -exportcert -alias androiddebugkey -keystore ~/.android/debug.keystore | openssl sha1 -binary | openssl base64

And I get a keyhash 1knQ67Fx4PUOYXggSe+mnzqaTL8=.

But google's own documentation suggests an alternative too.

I'm doing searches for 2 days and I couldn't fix this problem. I did everything, yet, this application can not work.

I want my application to work on Android 2.2 and above. Like it says "if you create your app in level 8, it'll support 95% of market".

Here are my screenshots and source codes:

I'm pasting the source code which is the easiest to get. I took this from web.

I have a custom keystore that I use for signing my apk. now I want to use the same keystore for debugging. when I go to eclipse->windows->preferences->android->build and set my custom key store I get "Keystore was tampered with, or password was incorrect"?

I have a simple problem, but thus far all of the advice found on this site and others have not helped.

I am trying to debug, through eclipse, on to a samsung device (SCH-R720.)

I have done this before with no problem.

I have my application already on playstore , I developed new project with same package name , when I try to export it with the same keystore file , Eclipse CRASH .. but If I export with new keystore , it works fine ... I need to export it with old keystore so I'll be able to update it on Play store