Google Map Android API v2: Authorization Failure

Question

I am trying to get my Google Maps to display on my app, but it is not working and this error appears:

01-25 11:38:54.763: E/Google Maps Android API(30514): Authorization failure.

I am currently using the SHA1 certificate fingerprint from the release certificate that was used to publish my app on the appstore.

Edit: I have also switched on the Google Map Android API v2 on the API Console.

I've read from the comments from here that "Signature Algorithm MUST be SHA1withRSA and NOT SHA256withRSA". However, I created the release certificate from Eclipse and it is SHA256withRSA, and I didn't do any settings to it. I can't seem to change it either.

Can someone enlighten me if the signature algorithm is causing the problem? If so, how should I be changing the signature algorithm on eclipse?

score 4 · Accepted Answer · answered Jan 25 '13 at 05:29

4

Figured out my problem.

I've been generating keys from my release certificate, which WILL NOT WORK during debugging when I run the app on my phone. I have to use the debugging keystore certificate fingerprint instead.

Please remember to keep 2 keys:

Debug API key from your debugging keystore when you run it on your phone.
Release cert API key to be used when you want to sign the app just before deployment to Google Play Store.

answered Jan 25 '13 at 05:29

lyk

1,578
5
25
49

What you mean Release Cert Api key?please give me some information i am getting same issue. – Harshid Aug 23 '13 at 05:16

score 0 · Answer 2 · answered Jan 25 '13 at 04:23

0

Please check that you have enabled the Google Maps Android API v2 in your google api console.

enter image description here

answered Jan 25 '13 at 04:23

GrIsHu

29,068
10
64
102

Sorry my bad for not mentioned it but yes it is switched on already before I encountered this problem. – lyk Jan 25 '13 at 04:25
Yes, I have followed all the steps in [here](https://developers.google.com/maps/documentation/android/start). That's why I'm wondering if its the signature algorithm is causing the problem. However now I am unable to try signing again due to [this problem](http://stackoverflow.com/questions/14515231/fatal-lint-erorr-during-exporting-of-signed-app) – lyk Jan 25 '13 at 04:30
Try to regenerate the key and clean your project. – GrIsHu Jan 25 '13 at 04:35
Ok, but like I've mentioned I'm suddenly encountering lots of lint errors which are preventing me from regenerating the key – lyk Jan 25 '13 at 04:42
cleaned it up and regenerated a new key and there's still no difference, still occurs with that error. Should I be using the key from my release certificate or use the debugging certificate? – lyk Jan 25 '13 at 05:14

score 0 · Answer 3 · edited Aug 09 '16 at 10:37

Check your API Key exists or not with the appropriate SHA, if not regenerate it with the appropriate SHA. If you don't know how to generate it, try it below:

JAVA_HOME\bin > keytool -list -v -alias androiddebugkey -keystore "~\.android\debug.keystore" -storepass password(your_own) -keypass "password(your_own)"

Check manifest file, if you written two meta tags like this

<!--<meta-data-->
<!--android:name="com.google.android.maps.v2.API_KEY"-->
<!--android:value="AIzaSyBHghWPWutTiOxCJKll2WoCuVOQ5YotLiY" />-->

<meta-data
    android:name="com.google.android.geo.API_KEY"
    android:value="@string/google_maps_key"/>

Comment any one among them, for my Project used geo.API_Key, it will handle both GEO and Google Maps.

More importantly import google-services.json file in to your app folder.

Google Map Android API v2: Authorization Failure

3 Answers3