Status Update
Comments
de...@dyson.com <de...@dyson.com> #2
Hello, can you please attach a sample that reproduces your error?
ad...@google.com <ad...@google.com> #3
I’ve attached two screen recordings demonstrating the mediator's behavior during the first and second launches after installation. Additionally,
di...@google.com <di...@google.com>
de...@dyson.com <de...@dyson.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
Description
Note Posting in here as I did not have permissions to post to
AndroidStudio > DesignTools > Compose Preview
Description:
The ability to have multiple
@PreviewParameters
in a Preview such that all combinations of said parameters are auto-generated.Use Case:
A simple example has been shown below. However, in practice, these might be sequences of more complicated data classes:
The above would then spit out previews for
MyCustomComponent
containing all combinations ofSampleTitleStrings
&SampleBodyStrings
. eg: