google map API not displayed when export APK - android

Hi I have a problem with Google Map API V2 does not appear when I export my project .apk.
In fact when I do my test sending my Eclipse project via USB everything works, the map is displayed. If I export the project .apk to send to a friend via Gmail and Google Map API V2 is not displayed.
I think this is a problem when exporting but I can not solve it.
If you have answers thank you in advance.

When exporting your app, in the final step the adt(eclipse) shows you the SHA1 key that would be used. Use that SHA1 key value for generating a new google maps api key. Worked for me.

Related

Google map v2 doesn't work in play store

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

google map is not working inside app

I am stuck with a strange problem
My google maps was working well on my asus device but now that I have installed it as an APK file on my tablet(I mean I have deleted the debug program and installed the version that I had produced from the manifest file) but the g.maps still not working.
Consider this that I have switched the API KEYS with the new ones.but the problem still exists.that means when I produce an APK file and install it on my tablet the google maps is not working but when I run that codes in debug mode with the new keys it works fine!
The key is generated from your keystore file so if you build you app with a different keystore file the map will not work.
Please Check your HA1 key that you use to create Google map v2 api key. If the Google map v2 create HA1 key is different form you create apk HA1 key then Google map v2 do not show in Android Device.
Thanks

Google maps api v2 key error

I recently changed my hard drive to my Pc and when I clone my project from github and add the google-play-services as a library I tried to open the google maps and I didn't get any error but nothing shown up. I can see only the zoom buttons and the my location icon. Do I have to regenerate the google-map-api-key for the new ssd?
Yes you need to get your currently generated key from debug.keystore folder and register it via the Google API Console, here is a blog post I wrote on how to do just that:
Generating Google Map API V2 key
Probably you'll have to regenerate your maps API key, as I gues you have a new certificate on your new hard drive. Use keytool to do that, like here:
https://developers.google.com/maps/documentation/android/start#the_google_maps_api_key

convert my application into .apk file it will not show google map

Hi i am new to android application development. I did a google map v2 to show my current location using GPS.
It will work fine when i testing with mobile using USB cable
but the issue is when i convert my application into .apk it will retrive my gps current >location but did not show the map
Can anyone help to resolve my problem?
for generation .APK you must have to use keystore & MAP API KEY from same machine. if this two are diffrent from diffrent machine then it 'll heppend.. (mean MAP are not show)
if you have diffrent keystore then you can get MAP API Key from Keystore.
check below links:
How can I get the MD5 fingerprint from Java's keytool, not only SHA-1?
https://stackoverflow.com/a/5262845/1168654
Edited
open this link: follow steps on "Getting the MD5 Fingerprint of the SDK Debug Certificate" then sign up from this link : after that use that map key in you code see what heppend.
This suggests that either you do not have the Google Play Services referenced in the project properly or your device doesn't support it.
Please read the Quick Start on how to properly reference the jar in your project.

google maps api key not working v2

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 tiles.
I know this is an issue with the API key.
So I created a new key, (and an apk with it) used it to generate a new API key from the google's console. I deleted the apk that was generated with the key, as it had the old ApiKey, and pasted the new api key here.
<com.google.android.maps.MapView
android:layout_width="fill_parent"
android:layout_height="fill_parent"
android:clickable="true"
android:id="#+id/mymap"
android:apiKey="my_api_key"
Then I re exported my project but this time used the same key that I had created the step before as they contained the same SHA-1.
However, still the map does not show and only grey tiles appear.
I have entered my SHA-1 key in the api console in the following way.
18:3E:1D:8C:xx:xx:xx:xx:xx:xx:xx:xx:xx:x:xx:1D:E1:08:32:8E;com.mycompany.mapapp
I tried to revert back to my debug key, but this time the debug app (running from eclipse) also did not show any maps.
my questions are the following.
Is this still the correct method to use? Because in the --https://developers.google.com/maps/documentation/android/start#obtaining_an_api_key -- google used different approach using fragments.
What am I missing ?
Is this method deprecated or should work ?
You're generating an ApiKey for the Google Maps V2, but you are using the v1 MapView com.google.android.maps.MapView.
On the Android Maps V2 API, the key is placed on the manifest, and you use com.google.android.gms.maps.MapView to show the map, using the Google Play Services Library.
I suggest reading the overview section here to learn how to setup your Project with the Google Play Services Library, and looking at the new API Reference here.
If you are developing google maps api. You need to have two sets of map api key. One map api key that is generated by using your SHA1 fingerprint from your debugging keystore, this map api key is to be used when you are debugging your app in eclipse and running it from there. The other map api key is generated by using your SHA1 fingerprint from official or production keystore, this map api key is used when you will signed or publish your app.
I think you are experiencing mismatch of your keys there since the map api key on the manifest is from debugging keystore and you have signed your app with your official keystore.
Also I think you are developing MapView. It is recommended now to use MapFragments now. I have links here that might help you.
Quick Start Guide: https://docs.google.com/document/d/1dFzZT0C782BxLkDIUEb711rmsbMmYPURFV_2Cdb36so/edit?usp=sharing
Trouble shooting thread if you encounter problems with MapFragment or Google Play Services Library:
Unable instantiate android.gms.maps.MapFragment
Also I have answers here in this How to/Error in declaring google-play-services-component that might help you.

Categories

Resources