I found out that there was a mistake on the ViewModel. Pager was created like this:

fun page(type: String) = Pager(
    config = PagingConfig(pageSize = 10),
    pagingSourceFactory = {
        TenantPagingSource(getTenantListUseCase, type)
    }
).flow.cachedIn(viewModelScope)

and collected like this:

viewModel.page("shop").collectAsLazyPagingItems()

This works with

1.6.0-alpha01

but doesn't work with

1.6.0-alpha02

When I fix it like this

val page = Pager(
    config = PagingConfig(pageSize = 10),
    pagingSourceFactory = {
        TenantPagingSource(getTenantListUseCase, "shop")
    }
).flow.cachedIn(viewModelScope)

or collect like this:

val shops = remember {
    viewModel.page("shop")
}.collectAsLazyPagingItems()

it works on the alpha02 too: But I really wonder how it's related to the compose version.

It sounds like what you should be doing instead is having a MutableStateFlow to represent your type and using

flatMapLatest

on that flow to create the Pager and return the Flow from it, then cachedIn the result. Then whenever your type changes, a new Pager and PagingSource gets created

I don't know if changing type is even something you expect to happen? Generally, that would be a fixed value that you'd already have in your ViewModel (i.e., it would be an argument to your screen that would be automatically available via

SavedStateHandle

, so you wouldn't need to pass the type manually to your ViewModel ever