This repository was archived by the owner on Jan 10, 2025. It is now read-only.
[Paging with Network] Fix consumeAsFlow can be collected just once #892
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The issue
Currently, the Paging with Network demo uses
ReceiveChannel.consumeAsFlow
which crashes the App on configuration changes. The reason, IMO, is when the Activity is recreated, the ViewModel's posts value starts collecting again for the new Adapter. This goes against the contract ofconsumeAsFlow
which allows up to one consumer.How to reproduce:
The fix
This PR use the
ReceiveChannel.receiveAsFlow
instead. It allows multiple receivers.