basically I have made an app on Android Studio and when I run the app on my phone the Google Maps activity runs perfectly. However I have since put the app on Google Play and when people download it, the Google Maps activity only shows a grey screen. Any ideas on why this is? I've done all the SHA1 fingerprint stuff and have an API key, any help would be much appreciated.
Comment promoted to answer:
It's probably because the SHA1 of your release key does not match the SHA1 of your debug key. Add another entry in your API console (under the Google Maps section) with your existing package name and the SHA1 for your release key, and you should be all set.
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 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.
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.