I have a problem with Google Maps api v2 on my android app.
I have generated the key for the debug certificate and everything works fine, but I can't make it work with the release certificate.
I've generated the key and the alias with eclipse, then I took the SHA1 which eclipse shows at the end of the "Export signed application" process.
Then I generated the api key for android apps in my google api console using
SHA1;package name
But it doesn't work... it works only with the debug key generated in the same way, only using the sha1 of the debug certificate!
Please help me, otherwise I can't release my app
Check your manifest file, I guess you've forgotten to set your release map api key there while exporting with your release key?
Me too faced the same problem during releasing my app to google Play, when I used Google Maps V2 in my app. After succeeding the issue, I wrote a blog post regarding this you can have a look.
As everyone requested, I would say the answer in following steps
1) Sign up your app using eclipse adt
2) Note down the SHA1 finger print which will be displayed at console of your eclipse adt
3) Again go to google console and get API_KEY for your app by using above got SHA1 fingerprint
4) Replace the old API_KEY with the new API_KEY on to manifest.xml of your app
5) Again sign up your app. Your app is ready to be published. But keep in mind that once you published your app to google market, you should be able to release updates to your app by signing .apk using the keystore which you used earlier for release.
Hope this helps ...
There are two files google maps api.xml, one is the debug and release the other, then you should replace the key generated on google website console and enter this file, another outlet is inserted directly into the manifest.
Related
I have Android app which include Google Maps It was working fine before releasing the app, but after releasing the maps are not shown .
Although I've added SHA-1 certificate fingerprint from google console after releasing and added it to the restrected apps
SHA-1 after releasing
API Key Restrictions
So the 2 SHA-1 are included with the package name, the Maps works fine when running the app directly from android studio, but it shows nothing when downloading the app from playstore, any Ideas ?
It's because Google Play is signing app with different SHA-1 Fingerprint, so you need to take it and register in google developer's console
I recently had the same problem. Please make sure you have set your release api key on your app resources.
In your app you might have:
src/debug/res/values/google_maps_api.xml
where you set your debug key and also:
src/release/res/values/google_maps_api.xml
where you must set your release key. If you have created only one API Key with both SHA-1, then you must introduce the same as in debug.
One more thing, in the Google Developers Console besides the debug SHA-1 and the Google Play Console SHA-1 I also add the release SHA-1 of the keystore I've use to sign my app.
Hello when I put the release apk of my google maps app on my phone it works great, but it does not work on other phones which is strange becausd i have the right api key and the right sha1 fingerprint of my keystore file??? Please help. Thanks.
This is because you need to generate a separate key for your app which is going to be released.In this key you need to use the SHA1 of the signed apk.
Please check This link for detailed steps
For signing your app in android studio and obtaining new key,you can use This and This.
In my android app I am using google map and location services.So I generated API key on google developer console for my development work using SHA1 generated by making use of debug.keystore.It worked fine and google map worked perfectly. When I had to release the apk I signed apk following instructions at http://developer.android.com/tools/publishing/app-signing.html#studio.
When I tried to beta test the app, google map didn't work.Visiting the forums told me that I need to generate another google console API key using SHA1 generated by using keysotore which was created while signing the apk.I did same and replaced the key in androidmanifest.xml(So now my project on google console has two API keys,older one I used for development,and newly created one ). But when I regenerated apk and tried to run it on my personal device from android studio, map didn't work.Moreover when I replaced new key by old debug version of key in manifest file and tried to rerun app on my android device map still don't work.So now my older key is also not working while it was working fine before all these changes.
Please help me in this regard.
You should be using the same API Key for your applications but you need to add both the debug and release credentials.
So you will end up with two entries in the android applications:
99:88:77:66:55:44:33:22:11:04:76:99:C3:2A:52:71:7C:64:EC:8B;com.package.app
99:88:77:66:55:44:33:22:11:1C:CC:33:D7:74:A2:49:5D:7D:BF:C6;com.package.app
You can refer to this question for help with the process of adding credentials for each keystore.
I am making an app that uses the Google Maps API V2. When building the App in debug mode, using the debug key the map gets displayed fine. The same is true, when I export the app using Eclipses export function and my production key, installing the app locally with:
adb install com.package.name
However when I publish the apk in the Play Store (as an alpha test) and download it on my device, no map is displayed, making me suspect that something goes wrong with the key.
I registered the production key in the API console and changed the maps key in the manifest to the new key, hence it works when I install it through ADB.
I also uninstalled the app, before the reinstallation from the Play Store and removed my debug key from the API console, to make sure that the release key gets used (and thereby is working correctly).
Any help would be greatly appreciated.
This is a late response, but I thought it might help others who might run into this similar problem. I too had all my release/debug keys generated correctly and the maps on my signed release apk works well through ADB install, but not after uploading to Google Play Store.
Here is my solution: With the new optional "Google Play App Signing" feature, your final SHA1 can be found in your Google Play Console -> Release Management -> App Signing. Add the SHA1 for the app signing certificate to your key restriction list for the API in your API console and your map should be working.
Apparently the generated SHA1 using my own keystore (release) prior to uploading, is different from the final one, after uploading into Google Play Store.
Hope this helps.
Go to the google Apis console and add one more entry with your debug key.
So then you will have an entry :
45:B5:E4:6F:36:AD:0A:98:94:B4:02:66:2B:-- blah blah production key;com.package.name
45:B5:E4:6F:36:AD:0A:98:94:B4:02:66:2B:--yada yada debug key;com.package.name
//The keys I used are random you will get them both running the following command for each keystore ( debug and production )
Use this command to get the key :
keytool -list -v -keystore mystore.keystore
tl;dr two keys one for debug one for production and two entries to the Google Api Console
I fixed the problem by creating a new app and a new certificate. I don't consider this a "solution" since I did not find out what went wrong in the first place.
Basically whenever in the case of Google Map, we need an API key, which is generated on the basis of SH1 key of keystore.
When you work on local system, then we have to use the SH1 key which is displayed in Eclipse. But when we sign our application to make an APK to upload on playstore, we need to edit the exiting key and replace the old SH1 key with a newer SH1 key.
Note: You can get the newer SH1, while signing the APK for playstore. While signing it display the SH1 key of of keystore file, which you are using for that particular application for Playstore.
I have Implemented Google maps V2 Successfully.I have made debug as described by Google Map Tutorial. Now its time to release my app with Google Maps on Google Play.For it i have to make release certificate of Google maps.And i am not understanding first step of release certificate fingerprint .
From Where to download Keystore file? it is From api console google
Where is release certificate keystore file?
It's the keystore you create yourself for signing your applications. You don't download it from anywhere. You should not give it to anyone, not even Google.
See http://developer.android.com/tools/publishing/app-signing.html#releasemode for more information.
Me too faced the same problem during releasing my app to google Play, when I used Google Maps V2 in my app. After succeeding the issue, I wrote a blog post regarding this you can have a look.
As everyone requested, I would say the answer in following steps
1) Sign up your app using eclipse adt
2) Note down the SHA1 finger print which will be displayed at console of your eclipse adt
3) Again go to google console and get API_KEY for your app by using above got SHA1 fingerprint
4) Replace the old API_KEY with the new API_KEY on to manifest.xml of your app
5) Again sign up your app. Your app is ready to be published. But keep in mind that once you published your app to google market, you should be able to release updates to your app by signing .apk using the keystore which you used earlier for release.
Hope this helps ...