[zambo]

Not able to try this out right now but:

1. You can select a custom debug key in eclipse and have multiple devs sign with the same debug key.

2. You should be able to instantiate the MapView in the code at runtime (don't have a dev set up to try this on right now but check out MapView(android.content.Context context, java.lang.String apiKey)). Just provide the API key based off a debug/release flag set in your code.

[mdelbo]

Thanks Zambo. I couldn't find a way to set a custom debug key in Eclipse - I'm using IntelliJ but this frustrated me so much I was considering migrating to Eclipse.

I was also using a debug/release flag previously but kept forgetting to change it when I sent the release build out for testing.

[petedoyle]

Great post, I'm working on my build tonight and this'll come in handy. I usually end up just changing the Maps API key locally and never committing it which kinda sucks.

For Eclipse you can set the debug key here: Window > Preferences > Android > Build > Custom debug keystore. That's for the normal Eclipse/android build process.

Comes in handy when developing on multiple machines as you can't update an app that was signed with a different debug key (must uninstall first).

[mdelbo]

Handy to know that setting exists. Thanks dude.