Setting the custom keystore path in ADT should work. If it doesn't, you can just have your team mates copy your debug.keystore in their default location.
As for giving development builds to clients, this should not be a problem, as long as they realize that the signing key is temporary and they will need to fully uninstall the dev version before installing the final version (signed with the release key). Xav On Mon, Jan 5, 2009 at 5:14 PM, Tony Hillerson <[email protected]> wrote: > > Hello all, > > I wasn't able to find the answer to this anywhere, so hopefully I'm > not overlooking something simple. We're building an app that makes use > of maps, so I was able to get everything working with a debug API key > fairly easily. > > The only thing is that I'm working with another developer and we also > need to provide builds to our client. I tried sharing my > debug.keystore with the other developer and using the Custom debug > keystore to get map tiles to display, but that doesn't seem to work. > > Is there a good way to share an API key with other developers during > development? I suppose we could each have our own non source > controlled properties file, but I'm hoping there's a better way. > > ------------------- > Tony Hillerson > EffectiveUI > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
