IssueTracker

Apologies Jeremy, I realized we have a tracking ticket for the sheet APIs specifically: b/261409034 Feel free to keep this issue or mark as duplicate of the other one.

Sounds good. I will make it a dup.

Actually, we should automatically do it when withLoadStateFooter is called as we are the ones creating the concat adapter.

Btw, you can also fix it more explicitly. Here is an update to your sample to scroll to top on first load:

findViewById<RecyclerView>(R.id.recycler_view_paging).apply {
            val linearLayoutManager = LinearLayoutManager(context)
            this.layoutManager = linearLayoutManager
            this.adapter = samplePagingAdapter.run {
                this.withLoadStateFooter(NetworkLoadStateAdapter { this.retry() })
            }
            var firstLoad = true
            samplePagingAdapter.addOnPagesUpdatedListener {
                if (samplePagingAdapter.itemCount > 0 && firstLoad) {
                    linearLayoutManager.scrollToPositionWithOffset(0, 0)
                    firstLoad = false
                }
            }
            this.setHasFixedSize(true)
        }

Granted, it won't play well with state restoration but for that, you can check if savedInstanceState is not null before adding the pages listener.

Re: comment#7

The fix for this bug was released in paging 3.2.0-alpha03 so you shouldn't need the workaround anymore.

Can you try updating to that version or later?

Can you please upload a minimal sample project that reproduces the issue you see?

Re: comment#11 Can you please upload a minimal sample that reproduces the issue?

var isFirstLoad = true //Either in your ViewModel or in your generic component

adapter.apply {
      addOnPagesUpdatedListener {
            if (itemCount > 0 && firstLoad) {
                recyclerView.scrollToPosition(0)
                isFirstLoad = false
            }
      }
}

recyclerView.scrollToPosition(0) works better than linearLayoutManager.scrollToPositionWithOffset(0, 0)

This might help solve the issue for now

The fix was reverted. We will work on re-landing it.