I have a simple Android app developed in Android studio. When I built it with Gradle 4.10.1, there was no warning or error. When I updated Gradle to Version 5.1.1, I got the following warning:
Task :app:processDebugResources UP-TO-DATE
Changing the value for a property with a final value has been deprecated. This will fail with an error in Gradle 6.0.
Can anybody help? Thank you in advance.
It’s just a warning. Not a „bug“. So there’s nothing to worry about Your build didn’t fail because of it. Right? Or did it?
The current Gradle release is 5.4.1. Judging by their apparent release schedule, you’ve got more than a year before version 6 is out.
That’s plenty of time for you to refactor your build script to whatever the warning is nudging you to refactor. Isn’t it?
Here is more details about the issue:
Task :app:processDebugResources UP-TO-DATE Changing the value for a property with a final value has been deprecated. This will fail with an error in Gradle 6.0.
The problem is: I have no idea what needs to be done to the Gradle scripts. I suspect the warning came from codes not controlled by me. That’s why I call it a “bug”.
We’d need more details to be able to know what exactly is causing your warning. Please, can you run this command?
gradle -i -Dconsole=verbose --scan :app:processDebugResources
When it asks for your permission to share the scan, answer yes (if you are OK with sharing). Then share with us the URL it outputs for you?
Thanks in advance.
Thanks for your suggestion. My build scan is published below:
Thanks. I’m sorry. I need to ask you to run it one more time. Please? Like this this time:
gradle -i -Dconsole-verbose --warning-mode all --scan :app:processDebugResources
Here is the new build scan:
Thanks again for looking into it.
As near as I can tell, going by the scans, something in the
com.android.application plugin is to blame. My best guess would be probably somewhere around
The scans say you’re already using the most up-to-date Android plugin. So I don’t think there’s anything you can do about the warning. Except wait until Google refactors their plugin to align with Gradle 6.0.