Key was already registered [159026663]

Fixed

Bug

Status Update

No update yet.

Description

ni...@google.com

created issue #1

Jun 15, 2020 05:12PM

I'm experiencing a runtime crash as compose believes I'm using a duplicate key.

https://paste.googleplex.com/6153325403701248

I'm iterating over a collection of @Immutable data classes and emitting @Composables into a VerticalScroller. Each of my items emits a HorizontalScroller and it seems that this fails when creating a ScrollerPosition:

https://devrel-review.git.corp.google.com/c/samples/android/compose/+/153852/3/Jetsnack/app/src/main/java/com/example/jetsnack/ui/home/Home.kt#117

I'm working around this issue with a key(…).

Comments

cl...@google.com <cl...@google.com> Jun 15, 2020 05:33PM

Assigned to ch...@google.com.

ch...@google.com <ch...@google.com> #2Jun 15, 2020 09:16PM

Reassigned to an...@google.com.

And create a non-compose app will just works fine.

an...@google.com <an...@google.com> #3Jun 15, 2020 09:18PM

Same issue here

an...@google.com <an...@google.com> #4Jun 15, 2020 09:20PM

Same issue here, app crashes on start when using android-gradle 7.1.0-alpha04 and AS Canary 4

an...@google.com <an...@google.com> #5Jun 19, 2020 03:41PM

aurimas@, are you the right person for triaging Android Studio version-specific issues? I saw you upgraded AndroidX to Bumblebee Canary 3 last week. This bug report might be specific to Bumblebee Canary 4, I'm not certain.

ap...@google.com <ap...@google.com> #6Aug 4, 2020 12:02PM

Marked as fixed.

Tested this quickly locally, it seems that the studio template creates a project that crashes out of the box. Updating compose_version to 1.0.0-rc02 and kotlin-gradle-plugin to 1.5.10 fixed the crash for me locally. We likely want to update studio template to use the latest of compose and kotlin.

Issue 159026663