Gradle 4.0无法找到匹配的配置 [英] Gradle 4.0 Unable to find a matching configuration

查看:303
本文介绍了Gradle 4.0无法找到匹配的配置的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我试图在新的Android Studio 3.0 Canary中打开我的现有项目。我根据 instructions ,更改了依赖配置的名称,但是我继续得到下一个错误:

 错误:无法解析配置的所有依赖关系:bankOK:betaNewApiInnerTestRuntimeClasspath'。 
>无法在项目中找到匹配的配置:abChat:
- 配置'debugApiElements':
- 必需的apiLvl'ProductFlavorAttr {name = newApi}',但未提供任何值。
- 必需的com.android.build.gradle.internal.dependency.AndroidTypeAttr'AndroidTypeAttr {name = Aar}',并找到兼容值'AndroidTypeAttr {name = Aar}'。
- 必需的com.android.build.gradle.internal.dependency.BuildTypeAttr'BuildTypeAttr {name = innerTest}',并找到不兼容的值'BuildTypeAttr {name = debug}'。
- 找到com.android.build.gradle.internal.dependency.VariantAttr'VariantAttr {name = debug}',但不是必需的。
- 运行时所需的org.gradle.api.attributes.Usage',发现'compile'不兼容的值。
- 必需的releaseType'ProductFlavorAttr {name = beta}',但未提供任何值。
- 配置'debugRuntimeElements':
- 必需的apiLvl'ProductFlavorAttr {name = newApi}',但未提供任何值。
- 必需的com.android.build.gradle.internal.dependency.AndroidTypeAttr'AndroidTypeAttr {name = Aar}',并找到兼容值'AndroidTypeAttr {name = Aar}'。
- 必需的com.android.build.gradle.internal.dependency.BuildTypeAttr'BuildTypeAttr {name = innerTest}',并找到不兼容的值'BuildTypeAttr {name = debug}'。
- 找到com.android.build.gradle.internal.dependency.VariantAttr'VariantAttr {name = debug}',但不是必需的。
- 运行时所需的org.gradle.api.attributes.Usage'并找到兼容值'for runtime'。
- 必需的releaseType'ProductFlavorAttr {name = beta}',但未提供任何值。
- 配置'releaseApiElements':
- 必需的apiLvl'ProductFlavorAttr {name = newApi}',但没有提供任何值。
- 必需的com.android.build.gradle.internal.dependency.AndroidTypeAttr'AndroidTypeAttr {name = Aar}',并找到兼容值'AndroidTypeAttr {name = Aar}'。
- 必需的com.android.build.gradle.internal.dependency.BuildTypeAttr'BuildTypeAttr {name = innerTest}',并找到不兼容的值'BuildTypeAttr {name = release}'。
- 找到com.android.build.gradle.internal.dependency.VariantAttr'VariantAttr {name = release}',但不是必需的。
- 运行时所需的org.gradle.api.attributes.Usage',发现'compile'不兼容的值。
- 必需的releaseType'ProductFlavorAttr {name = beta}',但未提供任何值。
- 配置'releaseRuntimeElements':
- 必需的apiLvl'ProductFlavorAttr {name = newApi}',但未提供任何值。
- 必需的com.android.build.gradle.internal.dependency.AndroidTypeAttr'AndroidTypeAttr {name = Aar}',并找到兼容值'AndroidTypeAttr {name = Aar}'。
- 必需的com.android.build.gradle.internal.dependency.BuildTypeAttr'BuildTypeAttr {name = innerTest}',并找到不兼容的值'BuildTypeAttr {name = release}'。
- 找到com.android.build.gradle.internal.dependency.VariantAttr'VariantAttr {name = release}',但不是必需的。
- 运行时所需的org.gradle.api.attributes.Usage'并找到兼容值'for runtime'。
- 必需的releaseType'ProductFlavorAttr {name = beta}',但未提供任何值。

以下是我们的构建类型和风格:

  buildTypes {

release {
// ...
}

debug {
// ...
}

innerTest {
// ...
}
}



flavorDimensionsreleaseType,apiLvl
productFlavors {
prod {
dimensionreleaseType
// ...
}
beta {
dimensionreleaseType
// ...
}
oldApi {
dimensionapiLvl
// ...
}
newApi {
dimensionapiLvl
// ...
}
}

另外,我们有一个名为abChat的库模块,没有任何口味。
我能做些什么来解决这个问题?

解决方案

这个问题已经解决,一切工作正常稳定的3.0版本。如果你仍然面临这个问题,那是因为没有回退机制。

如果您的应用程序包含库的构建类型,那么您将得到此错误。为了解决这个问题,你需要为你的构建类型提供 matchingFallbacks 。参考解决与依赖项匹配相关的构建错误 section 在本文档中



在构建类型的情况下,请执行以下操作,并且如果它是产品口味

  buildTypes {
release {
// ...
}
debug {
// ...
}
innerTest {
// ...
matchingFallbacks = ['debug','release ']
}
}

并简单地添加如下所示的依赖关系:

 依赖关系{
实施项目(':abChat')
}


I am trying to open my existing project in new Android Studio 3.0 canary 2. I updated Gradle according to instructions, changed names for dependency configurations but I continue to get next error:

Error:Could not resolve all dependencies for configuration ':bankOK:betaNewApiInnerTestRuntimeClasspath'.
> Unable to find a matching configuration in project :abChat:
    - Configuration 'debugApiElements':
        - Required apiLvl 'ProductFlavorAttr{name=newApi}' but no value provided.
        - Required com.android.build.gradle.internal.dependency.AndroidTypeAttr 'AndroidTypeAttr{name=Aar}' and found compatible value 'AndroidTypeAttr{name=Aar}'.
        - Required com.android.build.gradle.internal.dependency.BuildTypeAttr 'BuildTypeAttr{name=innerTest}' and found incompatible value 'BuildTypeAttr{name=debug}'.
        - Found com.android.build.gradle.internal.dependency.VariantAttr 'VariantAttr{name=debug}' but wasn't required.
        - Required org.gradle.api.attributes.Usage 'for runtime' and found incompatible value 'for compile'.
        - Required releaseType 'ProductFlavorAttr{name=beta}' but no value provided.
    - Configuration 'debugRuntimeElements':
        - Required apiLvl 'ProductFlavorAttr{name=newApi}' but no value provided.
        - Required com.android.build.gradle.internal.dependency.AndroidTypeAttr 'AndroidTypeAttr{name=Aar}' and found compatible value 'AndroidTypeAttr{name=Aar}'.
        - Required com.android.build.gradle.internal.dependency.BuildTypeAttr 'BuildTypeAttr{name=innerTest}' and found incompatible value 'BuildTypeAttr{name=debug}'.
        - Found com.android.build.gradle.internal.dependency.VariantAttr 'VariantAttr{name=debug}' but wasn't required.
        - Required org.gradle.api.attributes.Usage 'for runtime' and found compatible value 'for runtime'.
        - Required releaseType 'ProductFlavorAttr{name=beta}' but no value provided.
    - Configuration 'releaseApiElements':
        - Required apiLvl 'ProductFlavorAttr{name=newApi}' but no value provided.
        - Required com.android.build.gradle.internal.dependency.AndroidTypeAttr 'AndroidTypeAttr{name=Aar}' and found compatible value 'AndroidTypeAttr{name=Aar}'.
        - Required com.android.build.gradle.internal.dependency.BuildTypeAttr 'BuildTypeAttr{name=innerTest}' and found incompatible value 'BuildTypeAttr{name=release}'.
        - Found com.android.build.gradle.internal.dependency.VariantAttr 'VariantAttr{name=release}' but wasn't required.
        - Required org.gradle.api.attributes.Usage 'for runtime' and found incompatible value 'for compile'.
        - Required releaseType 'ProductFlavorAttr{name=beta}' but no value provided.
    - Configuration 'releaseRuntimeElements':
        - Required apiLvl 'ProductFlavorAttr{name=newApi}' but no value provided.
        - Required com.android.build.gradle.internal.dependency.AndroidTypeAttr 'AndroidTypeAttr{name=Aar}' and found compatible value 'AndroidTypeAttr{name=Aar}'.
        - Required com.android.build.gradle.internal.dependency.BuildTypeAttr 'BuildTypeAttr{name=innerTest}' and found incompatible value 'BuildTypeAttr{name=release}'.
        - Found com.android.build.gradle.internal.dependency.VariantAttr 'VariantAttr{name=release}' but wasn't required.
        - Required org.gradle.api.attributes.Usage 'for runtime' and found compatible value 'for runtime'.
        - Required releaseType 'ProductFlavorAttr{name=beta}' but no value provided.

Here are our build types and flavors:

buildTypes {

        release {
           //...
        }

        debug {
           //...
        }

        innerTest {
            //...
        }
    }



flavorDimensions "releaseType", "apiLvl"
    productFlavors {
        prod {
            dimension "releaseType"
            //...
        }
        beta {
            dimension "releaseType"
            //...
        }
        oldApi {
            dimension "apiLvl"
           //...
        }
        newApi {
            dimension "apiLvl"
            //...
        }
    }

Also, we have a library module named "abChat" without any flavors. What can I try to do to solve the problem?

解决方案

This issue is fixed and everything works fine in the Stable 3.0 version. If you still face this issue, that's because there is no fallback mechanism.

If your app includes a build type that the library doesn't then you will get this error. To fix this, you need to provide matchingFallbacks to your build type. Refer the Resolve build errors related to Dependency matching section in this documentation

In case of build types do the below, and if it's product flavors refer the documentation for migration.

buildTypes {
    release {
       //...
    }
    debug {
       //...
    }
    innerTest {
        //...
        matchingFallbacks = ['debug', 'release']
    }
}

and simply add your dependencies like below:

dependencies {
    implementation project(':abChat')
}

这篇关于Gradle 4.0无法找到匹配的配置的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆