Status Update
No update yet.
Comments
be...@gmail.com
Hello, can you please attach a sample that reproduces your error?
mu...@gmail.com
I’ve attached two screen recordings demonstrating the mediator's behavior during the first and second launches after installation. Additionally,
se...@google.com
co...@google.com
Based on first_launch_after_installation.mp4, your paging state is indeed showing null for nextKey, so it makes sense that Paging concluded there are no more items to load.
So I think the question is why the PagingState contains only an empty page and null values. My guess is either
- RemoteMediator REFRESH actually returned empty data - what is the returned
allNewsItemsvalue on initial REFRESH? - RemoteMediator REFRESH successfully loaded data and inserted it into database, but Paging hasn't processed that yet by the time Append is triggered, so PagingState is empty.
The second case doesn't seem likely though.
If you attach an executable app, I can look into this further.
Otherwise, you may gain more insight through Paging logs with adb shell setprop log.tag.Paging VERBOSE. You can also try implementing RemoteKeys in this
ma...@google.com
Hey! I ran into this same issue. It is in fact the second case you mentioned and is documented
I've published a repo
Description
Description:
It would be really useful if it was possible to define scroll behaviour in a Material3 Scaffold so that when the content Composable is scrolled,
Use Case:
This feature is a standard behaviour in many apps that use XML and Java with HideBottomViewOnScrollBehavior and scollFlags. The hide on scroll behaviour was present in the Material 2 Guidelines for both Toolbars and BottomAppBars. As the NavigationBar in Material3 is especially space-consuming, hiding it on scroll is important.