I have use, fragment for maps. and also i have putted same API key in both debug and release google_maps_api.xml
but it works only on debug mode. in release mode maps fragment is shown as empty. how to fix this issue.
Asked
Active
Viewed 1,784 times
-2
Sathish Kumar J
- 4,280
- 1
- 20
- 48
-
down voters can u tell the reason? – Sathish Kumar J Dec 08 '16 at 07:04
-
you create new key for release mode not same key – Rajesh Dec 08 '16 at 07:06
-
with same format? like sha1-fingerprint;packagename? – Sathish Kumar J Dec 08 '16 at 07:09
-
first create SHA1 Fingerprint based on your app play store .keystore file and same package name – Rajesh Dec 08 '16 at 07:11
-
it works well in debug mode – Sathish Kumar J Dec 08 '16 at 07:14
-
i know that one only for debug mode if you want to release mode you need to follow release procedure and debug mode key valid only one year only – Rajesh Dec 08 '16 at 07:16
-
release procedure ? any difference between that? – Sathish Kumar J Dec 08 '16 at 07:17
-
yes that based on your play store jks based you can search google map release android – Rajesh Dec 08 '16 at 07:19
-
debug and release apk's should be signed with different keystore files. Map api key changes depends on your keystore files. Because you create your api key with keystore sha1 fingerprint. – Faruk Toptas Dec 08 '16 at 07:32
2 Answers
2
referring to https://developers.google.com/maps/documentation/android-api/signup
you will have 2 SHA keys ... one for debug, one for release.
just enter the SHA finger print for the release app into your console and it should work.
open your console using this link https://console.developers.google.com/flows/enableapi?apiid=maps_android_backend&reusekey=true
under credentials, enter the sha and your package names (see image below).
For my case, i use the same API key for two apps (and debug and release), hence there are 4 rows.
Angel Koh
- 12,479
- 7
- 64
- 91
-
i cant understand `just enter the SHA finger print for the release app into your console and it should work.` – Sathish Kumar J Dec 08 '16 at 07:23
-
-
1@Chirayu, do you mean where can we get the SHA fingerprint? this should help http://stackoverflow.com/questions/27609442/how-to-get-the-sha-1-fingerprint-certificate-in-android-studio-for-debug-mode – Angel Koh Dec 08 '16 at 07:43
-
-
@SathishKumarJ the sha1 for debug is different from the sha1 for release. – Angel Koh Dec 08 '16 at 07:52
-
-
@AngelKoh i always find same sha key.. is this only key we need always? – Chirayu Dec 08 '16 at 09:09
-
1@Chirayu, the sha should be different for debug and release. you can try the suggestions by Naeem Ibrahim to get the SHA key for release http://stackoverflow.com/posts/35308827/revisions – Angel Koh Dec 08 '16 at 12:37
0
Pls. try this: use adb to install the apk on your device/emulator (adb install app.apk). Don't forget to uninstall the debug version first, otherwise the signature difference will prevent the installation
pankaj shinde
- 54
- 9
-
-
Instead of console ,add some alerts in the application and test it locally. – pankaj shinde Dec 08 '16 at 07:14
-
By using ADB install
install the release apk by using new SHA key – AndroidEnthusiastic Dec 08 '16 at 07:28