IndexOutOfBoundsException but I can't reproduce it. about dpadrecyclerview HOT 5 CLOSED

@MRDHR released in 1.2.0-alpha03

from dpadrecyclerview.

Hi @MRDHR can you please share the full stacktrace? I'm interested in knowing if the index was greater than the adapter size or if it was negative.

from dpadrecyclerview.

Hey @MRDHR. I managed to reproduce the crash with this UI test:

    @Test
    fun testSelectingPositionOutOfBoundsDoesNotCrash() {
        val numberOfItems = 500
        launchFragment(TestAdapterConfiguration(numberOfItems = numberOfItems))

        selectPosition(numberOfItems + 100, smooth = true, waitForIdle = false)

        Thread.sleep(1000L)

        mutateAdapter { adapter ->
            adapter.setList(MutableList(numberOfItems + 10) { it })
            adapter.notifyItemRangeInserted(0, 100)
        }

        onRecyclerView("Request layout") { recyclerView ->
            recyclerView.requestLayout()
        }

        assertFocusAndSelection(numberOfItems + 9)
    }

Please check if you're doing the following in your side:

1. Using DiffUtil and submitList to notify adapter changes correctly
2. Check if your setSelectedPosition calls are using indexes within bounds of the adapter contents

There's a PR here to address this specific crash now, but you might still hit some issues if you don't follow those 2 steps: #179

from dpadrecyclerview.

Regarding the two points you mentioned

1: I did not use DiffUtil to update data, I used replace. That is, items clear, then add all, and finally execute notifydatasetchanged
2: I can ensure that my items are not empty with setSelectedPosition.

The data updates are not very frequent, and they are not updated every 1 second.

At present, I have added the setSelectedPosition operation to be executed after recyclerview.post, and added the judgment for position>=0&&position<=items. size -1

from dpadrecyclerview.

Looking forward to your pull request being synchronized to the master and release an aar

from dpadrecyclerview.