Has anybody seen an issue with LazyRow/LazyList an...

# compose

[Richard Z]

Has anybody seen an issue with LazyRow/LazyList and fillParentMaxSize failing to work in release builds, or a different issue with the same type of symptoms?

I’m running into a case where, on the first measure/layout pass, the fillParentMaxSize modifier is using the correct widthState value set by the LazyList. However, subsequent measure/layout passes (that happen basically immediately) seem to be using a new LazyItemScope instance which seems to not be receiving the parent width/height state, therefore causing fillParentMaxSize to effectively be a no-op.

Only an issue in my release builds, making it hard to debug. In debug builds, the same LazyItemScope instance is used for each of the measure/layout passes. Makes me wonder if somehow the LazyList is trying to update the “max size” on an old LazyItemScope? This is in Compose 1.3.1 🫣

[Hackintoshfive]

As a debugging step, have you tried disabling minification on release builds, to see if it is cauesd by R8?

[Richard Z]

I haven’t yet, I’ll try to give that a shot.

[Richard Z]

Yes, disabling our minification system fixes it. Thanks for the suggestion

[Hackintoshfive]

That's a bit worrying. It really shouldn't...

[Richard Z]

Yeah… we have some custom processing in our toolchain, though, so it’s probably something there.

[Hackintoshfive]

Unless your minification system is custom too (kudos if that works) it is probably just a matter of adding some -keep rules to proguard-rules.pro