[android-developers] Keeping Map API keys in sync across a dev team

2010-01-05 Thread Carl Whalley
When an app which uses the Map API is released it must be signed with
the public cert. For individual use the key comes from the local debug
keystore, created each time the Android SDK is installed. In other
words, its different for each developer. When I include a view using
it, then commit, my key goes in the xml, but the next developer to
take an update clobbers his key, which being different to mine results
in no maps being shown for him. Is there a smarter way to prevent this
when a team is using the Maps API please?

Android Academy: http://www.androidacademy.com
-- 
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Re: [android-developers] Keeping Map API keys in sync across a dev team

2010-01-05 Thread TreKing
Actually, it is possible to get the same debug key. I alternate work between
a PC and laptop and originally had two different debug keys when I first
started.

A while ago I move the SDK folder to lie withing my root project tree (so I
could commit it to revision control, share AVDs across machines, and not
have to do two updates when the SDK is updated).

When I did that my debug keys were invalidated and I had to regenerate the
debug keys for both machines. When I did so the hash from the key-store
ended up being the same on both machines, so I think is determined by the
relative path between the SDK and your project.

If it's feasible, try having your developers move their SDK folders such
that the relative path to the project is the same for them all and see if
that gives you all the same debug key.

Hope that helps.

-
TreKing - Chicago transit tracking app for Android-powered devices
http://sites.google.com/site/rezmobileapps/treking


On Tue, Jan 5, 2010 at 10:54 AM, Carl Whalley
carl.whal...@googlemail.comwrote:

 When an app which uses the Map API is released it must be signed with
 the public cert. For individual use the key comes from the local debug
 keystore, created each time the Android SDK is installed. In other
 words, its different for each developer. When I include a view using
 it, then commit, my key goes in the xml, but the next developer to
 take an update clobbers his key, which being different to mine results
 in no maps being shown for him. Is there a smarter way to prevent this
 when a team is using the Maps API please?

 Android Academy: http://www.androidacademy.com

 --
 You received this message because you are subscribed to the Google
 Groups Android Developers group.
 To post to this group, send email to android-developers@googlegroups.com
 To unsubscribe from this group, send email to
 android-developers+unsubscr...@googlegroups.comandroid-developers%2bunsubscr...@googlegroups.com
 For more options, visit this group at
 http://groups.google.com/group/android-developers?hl=en

-- 
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en