We're testing 3.14.4 and noticed that when we fling a PDF (to scroll quickly) and then single tap while it's scrolling, the activity always snaps back to the first page. However, if we let the fling stop scrolling and then single tap, it does not snap to the first page. Is this a known issue, or is it perhaps just us? We have made some minor edits to the sources, but nothing we think would cause this.
I've exposed some logging that helps illustrate what's happening. I fling and then single tap when it hits page 11. Then it snaps back to page 1.
I upgraded to 3.14.5beta3 but still noticed the issue on my Nexus 5X (API 25). However, I restarted the phone and the issue went away. I don't know what to make of it, and perhaps it was simply something going on with the phone. Or, maybe it was stale data or code that remained in the .apk when Android Studio updated it.
Still, I would like to press a little further because we had one user mention this issue a while ago in production, and I wasn't able to reproduce it then. Are there any conditions where the PDF resets or snaps the position back to the first page? Perhaps if something happens to the touch or page states, or if there are resource constraints on the phone (that could have been freed up when I restarted the phone)? I realize that this is a bit of an open ended question, but if you have any insights, I'd appreciate it.