[BUG] recyclerView.computeVerticalScrollOffset() always return 0
π Describe the Bug
Upgrade pdf-viewer 2.1.1 version After upgrading pdf-viewer to version 2.1.1, recyclerView.computeVerticalScrollOffset() always returns 0. The offset cannot be determined, resulting in an inability to determine whether the PDF has scrolled to the bottom. Is there any good solution?
π Library Version
- PDF Viewer Version: [e.g., 2.1.1]
πΆ Steps to Reproduce
Please follow these steps to reproduce the issue:
-
Initial Setup/Library Method Used: [e.g.,
initWithUrlmethod] - Actions Taken: [e.g., Clicked on 'Load PDF']
- Unexpected Behavior: [e.g., PDF not loading]
- Relevant Code/Stack Trace: [Include code snippet or stack trace if applicable]
π€ Expected Behavior
What did you expect to happen?
πΌοΈ Screenshots/Videos
If applicable, add screenshots or videos to help explain your problem.
π± Smartphone Info:
- Device: [e.g., Samsung Galaxy S10]
- OS: [e.g., Android 11]
- Library Version: [e.g., 2.0.0]
π» Code Snippets
Include relevant code snippets or links to code repositories.
π Log Output/Stack Trace
Include any error logs or stack trace for more context.
π¬ Additional Context
Add any other context about the problem here. Mention if the issue is consistent, specific scenarios where the bug occurs, etc.
Thank you for creating your first issue. We appreciate your help in making this project better. We will look into it, and get back to you soon. Need help or want to discuss this issue? Join our Discord community here to ask questions and discuss this issue live!
Hey Can you please verify this in https://github.com/afreakyelf/Pdf-Viewer/releases/tag/v2.2.0
β οΈ Hi @cbuemc β this issue is marked Fixed and has had no activity for 25 days. It will be automatically closed in 5 days if no updates are made. Please comment or reopen if needed.
π Hi β this issue was marked as Fixed but hasnβt had any activity since then.
If itβs still relevant, feel free to leave a comment or remove the stale label to keep it open.
Otherwise, it will be automatically closed in 5 days.
πͺ Hi @{{ issue.user.login }} β this issue was automatically closed because it was marked as Fixed and had no activity for 5 more days after being marked stale.
If you believe this was closed in error, feel free to reopen it or leave a comment.