Fixed
Status Update
Comments
cl...@google.com <cl...@google.com>
ap...@google.com <ap...@google.com> #2
A couple of questions:
1. Have you saw crash in real device or only in simulators?
2. Do you use dynamic feature for language ID?
1. Have you saw crash in real device or only in simulators?
2. Do you use dynamic feature for language ID?
na...@google.com <na...@google.com> #3
Tested on Android 12 Emulator with custom executor, but cannot repro this issue.
Description
Paging currently supports collecting
Flow<PagingData>
from non-main thread, which is useful for controlling the context in which all of Paging's initialization and object creation happens. It also control the default context for transforms, since that is applied on the internalFlow<PageEvent>
which is collected from call to.submitData()
.Unfortunately, collecting
PagingData
and calling.submitData
all happen internally in paging-compose so there is no way to control this behavior if usingLazyPagingItems
.Ideally we can make the context configurable, but if not we should at least have a more sane default.