Fixed
Status Update
Comments
cl...@google.com <cl...@google.com>
le...@google.com <le...@google.com> #2
Some things to work out before making the annotations type-use:
- Determine guidelines for type nullability in public API
- Determine rules for when type nullability can change in public API
- Confirm that intellij nullability lint works as expected for type-use nullability annotations
- Test what the impact would be on existing arrays (due to ambiguities of type-use annotations on arrays)
- Confirm usage of type-use
androidx.annotation.NonNull/Nullable
in metalava won't break anything for platform
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