Verified
Status Update
Comments
yb...@google.com <yb...@google.com>
cc...@google.com <cc...@google.com>
cc...@google.com <cc...@google.com> #2
Thanks for finding this, fixed internally, will go out with next release (both to 1.0 and androidx).
cc...@google.com <cc...@google.com> #3
Fixed released in 1.0.1
Note though that this won't be released in AndroidX (2.0) until its next release.
Note though that this won't be released in AndroidX (2.0) until its next release.
ma...@gmail.com <ma...@gmail.com> #4
Eas
ae...@gmail.com <ae...@gmail.com> #5
...
[Deleted User] <[Deleted User]> #6
Eas
[Deleted User] <[Deleted User]> #7
Epic game
ma...@gmail.com <ma...@gmail.com> #8
GameOver
Description
Version used: 1.0.0
Devices/Android versions reproduced on: Moto E4/7.1.1
This is a pretty simple bug. In PagedStoragedDiffHelper / OffsettingListUpdateCallback onMoved is incorrectly implemented
@Override
public void onMoved(int fromPosition, int toPosition) {
mCallback.onRemoved(fromPosition + mOffset, toPosition + mOffset);
}
This is a huge issue in large lists. In my case i have a paged list of 30000 items. If i move item in position 15000 to item in position 15001, mCallback.onRemoved is called with parameters of 15000 and 15001. The second param (15001) is number of items removed.. so basically my adapter now things items 15000-30000 have been removed from the list which is clearly not the case