We have released Android Studio 3.0 Canary 7 to the Canary and Dev Channels.

Changes

Specify matching build types . If a consumer (such as an app module) defines a build type that does not exist in a producer dependency (such as a library module), the variant-aware dependency resolution model won’t know which version of the producer to use and your build fails with the following error:



Error:Failed to resolve: Could not resolve project :mylibrary.

Required by:

project :app

You can now specify an alternative build type the consumer should use from the producer using the

android.buildTypeMatching

property as shown below. The plugin uses the alternative build type only if a matching build type is not found.





android {





…





// Let’s say your app configures a ‘staging’ build type and a library module





// it depends on does not. You can use the property below to tell the Android plugin





// to use a library’s ‘debug’ build type instead.





buildTypeMatching ‘staging’, ‘debug’





}





Fixes

We had a number of fixes make it into this build a few reported by our external users include:

63623801 ResourceNotFoundException running Kotlin project on API 16 AVD after upgrading to Canary 6

37111818 Layout Editor cannot edit widget margins in RelativeLayout

63252394 Android studio 3.0 canary build variants auto resolving error



