Fixed
Status Update
Comments
ju...@google.com <ju...@google.com>
je...@google.com <je...@google.com>
hm...@google.com <hm...@google.com> #2
Is this fixed? I'm still seeing this issue with AGP 8.1.0-beta01 + Gradle 8.1
va...@gmail.com <va...@gmail.com> #3
The fix has not been landed.
hm...@google.com <hm...@google.com> #4
Due to this bug in CI we hit configuration cache invalidation 100% of the time. Can we make sure the fix lands soon? And especially before 8.1.0 stable.
na...@google.com <na...@google.com> #5
I cc'ed you on the CL which should be landed this week.
ia...@google.com <ia...@google.com> #6
Aurimas, is this 8.1 blocking for Androidx? If not, feel free to remove the "Blocking release" label.
Description
Coming from https://issuetracker.google.com/issues/244700433 , I changed my build.gradle files to build.gradle.kts and I had the following line:
instead of:
So the android proguard rules weren't loaded which probably caused this.
Would it be possible to warn about this when building using Gradle and potentially throw / fail the build if you're trying to use a proguard file which does not exist?