Assigned
Status Update
Comments
ia...@google.com <ia...@google.com> #2
Found the issue, ugh
Noticed that when I do the following:
transaction.addToBackStack(null)
When adding a Fragment with ViewPager2, the above issue occurs, although, idk if it's becaugh of gcFragments() anymore.
As soon as I un-comment that line, the issue disappears.
Noticed that when I do the following:
transaction.addToBackStack(null)
When adding a Fragment with ViewPager2, the above issue occurs, although, idk if it's becaugh of gcFragments() anymore.
As soon as I un-comment that line, the issue disappears.
mn...@google.com <mn...@google.com>
ap...@google.com <ap...@google.com> #3
Is the Sample application, to reproduce, move back really fast between page 2 -> 1 and vice versa (they are bottom buttons) a couple times.
Wait a couple seconds and page 1 (the black page) should turn white meaning the Fragment has been removed.
As soon as you comment line 40 on MainActivity, and attempt again, the error does not persist
Description
Jetpack Compose version: 1.6.7
Jetpack Compose component(s) used: ComposeView
Android Studio Build: Android Studio Jellyfish | 2023.3.1 Build #AI-233.14808.21.2331.11709847, built on April 12, 2024
Kotlin version: 1.9.23
Steps to Reproduce or Code Sample to Reproduce:
We have been seeing this compose crash in production, but have not been able to reproduce it. We are currently doing some Recyclerview + ComposeView interoperability - our screen is essentially one vertical RecyclerView. One of the items within this RecyclerView contains a ComposeView that is inflated from an XML layout. We see in our logging a back press occurs before many (if not all) of these crashes.
Here is some RecyclerView.Adapter related code that would be relevant:
Stack trace: