Wednesday, 15 February 2012

android - Does i need different SHA1 key to perform Google Map -


HJ I am using Google Maps API v2 for the project in my office, this cert_fingerprint key 1 < / Strong>

, but when I was doing it in the house, I found an empty Google map. I can see the trace log:

03-17 04: 40: 44.288 12461-12510 / com.dump.dms e / google map android API: in the Google Developer Console () Make sure "Google Maps Android API v2 "Ensure that the following Android key is present: API Key: AIZASEDE 3COcEWPZte_cpPl ********* L2Cm_A Android Application (& lt; cert_fingerprint>; & lt; package_name>): EF: FA : C1: 36: BD: FA: D6: 6A: DE: **: **: **: 53: C8: 8B: 16: C1: 15: C7: ED; com. Decomps (call protection_fingerprint key 2 )

I have to replace the fixed_fingerprint key 2 then my app works normally.

Can anyone explain why I need 2 cert_fingerprint key like that? I'm using my app as a debug build, so the problem is how can I use only one dot / fingerprint key?

Your debug at home. Castor is different from work, in your office, you have that debug. Kistor SHA1 Used to generate the key you used to make Google Maps API Key When you keep your app at home, another debug. Kistour is used and the key does not match.

The easiest way is to copy your debug .cstore file from your work environment and use it at home. But you can also enter several SHA1 keys in your Google API console like this (for every environment that you use, which means that you need to create a SHA1 key for debug. Kistour files of all your environments. ): 

  AB: 0A: 05: ...: 12; Com.example CD: 35: 01: ...: 2b; Com.example

The same problem occurs when you deploy as

Also see:

Release Build (using the keystore file required to be generated while exporting your Android app as an APK file)
Posted by at

No comments:

Post a Comment

Subscribe to: Post Comments (Atom)