I'm having a crash caused by navigating from a screen containing a lazy column to another one, then navigating back. The stack trace doesn't point to any of my code so I'm not sure what's going on
it is not a know bug. if you can provide a reproducible sample we can try to fix that
z
zt
05/20/2022, 8:50 PM
I might have narrowed the issue down, the way I'm doing search is by setting the paging source to a new instance, which I doubt is the best way of doing it. Testing with it set already to an instance of a paging source seems to fix the bug. I'm not really sure how else to create a source for paging data when the search button is pressed though
zt
05/20/2022, 8:51 PM
It looks like this in my viewmodel
Copy code
var results by mutableStateOf<Flow<PagingData<DomainSearch.Result>>>(emptyFlow())
private set