Fixed
Status Update
Comments
cl...@google.com <cl...@google.com>
le...@google.com <le...@google.com> #2
Is this really a P1? This seems less priority than the perf work that I am doing but if it is a P1 I will block that and work on this.
ch...@google.com <ch...@google.com> #3
I'm happy to move it to a p2, but it seems like a pretty big correctness issue that we should take a look at in the near future. I'm also happy to help look at this myself if you can give me some pointers on what the issue may be
ap...@google.com <ap...@google.com> #4
This is not simple as and will change once Jim lands the threading of the composer.
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