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 <[email protected]> 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 [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.
