Not in a nice way. Since we are talking about the debug signing here, you could:
- disable signing on the debug build type. - for the flavors you want to sign, configure them to sign with the debug signing. But this means they'll always be signed with debug key unless you create another signing config for release and assign it to the release build type. Then this will override the signing config on the flavor. If the flavor have a signing config but the build types don't then the flavor one wins. What's your use case anyway to sign some flavors with the debug key but not others? On Thu, May 29, 2014 at 8:28 PM, Avram Lyon <[email protected]> wrote: > On Thu, May 29, 2014 at 5:07 PM, Xavier Ducrohet <[email protected]> wrote: > >> Just change the signing config associated with your build type to be null. >> >> > Is there a way to do this on a per-flavor basis? Seems to only work on > build types. > > -- > 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.
