Fixed
Status Update
No update yet.
Comments
ju...@google.com
je...@google.com
hm...@google.com
I also have the same issue so it seems to be a real problem.
hm...@google.com
why is this marked has Obsolete? this is still a bug that is happening and its difficult to fix.
for all who are looking for a solution use this:
http://stackoverflow.com/questions/16200972/android-css-positionfixed-after-a-device-rotate
for all who are looking for a solution use this:
na...@google.com
This bug was linked in a change in the following release(s):
androidx.wear.compose:compose-foundation:1.1.0-alpha07androidx.wear.compose:compose-material:1.1.0-alpha07androidx.wear.compose:compose-navigation:1.1.0-alpha07
ia...@google.com
Using gradle 7.4.2, I had a typo in my proguard file which led to about 2 hours of churn. I'd like to request this be treated as an error instead of a warning.
gd...@google.com
+1 to upping warning to error. I wasted couple of days due to missing file, even had a help of another engineer and we couldn't figure out the issue until I went back and laboriously checked config files for any typos/missing files.
hm...@google.com
We don't see any reason why not to update it to an error. I will create a bug for updating the warning to an error, but it will be implemented in the next major AGP version (9.0) as it's a breaking change. Projects that were building before may stop building.
Description
Coming from
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?