If this isn't already a known bug, I'll create and attach a project that reproduces the issue. I've found that using the "provided" configuration with a JAR artifact will (correctly) include the jar on the classpath but exclude it from the APK, whereas specifying an AAR artifact ends up with that code being *included* in the APK. Currently the only workaround I have is to hack up the proguard<Variant> task and add the undesired classes to an exclude pattern.
-- 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.
