Component used: androidx.paging:paging-compose
Version used: 3.2.1
Devices/Android versions reproduced on: Pixel 6 Pro API 32 emulator

val emptyApi = MutableStateFlow(PagingData.empty<String>()).collectAsLazyPagingItems()
val emptyList = MutableStateFlow(PagingData.from(emptyList<String>())).collectAsLazyPagingItems()
assertThat(emptyApi.loadState.refresh).isInstanceOf(LoadState.Loading::class.java)
assertThat(emptyList.loadState.refresh).isNotInstanceOf(LoadState.Loading::class.java)

That last line shouldn't pass. Both empty the API call and from(emptyList()) should be marked as not loading. Ian mentioned the difference was in the cachedPageEvent that's in the from method, but not the empty one.

For what it's worth, I would consider this a breaking API change. In places where people were relying on empty to be an initial loading state to show a progress indicator, it won't if this bug is fixed.

As an alternative, maybe expose a PagingData.loading() which does what empty does now.