[android-developers] Re: Managing Google apiKeys
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 mmur...@commonsware.com 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 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 To unsubscribe, reply using remove me as the subject.
Re: [android-developers] Re: Managing Google apiKeys
I'm looking to automate my build. But I'm a .NET guy by day, so am not 100% familiar with all the Java tools yet. I've heard of Hudson (highly regarded amongst my peers), so I will definitely check this out. On Sat, Apr 10, 2010 at 02:49, Hugo Visser botte...@gmail.com wrote: 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 mmur...@commonsware.com 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 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 To unsubscribe, reply using remove me as the subject. -- http://www.opgenorth.net -- 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
[android-developers] Re: Managing Google apiKeys
regardless whatever others think, i still knees and begs for an SDK function for an apk to see if it has been signed by debug signing key or by release signing key, which seems of more humanity to me than other approaches because MAP API key is associated with the signing key. other approaches require good human memory :) On Apr 9, 2:20 pm, Tom Opgenorth opgeno...@gmail.com wrote: Hi all, Perhaps I'm missing the boat here on something, so any advice/feedback would be appreciated. I have a simple app that uses a Google MapView. Now in the layout file for my map activity, I created an apiKey for the debug keystore and use that. However when I want to deploy my app, I need a seperate apiKey for production (based on when I sign my application), correct? What I'm wondering is how do people manage these two apiKeys. When developing I want to use the emulator and the debug apiKey, but when I'm deploying / doing some integration testing with my phone, I want to use the production apiKey. To me, it seems that I need to remember before compiling for production, to swap out the apiKeys in my layout file. A very error prone process given my bad memory. Is there a better way to manage this? --http://www.opgenorth.net -- 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 To unsubscribe, reply using remove me as the subject.
