IssueTracker

It appears that AGP indeed excludes androidx libraries from jetifier https://android.googlesource.com/platform/tools/base/+/a0e4d77697/build-system/gradle-core/src/main/java/com/android/build/gradle/internal/dependency/JetifyTransform.kt#184

In our case however it's a custom exclude list for Buck build system and we've definitely forgot to exclude androidx dependencies.

I'm not sure about other users reporting this issue (also on StackOverflow btw https://stackoverflow.com/q/53193657/1562633),  you might want to double-check that to be sure

Yes, when giving libraries directly to jetifier it is important to exclude the AndroidX ones.I will look into what we could do in jetifier to skip them, maybe by looking into the version file.

However in #1 I see reference to Android Studio 3.2.1. I would like to ask the reporter to help to clarify their repro case.

Seems like we have a repro case with usage from a third party library. Taking the bug back.

This is going to be fixed in jetifier beta03.

Once we publish beta03 you can start using it as part of you gradle build if you do add the following lines:
buildscript {
   dependencies {
       classpath 'com.android.tools.build.jetifier:jetifier-processor:1.0.0-beta03'
   }
}

This allows you to get the fix asap without waiting for updated version of AGP / AS.

NOTE: this bug will be marked as fixed once beta03 is published.

Any ETA on beta03?

We are aiming for this week. Worst case would be probably the next week.

I added below lines to my gradle file.

buildscript {
   dependencies {
       classpath 'com.android.tools.build.jetifier:jetifier-processor:1.0.0-beta03'
   }
}

But I get these below errors on gradle sync.

ERROR: Unable to resolve dependency for ':frollo-android-sdk@debug/compileClasspath': Failed to transform file 'core-ktx-1.0.1.aar' to match attributes {artifactType=processed-aar} using transform JetifyTransform
ERROR: Unable to resolve dependency for ':app@releaseUnitTest/compileClasspath': Failed to transform file 'activity-1.0.0-alpha02.aar' to match attributes {artifactType=processed-aar} using transform JetifyTransform
ERROR: Unable to resolve dependency for ':app@releaseUnitTest/compileClasspath': Failed to transform file 'lifecycle-process-2.0.0.aar' to match attributes {artifactType=processed-aar} using transform JetifyTransform
ERROR: Unable to resolve dependency for ':app@releaseUnitTest/compileClasspath': Failed to transform file 'lifecycle-service-2.0.0.aar' to match attributes {artifactType=processed-aar} using transform JetifyTransform
...more like this

Am I missing something else to configure?

I believe this is due to us accidentally releasing incorrect mappings in beta03. Can you please try beta04 and let me know if that helps?

Same errors using beta04 as well.

Same here, dozens of Failed to transform errors

Could you build from the command with --stacktrace and let us know the result?

Please find the attached result of the command "gradlew build --stacktrace"

@15: I see "Transformation hasn't been executed yet". Can you use Gradle 5.1.1+ to get a more detailed stacktrace? (See Bug 119951660 for why we need Gradle 5.1.1+.)

It's working with gradle-5.2.1-all and gradle-5.1.1-all, but it's failing with gradle-4.10.3-all.
Errors similar to post above with gradlew build --stacktrace:
ERROR: Unable to resolve dependency for ':app@debug/compileClasspath': Failed to transform file 'crashlytics-2.9.9.aar' to match attributes {artifactType=processed-aar} using transform JetifyTransform

Yes. It's working with gradle-5.1.1-all. But, it's failing with gradle-4.10.1-all.

Do you recommend to use jetifier beta04 & gradle-5.1.1-all with Android Studio 3.3.1 & Gradle plugin v3.3.1 ? Are all of them compatible with each other?

I was expecting Gradle 5.1.1+ to show an error with a stack trace that pinpoints the root cause. However, it is passing for you, so it's not clear where to debug from here.

Anyway, since it's working for you, I would recommend trying that combination for now. The only issue I'm aware of with Jetifer 1.0.0-beta04 is that it will fail when detecting libraries that need to be jetified but have signatures in them (Issue 115556774), but if you don't run into that issue, then no need to worry.

Yep but seems like instant run is not too friendly with AS 3.3.2 and Gradle 5.1.1+
Anyway, thank you for participation here, it's possible to stick with this combination for now!

Support PC

Thanks! I will stick with this combination for now!

I'm seeing the same: beta04 + gradle-4.10.1-all fails, but with gradle-5.1.1-all it works fine.

FYI, in AGP 3.4.0-rc03 and 3.5.0-alpha09, the AGP has been updated to use Jetifier 1.0.0-beta04: https://android.googlesource.com/platform/tools/base/+/f7fdfbb94aebb43b7e9515c683fd71b8c905ee79.

Please let us know if you still run into this issue when using the above AGP versions.

When will 3.4.0-rc03 release?

It should be some time today.

Closing as fixed. Please re-open if you encounter anymore issues.