On Apr 28, 10:12 pm, Ted Hopp <ted.h...@gmail.com> wrote: > We are now writing an app that another company will brand and sell through > their > own publisher account.
> *Signing the app* > The alternatives we see are: sign with our usual key; create a signing key > pair specific to the other company and sign with that; or help the other > company install a development system, generate a key pair, and do the > signing themselves. The latter would require us sending them the project > sources, which presents its own problems. Other than our concern about > sending the source, does the choice matter in any way? You need not send them sources if that's not part of the contract, as signing the apk can be a distinct step from compiling it, by using jarsigner at the command line after stripping out any existing signature (treat the .apk as a zip file) If you set them up with something to do this, push them to deposit a backup of the key wherever they keep the critical corporate papers. -- 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
