28

I have a project with 2 modules: an app (Java) with build types debug, release, and enterprise and a Kotlin library (release and debug) used by the app.

I'm using AndroidX and have the following in my gradle.properties:

android.useAndroidX=true
android.enableJetifier=true

If I run the project through Gradle, I get a bunch of compile errors (expected). But if I try to use it from within Android Studio (3.2 Beta 5), specifically when trying to sync with the Gradle model, I get this:

Unable to resolve dependency for ':app@debug/compileClasspath': Failed to transform file 'some-lib-release.aar' to match attributes {artifactType=processed-aar} using transform JetifyTransform
Unable to resolve dependency for ':app@debugAndroidTest/compileClasspath': Failed to transform file 'some-lib-release.aar' to match attributes {artifactType=processed-aar} using transform JetifyTransform
Unable to resolve dependency for ':app@debugUnitTest/compileClasspath': Failed to transform file 'some-lib-release.aar' to match attributes {artifactType=processed-aar} using transform JetifyTransform
Unable to resolve dependency for ':app@release/compileClasspath': Failed to transform file 'some-lib-release.aar' to match attributes {artifactType=processed-aar} using transform JetifyTransform
Unable to resolve dependency for ':app@releaseUnitTest/compileClasspath': Failed to transform file 'some-lib-release.aar' to match attributes {artifactType=processed-aar} using transform JetifyTransform
Unable to resolve dependency for ':app@enterprise/compileClasspath': Failed to transform file 'some-lib-release.aar' to match attributes {artifactType=processed-aar} using transform JetifyTransform
Unable to resolve dependency for ':app@enterpriseUnitTest/compileClasspath': Failed to transform file 'some-lib-release.aar' to match attributes {artifactType=processed-aar} using transform JetifyTransform

My settings.gradle:

include ':app',':some-lib'
project(':some-lib').projectDir = file ('../some-lib/lib')

The library module will eventually be its own library used by this app and others, but while I'm working on it I build it as a part of the app. Things were working fine until I switched to AndroidX.

The app module declares the dependency as:

implementation project(path: ':some-lib', configuration: 'default')

If I leave out the configuration: 'default' bit when declaring the dependency, I get:

Unable to resolve dependency for ':app@enterprise/compileClasspath': Could not resolve project :some-lib.
Unable to resolve dependency for ':app@enterpriseUnitTest/compileClasspath': Could not resolve project :some-lib.

Any ideas on what I'm doing wrong here?

copolii
  • 13,331
  • 9
  • 46
  • 76
  • I'm getting similar issues to this with 3.2, even without Jetifier/AndroidX :-\ Did using `matchingFallbacks` work for you? I've been using that since 3.0 and while it still works in 3.1.3, it doesn't seem to work anymore in `3.2.0-rc02` – ankushg Sep 05 '18 at 01:35

6 Answers6

10

The error seems to be caused by corrupt Jetified files.

Delete ONLY the corrupted .aar from the Gradle caches folder:

rm ~/.gradle/caches/modules-2/files-2.1/path-to/some-release.aar

The "path-to" will be probably be the package name e.g., com.example.somerelease

Sometimes it is possible to get the path of the file to delete from the error message itself and cut and paste it into the terminal in order to execute the rm command.

Deleting the entire folder is not an optimal solution as all the dependencies will need to be Jetified again. If you're already having corruption issues, you're likely to encounter the issue again.

David Rawson
  • 17,631
  • 6
  • 78
  • 112
  • 1
    Try not to delete the whole gradle folder if you don't have to. It requires a super-long first build on almost each old project you try to build – milosmns Apr 03 '20 at 12:16
9

I could swear I had already tried this, but specifying a set of matchingFallbacks for the build types did the trick:

buildTypes {
    release {
        // blah blah
        matchingFallbacks = ['release']
    }
    enterprise {
        // blah blah
        matchingFallbacks = ['release']
    }
    debug {
        // blah blah
        matchingFallbacks = ['debug']
    }
}

More here

copolii
  • 13,331
  • 9
  • 46
  • 76
  • 1
    I'm still having the same issue. and I cannot figure out why... it only happens when I use kapt... and if I use implementation project(':library') insteaad of implementation project(path: ':library', configuration:'default') I get another error:Caused by: org.gradle.internal.component.AmbiguousVariantSelectionException: More than one variant of project :library matches the consumer attributes: – Patric Nov 01 '18 at 03:21
  • 1
    The link 'here' is dead. – GoZoner Jan 14 '19 at 19:57
  • 1
    @GoZoner Fixed. Thanks. – copolii Jan 15 '19 at 20:10
  • unfortunately, for me [answer below](https://stackoverflow.com/a/53217799/1870447) resolves this particular error - but then again, it has its own set of errors with the particular project I'm working on right now! – Antek Feb 27 '19 at 13:29
3

Try this:

implementation fileTree(include:[':some-lib'], dir: "../lib/path")
Chris Lacy
  • 3,977
  • 3
  • 31
  • 32
  • This solution resolves this particular error, but it has its own set of errors with the particular project I'm working on right now, unfortunately. It fails on linking the resources (cannot find e.g. colours) – Antek Feb 27 '19 at 13:30
2

I got the solution.. Just enter the following lines into build.gradle(app) 

compileOptions {
        sourceCompatibility '1.8'
        targetCompatibility '1.8'
    }
abhi
  • 228
  • 3
  • 9
1

Options to resolve this (Priority Wise):

(Note: Follow next only if previous option doesn't work)

  1. update library declaration to following : implementation project(path: ':yourLibraryname', configuration: 'default')
  2. Android Studio > File > Invalidate Caches/Restart.
  3. Goto Users > (Current User) > .gradle > delete caches folder and open Android Studio again.
  4. "assemble" that specific library separately. (Use Gradle option available on RHS of Android Studio.
pravingaikwad07
  • 364
  • 1
  • 5
  • 20
0

I also encountered such problem today and hopefully I resolved it. The name of .aar file in my case is "open-web-sdk-release.aar".

Error was here, implementation files("libs/open-web-sdk-release") .

I replaced it with, implementation project(":open-web-sdk-release") .

Used this link ... https://developer.android.com/studio/build#module-level .

Mrudul Tora
  • 390
  • 2
  • 11