That would only be true if you put code in src/fast/java (assuming the variant is named 'fast'). The default config (and thus main code) can retain the normal minSdk.
On Fri, Nov 13, 2015, 6:02 AM Csaba Kozák <[email protected]> wrote: > The multidexing documentation > <http://developer.android.com/tools/building/multidex.html#dev-build> > suggest to developer to add a flavor which uses minSdkVersion >= 21. > This way a more effective multidexing can be used during Gradle build, > which is faster then legacy multidex. > > This is great, but it has a caveat: if a developer uses minSdkVersion >= > 21 in the development flavor which he > uses for dev he could unintentionally call APIs which are only available > from API 21. > But the real minSdkVersion is lower than 21, so this will cause problems > on older Android versions. > > Is there a way to instruct the multidexing task to use the API 21 > behaviour, but leave the minSdkVersion intact for other tasks (and AS)? > > Thanks in advance! > > -- > 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. > -- 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.
