Library incompatible with AndroidX
See original GitHub issueHi, I use your library (v2.2.2) and when I try to update to version 3.0 or 3.1, my Gradle sync fails with error:
Failed to transform file 'pinentryedittext-1.3.3.aar' to match attributes {artifactType=processed-aar} using transform JetifyTransform
I see the issue in PinEntryEditText library https://github.com/alphamu/PinEntryEditText/issues/40 and solution is to use version 2.0 to properly support Android Jetpack.
Could you update the library to use the new version? Thanks.
Issue Analytics
- State:
- Created 5 years ago
- Comments:12 (7 by maintainers)
Top Results From Across the Web
Unable to import any androidx libraries due to incompatible ...
I'm using gradle 6.7. Incompatible because this component declares a component, with the library elements 'aar' and the consumer needed a ...
Read more >Known issues with Android Studio and Android Gradle Plugin
Find out about current known issues with Android Studio and the Android Gradle ... from a previous version of Android Studio or an...
Read more >Version incompatibility issue! 'com.android.support:support-v4 ...
Version incompatibility issue! 'com.android.support:support-v4:28.0.0' ... There are errors that I can't fix as seen in the picture.
Read more >espresso 3.0.1 incompatible with play-services-auth:11.6.0 in ...
espresso 3.0.1 incompatible with play-services-auth:11.6.0 in android library module.
Read more >Unity build Error - ' SDK incompatible with the package ' How ...
* What went wrong: Could not determine the dependencies of task ':launcher:lintVitalRelease'. > This project uses AndroidX dependencies, but the ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

Nice 😃 Perhaps you can update also Usage in readme, so people know they have this opportunity to select 2 different artifacts of the library.
The Article you linked says
From my understanding that means the actual implementation does not have to be changed, only dependencies and import statements. So it should be easy to provide two branches and builds of the library (the one with the support library that already exists and the new AndroidX) for the short term. In the long term I will probably end supporting the support library and only continue development with AndroidX.
I tried the migration as described in the article you linked @Robyer. It looks like that worked out just fine, so we have a fully AndroidX supporting version of the library and testApp in the
androidxbranch now.