openreads
openreads copied to clipboard
mateusz-bak
[BUG] screen size cut after barcode scan
Describe the bug The app available screen size gets smaller after certain actions are done. You can still scroll to access hidden content, though, so it's not completely unusable.
To Reproduce Steps to reproduce the behavior:
- Launch the app.
- Click on the + button
- Use barcode to scan.
- Scan an item. 4.1. If there is a book, both choosing an edition as well as add book will result in a smaller screen size. 4.2. If there is no book found, going back will also result in a smaller screen size. 4.3. In both cases, going back will not result in a smaller screen size.
Expected behavior Screen size to remain constant after any action.
Screenshots
After selecting an avalable book after a sucessfull barcode scan:
And after going back to my book list:
Additional info(please complete the following information):
- Manufacturer and model: Xiaomi Redmi Note 9
- Android version:MIUI Global 12.0.1 (Android 11 RP1A.200720.011)
- App version: 2.0.3
- App source (F-Droid, Google Play, Github): Google Play
Additional context This is my first time using the app, I've installed it a few days ago. I don't know if this should be expected behavior or if there is a setting that needs to be changed before first use.
Hi, thanks for reporting. Seeing this for the first time - this should not happen. Will be investigating this issue.
If you have any more info or information that could help please add them as well.
Update! I cannot reproduce it anymore. It has been a few weeks though, so I'm not sure what solved it.
@jrom99 Then it was probably an issue with the Flutter framework itself. The version that was used to build the newest app was updated. Glad to hear it is gone now!
The bug is happening again. When I scan a barcode and choose cancel, or when I choose an edition and then click ok or cancel, the screen is cut. This seems to be related to the keyboard, as I was able to reset the screen size by tapping on a textbox field.
Hi @jrom99, do you still have this problem with the last 2.2.0 release? Just checking
I'm having the same problem, I believe.
2024-01-06 18:21:48
2024-01-06 18:22:00
2023-01-06 18:22:14
2024-01-06 18:22:20
(P.S. Sorry for the multiple screenshots; it only just barely gets the point across, I think. I tried uploading a screen recording, but it said the file was too big.)
Details
- App Version: 2.3.0
- OS: Android 11
- Hardware: Motorola One 5G Ace
I see the visual behaviour is not consistent with this bug. Any ideas @PrivacyFriendlyMuffins what could be the cause on your device? I was never succesfull to reproduce the issue.
Do you have any Flutter knowledge? Maybe you could install debug version and check the logs for any errors.
@mateusz-bak, sadly I do not have any Flutter knowledge. I'm still learning how to code, heavy on the "learning" part. All I know is pretty much what I described. Is there a log file or something I can send that would provide more context? Or would it help if I posted screenshots of my settings page or whatever?
Sorry for not being very helpful...
No worries @PrivacyFriendlyMuffins If you feel like learning Flutter I can guide you through the steps you could take to get the logs.
Firstly you can follow Flutter installation docs: https://docs.flutter.dev/get-started/install
After that you need to pull the code for Openreads from Github.
Then you can turb on developer options in your phone, then turn on USB debugging. Do a backup of your books because you will loose them. Connect phone to pc and run the app from your IDE.
@mateusz-bak Hi, I'm really sorry I pretty much dropped off the face of the earth. I had stuff happen that kind of...took my attention elsewhere. I sincerely apologize!
Regarding the debugging, I'm going to have to decline the instruction after all, for all that my delayed response is worth. I am sorry for wasting your time... :(