Status Update
Comments
cl...@google.com <cl...@google.com>
le...@google.com <le...@google.com> #2
May I ask why P3? This is blocking for me to go to prod, I'd really like some inputs about what is going on so I can either fix or build a repro to have this fixed.
ch...@google.com <ch...@google.com> #3
For the ideas on what to take a look, how do you use LazyListState.layoutInfo in your app? Will it continue growing if you comment out such usages?
ap...@google.com <ap...@google.com> #4
It happens even on screens that does not use the layoutInfo it just require many up / down flings.
LazyColumn(state = rememberLazyListState())
The only thing all screen have in common in that they have multiple item {} item{} block :(
Just in case the app is in open beta at
My main question before trying to do complex repro, is how much will it be relevant with all the recent changes in alpha 8 about Lazy stuff? And side question when
Description
IMPORTANT: Please readhttps://developer.android.com/studio/report-bugs.html carefully and supply
all required information.
Android Studio Build: 4.1 Canary 9
Version of Gradle Plugin: 4.1.0-alpha09
Version of Gradle: 6.4
Version of Kotlin: 1.3.70
OS: Arch Linux
Version of Compose: dev-11
Steps to Reproduce:
Result: Crash with stacktrack:
I believe that this might be due to the fact that the HorizontalScroller is being treated the same for each iteration of the loop meaning that the HorizontalScroller is initalised with a ScrollerPosition with rememberSavedInstanceState with the same id causing a conflict and hence crashing