widget.RecyclerView.assertNotInLayoutOrScroll possibly overextended [37084037]

Fixed

Bug

Status Update

No update yet.

Description

za...@gmail.com

created issue #1

Feb 28, 2016 02:49AM

Library used (support-v4, appcompat-v7, ...): recyclerview
Version used: 23.2.0
Theme used: Theme.AppCompat
Devices/Android versions reproduced on: Nexus 6P - 6.0.1

- Relevant code to trigger the issue.

Run the app built from this branch, comes up in a few places namely around using a recyclerview with an InfiniteScrollListener:

https://github.com/hzsweers/plaid/tree/z/compat

- A screenrecord or screenshots showing the issue (if UI related).

N/A

Comments

za...@gmail.com <za...@gmail.com> #2Feb 28, 2016 02:50AM

Here's another log file from the real development project, reproduced using the method with 1-finger touch described above.

dn...@google.com <dn...@google.com> Feb 29, 2016 06:21AM

Assigned to dn...@google.com.

dn...@google.com <dn...@google.com> #3Feb 29, 2016 08:53AM

Status: New

Thanks for the bug report. I was able to repro and I have a fix in review.

al...@gmail.com <al...@gmail.com> #4Feb 29, 2016 10:40AM

Great! Do you know in which version it'll be updated/fixed and available for download?

yb...@google.com <yb...@google.com> #5Feb 29, 2016 05:52PM

Assigned to yb...@google.com.

The fix is still in review. We will update this bug once the fix lands.

yb...@google.com <yb...@google.com> Mar 1, 2016 05:47PM

Marked as fixed.

la...@gmail.com <la...@gmail.com> #6Mar 2, 2016 12:33AM

+1 I also am seeing this crash in the latest recyclerview update.

tm...@gmail.com <tm...@gmail.com> #7Mar 2, 2016 10:40PM

I just checked with the com.android.support:design:23.3.0 library, and it doesn't crash any more but the bug is still there, resulting the UI issue described in my initial post above (i.e. the snackbar doesn't come back to its original position).
In the official page of Support Library (

http://developer.android.com/tools/support-library/index.html) it's mentioned that you've fixed the crash issue but nothing about the ugly UI bug. Was it so hard or you guys just overlooked/ignored it?