Avoid jetifier skipping mixed androidx / support libraries [148462462]

Fixed

Feature Request

Reviewed (L1)

Status Update

No update yet.

Description

pa...@google.com

created issue #1

Jan 28, 2020 07:39PM

Jetifier has a detection to skip libraries that contain androidX references in their bytecode. However this does not work for libraries that are migrated only partially. As a remedy we need to also look for android.support references and if we find any we rewrite the library (and show a warning). This still makes the detection useful as we don't scan strings. So in case of library with ambiguous or backwards compatibility strings that is depending only on androidx we still skip it.

Comments

ap...@google.com <ap...@google.com> #2Jan 29, 2020 01:06PM

Hi Ed, Thank you so much for these suggestions. I've been reviewing them and merging them in. Hopefully it should be live. I've included a thank you note too in the article.

pa...@google.com <pa...@google.com> #3Jan 30, 2020 12:10PM

Great! Thanks a lot, I'll look for the live updates soon!

ga...@google.com <ga...@google.com> #4Jan 30, 2020 12:21PM

Here is a sample of the warning message:

> Transform artifact wearable-2.5.0.aar (com.google.android.support:wearable:2.5.0) with JetifyTransform
WARNING: [Processor] Library '/usr/local/google/home/gavra/.gradle/caches/modules-2/files-2.1/com.google.android.support/wearable/2.5.0/52dec610511a6ccde7c4dd3480a82909fc83f5aa/wearable-2.5.0.aar' contains references to both AndroidX and old support library. This seems like the library is partially migrated. Jetifier will try to rewrite the library anyway.
Example of androidX reference: 'androidx/viewpager/widget/PagerAdapter'
Example of support library reference: 'android/support/v4/view/VelocityTrackerCompat'

ga...@google.com <ga...@google.com> #5Feb 22, 2020 07:56PM

Assigned to pa...@google.com.

Can we update AGP 4.0 to use this version?

hu...@google.com <hu...@google.com> #6Feb 24, 2020 09:37AM

Yes, I'll send out a CL for that.

hu...@google.com <hu...@google.com> #7Feb 26, 2020 11:35AM

Marked as fixed.

Jetifier 1.0.0-beta09 have been included in AGP 4.0.0-beta02 and 4.1.0-alpha02:

https://android.googlesource.com/platform/tools/base/+/3839282c272e1fe6d93f800ea6c5772ef505f7d8#

[Deleted User] <[Deleted User]> #8Apr 25, 2020 09:20PM

unfortunately, the jetifier still fails for this libraries:

com.facebook.android:facebook-android-sdk:5.0.1
com.github.nikartm:image-support:1.0.5
com.clevertap.android:clevertap-android-sdk:3.7.2

I've also did this: https://github.com/bumptech/glide/issues/3185#issuecomment-619436009 but still no success

My setup: AGP: 4.0.0-beta05 Gradle Wrapper: 6.1.1 Kotlin: 1.3.72

still working on the sample project for to reproduce this

hu...@google.com <hu...@google.com> #9Apr 27, 2020 09:48AM

Can you please attach a stack trace? That'll help confirm if what you're seeing is the same or a different issue.

[Deleted User] <[Deleted User]> #10May 2, 2020 06:26PM

turns out, this fixed my issue for now: https://github.com/facebook/facebook-android-sdk/issues/591#issuecomment-619435280

[Deleted User] <[Deleted User]> #11May 2, 2020 06:27PM

in a clean project this is not hapenned. but with existing codebase migration, there's a lot of 3rd-party library that still using Android Support Library, and the process always fails, my original SO questions: https://stackoverflow.com/questions/61179356/androidx-jetifier-unable-failed-to-transform-3rd-party-transitive-dependency-tha

hu...@google.com <hu...@google.com> #12May 4, 2020 02:00PM

Okay, glad to hear that your issue has been fixed now.

If you run into another Jetifier-related issue, please send us a stack trace of the failure, and we will investigate it. Thanks!