Encountering ambiguous configuration exception in submodule

android

(Zachary Sperske) #1

I’m sure questions like this are all over the place now that Android Studio 3.0 is out officially. We’re seeing this error when resolving our dependencies.

Could not resolve project :core:base.
Required by:
project :design
> Cannot choose between the following configurations of project :core:base:
- debugApiElements
- debugRuntimeElements
- releaseApiElements
- releaseRuntimeElements
All of them match the consumer attributes:
- Configuration ‘debugApiElements’:
- Found com.android.build.api.attributes.BuildTypeAttr ‘debug’ but wasn’t required.
- Found com.android.build.gradle.internal.dependency.AndroidTypeAttr ‘Aar’ but wasn’t required.
- Found com.android.build.gradle.internal.dependency.VariantAttr ‘debug’ but wasn’t required.
- Found org.gradle.api.attributes.Usage ‘java-api’ but wasn’t required.
- Configuration ‘debugRuntimeElements’:
- Found com.android.build.api.attributes.BuildTypeAttr ‘debug’ but wasn’t required.
- Found com.android.build.gradle.internal.dependency.AndroidTypeAttr ‘Aar’ but wasn’t required.
- Found com.android.build.gradle.internal.dependency.VariantAttr ‘debug’ but wasn’t required.
- Found org.gradle.api.attributes.Usage ‘java-runtime’ but wasn’t required.
- Configuration ‘releaseApiElements’:
- Found com.android.build.api.attributes.BuildTypeAttr ‘release’ but wasn’t required.
- Found com.android.build.gradle.internal.dependency.AndroidTypeAttr ‘Aar’ but wasn’t required.
- Found com.android.build.gradle.internal.dependency.VariantAttr ‘release’ but wasn’t required.
- Found org.gradle.api.attributes.Usage ‘java-api’ but wasn’t required.
- Configuration ‘releaseRuntimeElements’:
- Found com.android.build.api.attributes.BuildTypeAttr ‘release’ but wasn’t required.
- Found com.android.build.gradle.internal.dependency.AndroidTypeAttr ‘Aar’ but wasn’t required.
- Found com.android.build.gradle.internal.dependency.VariantAttr ‘release’ but wasn’t required.
- Found org.gradle.api.attributes.Usage ‘java-runtime’ but wasn’t required.

I’m not sure if this is the correct forum to ask questions about the Android gradle plugin, if not I apologize. The new plugin suggests that you add “matchingFallbacks” to your build types, which we have in this form: matchingFallbacks = [‘release’, ‘debug’]. Our application has 2 buildTypes, debug and release and the library throwing the errors has one buildType, release.