Another way to approach this is to build your releases in an automated way. So you run all your dev stuff from Eclipse, and when it's time to release you build it automated. I'm using hudson for this and I've written a post on the hudson ci blog about it here: http://blog.hudson-ci.org/content/getting-started-building-android-apps-hudson
I use this method to replace the maps key with the "release" one and to disable the debugging attribute that I might have left in the AndroidManifest.xml. After building Hudson automatically deploys my app to different emulators to check if my app installs on all versions of Android that I like to support. Hope that helps. Hugo On Apr 10, 3:12 am, Mark Murphy <[email protected]> wrote: > Tom Opgenorth wrote: > > I'm developing on my laptop. I have a colleague developing on his. > > We both have different debug.store files, which implies a different > > apiKey for each of us, and different from the production apiKey. So > > does this mean that we'd have to have three copies of the layout file: > > one for my debug key, one for my colleagues debug key, and then one > > for production? > > Or perhaps you sync your debug.store files. > > -- > Mark Murphy (a Commons > Guy)http://commonsware.com|http://twitter.com/commonsguy > > Android Training...At Your Office:http://commonsware.com/training -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en To unsubscribe, reply using "remove me" as the subject.
