Question

This cannot be impossible: We have four developers on an android app that uses the google maps api. We have generated a maps key that works for the one who generated it. All the others, however, see a tiled MapView without the actual map. Since my debug.keystore was used to generate, I was suspecting that the others need the same keystore. So I moved it into the repository so that everyone has a copy of it now. Then, everyone pointed eclipse towards that keystore using the custom keystore setting in Android->Build. This still does not work. What do we have to do? Surely we don't have to each use our own key and keep replacing it after every pull?

This site (and the web in general) contains tons of information on Google Maps API keys, but none answered my question unfortunately.

Was it helpful?

Solution

Rather than trying to point Eclipse to a different keystore, just replace your local debug.keystore with the shared copy.

OTHER TIPS

In year 2013 for V2 you can include as many keystores app as you like. For me it was debug and production keystores. Just follow process described here (this is a common process). When you create Android Key in Google API Console specify each fingerprint;package.name per line. E.g.:

BB:0D:AC:74:D3:21:E1:43:67:71:9B:62:91:AF:A1:66:6E:44:5D:75;com.example
94:66:06:01:12:27:AC:39:BB:44:90:41:40:86:88:3D:96:A7:99:A9;com.example

That's it! Now you have 1 API Key for 2 keystores.

Licensed under: CC-BY-SA with attribution
Not affiliated with StackOverflow
scroll top