Status Update
Comments
mo...@google.com <mo...@google.com>
al...@google.com <al...@google.com> #2
Hello, can you please attach a sample that reproduces your error?
na...@google.com <na...@google.com> #3
I’ve attached two screen recordings demonstrating the mediator's behavior during the first and second launches after installation. Additionally,
al...@google.com <al...@google.com> #4
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
allNewsItems
value 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
cl...@google.com <cl...@google.com> #5
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: We have created a bunch of benchmark util functions for benchmarking Compose code. We often get requests for how to do this. We should consider releasing these util functions as a library for developers to use to benchmark their composable functions the same way we benchmark ours.
Use Case:
ComposeBenchmarkRule.benchmarkLayoutPerf
ComposeBenchmarkRule.benchmarkDrawPerf
ComposeBenchmarkRule.toggleStateBenchmarkRecompose