Put in debug maps key for development

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Run My Tracks from eclipse

What is the expected output? What do you see instead?
You should see the google maps images, and you don't. This is because the
API key matches the certificate we use for releasing, but not the debugging
one.
The proposed solution is to keep the debug key there, and only switch for
releases.

Original issue reported on code.google.com by rdama...@google.com on 20 May 2010 at 6:55

[GoogleCodeExporter]

Original comment by rdama...@google.com on 22 May 2010 at 8:40

• Changed state: Started

[GoogleCodeExporter]

This is done, but I suspect the debug key may be different for each user. If 
that's
the case, it becomes a bit more annoying as each developer will need to change 
it
locally. Sandor, can you grab change
http://code.google.com/r/rdamazio-mytracks/source/detail?r=a6143aea6b13c66af8702
d639ee23524de8529d9
and see if it works out of the box for you?

Original comment by rdama...@google.com on 22 May 2010 at 8:49

• Changed state: Fixed

[GoogleCodeExporter]

Sorry for the dumb question.
How can I use the map key and certificate fingerprint provided in the 
repository? It doesn't work out of the box for me, I can't get the MapView 
working...

Original comment by emanuele...@gmail.com on 25 Jun 2010 at 2:16

[GoogleCodeExporter]

The one in the repository only works if the APK is signed with the official 
release key (which is not in the repository, for security reasons).
You have to generate your own maps api key from your ~/.android/debug.keystore

Original comment by rdama...@google.com on 25 Jun 2010 at 3:36