I have a problem with google maps API on my android application.
before all was normal, and the application can display the map. I published the apk and follow all tahap2 correctly.
I install applications on my smartphone. but after a week or more all of a sudden my application can not display the map. only the grid view only.
if anyone can give me a solution to this problem?
Thanks in advance
DevYudh
I had this problem in the past. You have to register a Google Maps API key. (Not the debug one). Debug key only works when you are testing the app. But when you publish the app in the market, you need to use the release key. That will surely solve your problem.
See it here..
http://code.google.com/android/add-ons/google-apis/mapkey.html
for display google map on android device, the map key and apk file's sign key must match.
If you debugging, map key must be made by debug key's fingerprint. and the other side, for deploying apk map key must be made by deploying key's fingerprint.
Related
We have implemented Google Maps API V2 and it works fine in development. When the APK is signed and published in Google Play the maps doesn't appears.It loads with a blank White screen with MyLocation button and Zooming controls button.
How to make display the maps on the play store version.
And also,we have generated the Key with keystore file
And also iahd checked with is stackoverflow question:Google map not loading on normal devices but loads on test device(real device)
Still now the same problem exists for us
Thanks in advance for the help
When you test your application during development, you obviously used you Eclipse/Android-Studio debug key. This means that the IDE (Eclipse or Android Studio or w/e) sign your application automatically to save you the trouble, in order to test it fast. They key used for this signing is different than the one for publishing applications on Google Play.
So, you need to follow the instructions here: https://developers.google.com/maps/documentation/android/start
Following the guide, you should be able to generate a "release" key to use with your published application (instead of the debug key that you have been using until now).
I've made an app with google maps api v2. Everything seems to work fine, when i build .apk and install it's still working, but when i upload it on google play and download from there, maps are not working. I think something is wrong with those keys (who start with Alza). I know there are 2 tipes: debug and release. I tried making release key, but i think it still makes that key debug, but that just my opinion i'am still not 100% sure what's the problem.
Any help would be greatly appreciated.
You need to generate SHA1 from the certified keystore which you used to sign the android apk build. Obtaining the google map key using this SHA1 and pass it in the Google Map and API console.
I created an android app that shows google map using Google Map api V2 and it works well with me in my mobile.
But when I uploaded the apk of this app to (Google play store), it doesn't show my map.
Could anyone tell me why? and how to solve this issue?
Thanks in advance.
Your Maps API key is tied to the SHA1 signature of the keystore that is used to sign the app .apk. When you run your app from eclipse, a debug keystore is used, when you export your app for release, you use a 'real' keystore (it's SHA1 fingerprint is shown at the end of eclipse's export wizard).
So you have to create another Maps API key (to put in your manifest) corresponding with you release keystore for release.
Check Google's documentation here.
This is simple method. Select your project->Right click->Export android application. Fill all requirements. When exporting it will show your SHA 1 finger print. copy that and paste it along with package name in google console. You can see Certificate finger prints in screenshot.Use that SHA1 key.
Check whether you are using signed api key when you are exporting. Otherwise map looks blank.
Signed apk for release key procedure is here
Google Map Android API v2 can't display map in play store application
I know there are many other topics that have the problem with the Google Maps API displaying a grid instead of the map, and that is the problem I am having as well.
The difference is that I have had mine working before. I followed a bunch of tutorials and signed my application and all of that stuff, but a few days later the map went back to the grid.
I can just generate another release token, but I don't want to have to do that every time the map displays a grid, and the debug key isn't working like it should.
What do you all suggest?
When you signed the build, did you update the key which the Google Maps use?
Because if not you will get a blank map.
You will need to generate a new Google Maps API key with the keystore you used to sign the build and use this for the signed build.
https://developers.google.com/maps/documentation/android/v1/mapkey
You will then notice the maps will not work when built in Eclipse using the debug keystore but will when exported and signed. It's an annoying process.
Both in eclipse and when uploaded to Play Store the app just shows the grey grid and the custom markers I added but the actual map is not shown.
I am using the keys from the previous developer before me and the previous versions seem to work on Google Play but when I build it it fails to show the map.
Can anyone help me with this?
Only two reasons this would ever happen:
Your device does not have an internet connection or is otherwise unable to download the map tiles because of a firewall on your network etc.
You are using an API key for the maps library that doesn't match the certificate you are signing the apk with. Remember that Eclipse signs the apk with a debug key, and you use a different key for publishing. See this documentation for details on this.
Google Maps API key is connected to they keystore, you should ask the previous developer for the keystore and export your APK with it. Otherwise, you follow the steps in this post and when you get the MD5 fingerprint you sign up here to get new Google Maps API key.