We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
So as discussed by mail a few times, Google now starting with AGP 8.0 alpha 10 enforce this.
And you can no more compile tasker plugins.
For the moment it's still possible to opt out with android.nonFinalResIds=false in gradle.properties but for how long.
android.nonFinalResIds=false
It's also necessary to disable lint rule: NonConstantResourceId
NonConstantResourceId
This was delayed for a long time, but it's really time to think about alternative solution for the future.
The text was updated successfully, but these errors were encountered:
Sorry, I should've mentioned. You can already use resource Ids as strings with the latest update :) Can you please try that? Thanks in advance!
Sorry, something went wrong.
You always forget to push to Github :p
Will try that in the coming weeks thanks. Does it require a specific Tasker version or 100% internal to the lib?
Hhmm, but it's on Github too 😅
1b32696#diff-d67fd9793dc8662b4ced6d48c86d8aefb24b2bb8d2b55f12a79ac4a1b2407b4f
It's internal to the lib so Tasker version doesn't matter.
Hope this helps!
Yes it's present now :) But when you released the library to maven it was not :p Anyway no big deal.
No branches or pull requests
So as discussed by mail a few times, Google now starting with AGP 8.0 alpha 10 enforce this.
And you can no more compile tasker plugins.
For the moment it's still possible to opt out with
android.nonFinalResIds=false
in gradle.properties but for how long.It's also necessary to disable lint rule:
NonConstantResourceId
This was delayed for a long time, but it's really time to think about alternative solution for the future.
The text was updated successfully, but these errors were encountered: