Closed ludovicroland closed 2 years ago
This is not so easy to do without forcing users to migrate to Gradle 4.10 and above. Android took the shortcut and made that a requirement.
Since this project is not only for Android, I think we would like to keep backward compatibility.
The following is what I did for SAP. It is just for idea, may not be enough. https://github.com/novoda/gradle-static-analysis-plugin/pull/165/files#diff-46504f51605469d88fd5592bafb1c72eR10
I have the same problem, how to fix it???????
Hey, just to be clear this is supposed to be a warning. Everything should be working as expected.
This definitely spams Gradle build logs like crazy (especially for projects with a lot of modules), but yes things still work for now
I also want to know how to ignore this warning
It is a warning but that API ...will be removed at the end of 2019
🥴
Yes, this is a good solution if anybody wants to contribute.
I fixed this issue as fowllowing option
change api fileTree(include:['*.jar'],dir:'libs')
to
...
api files('libs/lib1.jar')
api files('libs/lib2.jar')
...
I fixed this issue as fowllowing option change
api fileTree(include:['*.jar'],dir:'libs')
to... api files('libs/lib1.jar') api files('libs/lib2.jar') ...
If we do it this way, wouldn't that be a lot of individual .jar
imports though?
ext.kotlin_version = '1.3.21' dependencies { classpath 'com.android.tools.build:gradle:3.4.0' classpath "org.jetbrains.kotlin:kotlin-gradle-plugin:$kotlin_version" }
Change the kotlin version to 1.3.21, this method solves my problem
When I did debug. It says
WARNING: API 'variant.getPackageLibrary()' is obsolete and has been replaced with 'variant.getPackageLibraryProvider()'. It will be removed at the end of 2019. For more information, see https://d.android.com/r/tools/task-configuration-avoidance. REASON: The Kotlin plugin is currently calling this API. We are working to solve this. WARNING: Debugging obsolete API calls can take time during configuration. It's recommended to not keep it on at all times.
I feel very sorry, I am not the author of this project and I am not involved in development. So I don't know why I received your email.
@SnowyTomorrow you received an email because you commented above and you're following this thread as a result.
@afollestad many thanks
Hey @Shouheng88 sorry, but we work on open source projects when we can in our spare time. If you have any idea of how to workaround then feel free to contribute that as a PR.
Was this problem fixed? plz fix it, it blocked my project
How this warning blocked your project? it's just a log as far as I know 🤔
Just update your gradle.properties with android.debug.obsoleteApi=true
and sync the gradle files. Rerun the emulator. Works fine !!
thanks for the tip @SrilakshmySooraj!
Just update your gradle.properties with
android.debug.obsoleteApi=true
and sync the gradle files. Rerun the emulator. Works fine !!
I try but still not work =.=
Just ignore it. It shouldn't be a blocker if you're using Gradle 5.5.
Just ignore it. It shouldn't be a blocker if you're using Gradle 5.5.
I'm so sad,I using Gradle 5.5, but still not work 🤔
2019 is passing, is anyone have a idea to fix this issue?
Created a Pull request regard this issue, thanks for the guy who comment here for the idea (I can not figure out who comment). I tested the implementation on one of my android project with gradle version 5.4.1 and another android project with gradle version 4.6 and it seems work.
Hi,
After the migration of an Android project from Android Studio 3.2.1 to Android Studio 3.3 I have update the following components and plugins :
I now have the following warning into the project :
Here the full stacktrace :
So according to this stacktrace, into the
AndroidAttachments.groovy
file, the line 51 (variant.outputs[0].packageLibrary
) should be changed.I am using the version
0.9
of the library.