Well if you are talking strictly about release signing then it's different!
Don't change the signing config of the debug buildType. Don't setup any signing config on the release build type. Instead set it up on the flavors you want to sign directly from gradle (I'm guessing the flavor associated with the "Play Store" variant?). Then your release build for your amazon variant won't be signed but the release build of your play store one will be. On Fri, May 30, 2014 at 6:31 AM, Avram Lyon <[email protected]> wrote: > On Thu, May 29, 2014 at 11:37 PM, Xavier Ducrohet <[email protected]> wrote: >> >> What's your use case anyway to sign some flavors with the debug key but >> not others? >> > > We are using Amazon's two-step APK signing procedure on one of our titles, > which means we need to get unsigned APKs for only the Amazon flavor, for > release builds. We upload the unsigned APK to their console, they inject > their modifications, and we download the modified version and re-sign it. > This is an option that they no longer encourage, but we're stuck with the > two-step procedure for this one title. > > -- > You received this message because you are subscribed to the Google Groups > "adt-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- Xavier Ducrohet Android SDK Tech Lead Google Inc. http://developer.android.com | http://tools.android.com Please do not send me questions directly. Thanks! -- You received this message because you are subscribed to the Google Groups "adt-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
