Fixed
Status Update
Comments
mn...@google.com <mn...@google.com>
ap...@google.com <ap...@google.com> #2
Related bug - https://issuetracker.google.com/issues/124511903
Initial loads in LimitOffsetPagingSource run in transaction but subsequent loads do not because of cost of transaction. Loads rely on count query to return correct LoadResult.
If count query is outdated, i.e. large amount of data deleted, LimitOffsetPagingSource can return i.e. empty/wrong data and incorrect itemsBefore/itemsAfter/prevKey/nextKey. This can happen if outdated PagingSource doesn't get invalidated in time.
Initial loads in LimitOffsetPagingSource run in transaction but subsequent loads do not because of cost of transaction. Loads rely on count query to return correct LoadResult.
If count query is outdated, i.e. large amount of data deleted, LimitOffsetPagingSource can return i.e. empty/wrong data and incorrect itemsBefore/itemsAfter/prevKey/nextKey. This can happen if outdated PagingSource doesn't get invalidated in time.
Description
Jetpack Compose version:
compose-bom:2023.09.00
Jetpack Compose component(s) used:
Android Studio Build:
Build #AI-223.8836.35.2231.10406996, built on June 29, 2023
Kotlin version:
1.8.21
Steps to Reproduce or Code Sample to Reproduce:
Crash:
No crash: Both of the below implementation works
Stack trace (if applicable):