Status Update
Comments
jb...@google.com <jb...@google.com>
cl...@google.com <cl...@google.com>
ap...@google.com <ap...@google.com> #2
Andrey, I haven't changed AnimatedVisibility
since alpha01, so I don't expect any behavior change. This looks like it may be an issue with subcompose, could you please take a look?
cl...@google.com <cl...@google.com> #3
I updated to 1.0.0-alpha09 but still experiencing the same result.
je...@gmail.com <je...@gmail.com> #4
cc+ Matvei for input on Scaffold
il...@google.com <il...@google.com> #5
Hm, interesting, form the quick looks it seems like nothing changed in scaffold in alpha08. The only thing we've done around alpha07 is migrated scaffold to subcompose and it directly affects the padding parameter.
Louis, do you have any ideas is that might've caused the problem?
lu...@gmail.com <lu...@gmail.com> #6
Hm, I can't immediately reproduce with an example locally so not sure what's going on, might be related to how / when subcomposition invalidates
cl...@google.com <cl...@google.com> #7
Hi just another update, I updated to 1.0.0-alpha10 but still experiencing the same result.
pr...@google.com <pr...@google.com> #8
Same issue on beta01.
Description
Component used: Navigation: androidx.navigation:navigation-compose
Version used: 2.8.0-beta02
Per Ian's comment here https://issuetracker.google.com/issues/346505952#comment2 it should not be needed.
Repro here:https://github.com/hrach/navigation-compose/commit/6342c95cc0c57a5e8598f92241d59a658c538071