Fixed
Status Update
Comments
du...@google.com <du...@google.com> #2
Some new information? This issue is already over a year old, it was just shifted, and the new ticket here seems to be ignored. This should have a higher Priority then P3.
I feel like this is a serious issue that should get more attention. When working with RecyclerViews you had the possibility of setting up if a ViewHolder is able the be recycled.
All the solutions to circumvent this problem here are either hacks in regards to how the Keyboard is opened, or you ditch LazyColumn completely and use a Column, which is not a solution for complex layouts.
I feel like this is a serious issue that should get more attention. When working with RecyclerViews you had the possibility of setting up if a ViewHolder is able the be recycled.
All the solutions to circumvent this problem here are either hacks in regards to how the Keyboard is opened, or you ditch LazyColumn completely and use a Column, which is not a solution for complex layouts.
ma...@justpinch.com <ma...@justpinch.com> #4
and cause the other focusable element could not access touch
Description
Component used: Paging 3.0.0
Version used: alpha02
Devices/Android versions reproduced on: Nokia 7.1/Android 10
Steps to reproduce:
step11_loading_state
:alpha02
IOException
, use airplane mode etc)Sample project illustrating the problem attached for convenience.
I've confirmed the retry call makes it all the way up to
PageFetcherSnapshot
and is collected fromretryChannel
. From there I got lost in the world of suspend functions and breakpoints without any useful context...Further observations:
alpha01
.FAIL
toON_INITIAL_LOAD
inGithubPagingSource
to confirm)