Generating Google Map Release API Key

Generating Google map Release API Key

You need to :

1. Create your own signing key that you will use for publishing, using Keytool : http://developer.android.com/guide/publishing/app-signing.html#cert

2. Get the MD5 fingerprint of your newly generated key : https://developers.google.com/maps/documentation/android/mapkey#getfingerprint

3. Submit the signature to this link to get your Google Maps key : https://developers.google.com/android/maps-api-signup?hl=fr

4. Export your application with your newly created key, in Eclipse : right click on your projet -> Android Tools -> Export signed application package.

Be careful to keep your certificate in a safe place, because you will need it if you want to publish an update of your app on Google Play.

EDIT :

For the Google Maps Android V2, the signing is a little different. You will need to get the SHA-1 signature and provide the package name of your application as well. A Google APi account is moreover needed. All info are given on this page : https://developers.google.com/maps/documentation/android/start?hl=fr#the_google_maps_api_key

Android google maps release key?

The same way you get a "debug" key. There is no real difference, just as there is no real difference between a debug and a release certificate in Android (except that the debug certificate gets created automatically for you and resides in your Android settings folder).

Get the SHA-1 fingerprint for your Android release key and use it along with the proper package name (debug builds usually have a ".debug" attached, so make sure to omit that) to create a new Google Maps Key in the Google Developer Console.

Generating a Google Maps Release Key

You can use the same Android API key for both debug and release.

Package names can be the same, but as you cannot sign your release with a debug keystore, the certificate fingerprints should be different.

Check that the release fingerprint is correct with the keytool command:

keytool -list -v -keystore my_release_store.keystore

How to change google map api key from debug to release in android?

generate your hash using your sign apk. and than update your sha1 in google developer console.

Google map Release API Key not working

I got the solution. I was adding API key at wrong location. I added release API key inside src/debug/res/values/google_maps_api.xml mistakenly. When I copied it to src/release/res/values/google_maps_api.xml it worked.

Android add separate google map api key for release and debug build modes

Just create same xml file in release folder.

You're default debug key is probably in file project_location/src/debug/res/values/some_file_name.xml.

You need to create same file in project_location/src/release/res/values/some_file_name.xml And put you'r release key there.

Google Maps API Key in release build doesn't work

I had this same problem, it was super frustrating. What I ended up doing was taking the key I made using my release keystore and putting it in the google developers console. Then, added the following into the android manifest.

<meta-data
        android:name="com.google.android.geo.API_KEY"
        android:value="KEY GOES HERE"/>

I'm sure you read the documentation on this, but make sure you follow the instructions for the release certificate to the dot.

https://developers.google.com/maps/documentation/android/signup

You could also follow the link that was generated for you in the google_maps_api.xml file. This automates the process of entering the key into the developer console. However, make sure you still add that meta data value into your manifest.

---

Related Topics