flavorDimensions gradle error - Android Studio 3.0 Canary 1

后端 未结 4 463
有刺的猬
有刺的猬 2020-12-31 04:42

I would like to upgrade my project to Android Studio 3.0 Canary 1 and the gradle:3.0.0-alpha1 plugin, however I have a problem with the correct definition of flavors for inc

相关标签:
4条回答
  • 2020-12-31 05:28

    I had a similar issue using Canary 2, but the proposed solution didn't work. Apparently there is a way to use the implementation from a Local library or project:

    // This is the old method and no longer works for local
    // library modules:
    // debugCompile project(path: ':foo', configuration: 'debug')
    // releaseCompile project(path: ':foo', configuration: 'release')
    
    // Instead, simply use the following to take advantage of
    // variant-aware dependency resolution. You can learn more about
    // the 'implementation' configuration in the section about
    // new dependency configurations.
    implementation project(':foo')
    

    Reference from Studio Documentation.

    0 讨论(0)
  • 2020-12-31 05:34

    I got around this by using gradle 4.3 (with Android Studio 3.0)

    To use it with Android Studio 3.0:

    1. Download the binary here: https://gradle.org/releases/
    2. Configure local gradle binary in Android Studio, under preferences...

    1. Then in your gradle file replace compile with either implementation or api depending on your requirements.

    references: https://developer.android.com/studio/build/gradle-plugin-3-0-0-migration.html

    ALSO: make sure that your external modules (i.e util) have the same flavors as your App or you will get the error outlined in here: Gradle 4.0 Unable to find a matching configuration

    0 讨论(0)
  • 2020-12-31 05:36

    From https://issuetracker.google.com/issues/65867056:

    You should have only one buildScript block in the root build.gradle. If you are using Composite builds, this is not currently supported by our plugin due to limitations in Gradle.

    EDIT: I guess this now works for latest versions of gradle

    0 讨论(0)
  • 2020-12-31 05:43

    Seems like a bug in the Gradle build process, I'm not quite sure why exactly it's not working. I was stuck on this for a while but I was able to fix it by changing

    compile project(':util')
    

    to

    compile project(path: ':util', configuration: 'default')
    

    Let me know if this works for you!

    0 讨论(0)
提交回复
热议问题