Fixed
Status Update
Comments
rv...@google.com <rv...@google.com>
rv...@google.com <rv...@google.com>
rv...@google.com <rv...@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.
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
rv...@google.com <rv...@google.com> #4
Woops, sorry, If you guys had the previous ViewPagerCrash test app, I forgot to push (was exhasuted after debugging) I pushed one more time for the latest reproducible code
pr...@google.com <pr...@google.com> #5
We'll have a look, thanks for reporting and repro steps / sample app. Stay tuned for updates on this issue.
Description
Component used: TV
Version used: 1.0.0-alpha03
Devices/Android versions reproduced on: Emulator (Android TV 4K API 33)
This is pretty simple to reproduce. For items within an immersive list, the
focusableItem
modifier should be applied to each list item in which the background should change. IffocusableItem
is used withclickable
clickable no longer works.I think passing an
InteractionSource
tofocusableItem
which is also shared withclickable
will resolve the issue.