Describe the bug
I have some aars with support dependencies that byebyejetifier is not identifying.
To Reproduce
Steps to reproduce the behavior:
For example download swipe-reveal.layout.1.4.1.aar which throws errors if jetifier is not enabled,
If you apply the conversion with jetifier-standalone, then error goes away when running the app.
Use default swipe-reveal.layout lib withoutjetifier-standalone, in a project with jetifierEnabled = false
Run ./gradlew canISayByeByeJetifier -Pandroid.enableJetifier=false
Build will be successful
Run the app where the swipereveallayout is used, it will throw error regarding support libraries.
Expected behavior
ByebyeJetifier should detect the classes where support libs are used.
Additional context
I have over 20 aar libs in my project, knowing that byebyejetifier is not correctly checking all of them requires me to apply jetifier-standalone to everyone of them to assure no problem will happen.
The following aar also presents problems, probably it is not being detected from the way it is implemented as a module:
Describe the bug I have some aars with support dependencies that
byebyejetifier
is not identifying.To Reproduce Steps to reproduce the behavior:
For example download
swipe-reveal.layout.1.4.1.aar
which throws errors ifjetifier
is not enabled,If you apply the conversion with jetifier-standalone, then error goes away when running the app.
jetifier-standalone
, in a project withjetifierEnabled = false
./gradlew canISayByeByeJetifier -Pandroid.enableJetifier=false
Expected behavior ByebyeJetifier should detect the classes where support libs are used.
Additional context I have over 20 aar libs in my project, knowing that byebyejetifier is not correctly checking all of them requires me to apply jetifier-standalone to everyone of them to assure no problem will happen.
The following aar also presents problems, probably it is not being detected from the way it is implemented as a module: