Fixed
Status Update
Comments
sg...@google.com <sg...@google.com>
sg...@google.com <sg...@google.com> #2
Is this fixed? I'm still seeing this issue with AGP 8.1.0-beta01 + Gradle 8.1
ph...@gmail.com <ph...@gmail.com> #3
The fix has not been landed.
ra...@gmail.com <ra...@gmail.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.
ap...@google.com <ap...@google.com> #5
I cc'ed you on the CL which should be landed this week.
ap...@google.com <ap...@google.com> #6
Aurimas, is this 8.1 blocking for Androidx? If not, feel free to remove the "Blocking release" label.
ap...@google.com <ap...@google.com> #7
ap...@google.com <ap...@google.com> #9
Reassigning to Xav to review CP to 8.1 branch
ap...@google.com <ap...@google.com> #10
Scott, do we have a cherry-pick ready for the lint fix?
Description
I started seeing
minifyReleaseWithR8
task failure of my Compose project. It fails with some random project library jar, e.g.If I exclude this library from proguard, it'll fail with some next library - it can be both Compose one or any other, looks like message is unrelated to the problem.
By commenting code in the project, I've found out that I can fix the build by replacing one of
@StringRes param: Int
in composable function withparam: String
. But I still not sure if that's the root case.When trying to reproduce it in a sample project, I was able to reproduce it with even simpler code, that doesn't include int parameter. If I switch from compose-material to compose-material3, it builds fine.
MRE with dependencies is attached.