Originally created by @depwl9992 on GitHub (Sep 18, 2024).
What was the Problem?
When using the search feature, I can type out text if my device is vertical, but when it's rotated to a horizontal aspect, any text typed (and hidden by the popup keyboard) is entered right-to-left, resulting in a reversed search string.
Steps to Reproduce the Issue
Tap search icon in any library type or podcast RSS catalog search.
Rotate phone 90-degrees to horizontal
Tap search box
Note keyboard covers the search box
Blindly type in search term (ex. "fairy tale")
Close keyboard with back button or rotate phone to vertical
Entered search term is reversed (e.g. "elat yriaf")
Example:
What was Expected?
Vertical aspect typing:
Phone Model
Samsung Galaxy S21 5G
Phone OS
Android 14, One UI version 6.1
Audiobookshelf App Version
Android App - 0.9.76
Installation Source
Google Play Store
Additional Notes
Version Information:
Originally created by @depwl9992 on GitHub (Sep 18, 2024).
### What was the Problem?
When using the search feature, I can type out text if my device is vertical, but when it's rotated to a horizontal aspect, any text typed (and hidden by the popup keyboard) is entered right-to-left, resulting in a reversed search string.
### Steps to Reproduce the Issue
1. Tap search icon in any library type or podcast RSS catalog search.
2. Rotate phone 90-degrees to horizontal
3. Tap search box
4. Note keyboard covers the search box
5. Blindly type in search term (ex. "fairy tale")
6. Close keyboard with back button or rotate phone to vertical
7. Entered search term is reversed (e.g. "elat yriaf")
#### Example:
<img src="https://github.com/user-attachments/assets/8ecc7e1a-197e-490f-ac65-43b286d3b632" height="150px" target="_blank" />
<img src="https://github.com/user-attachments/assets/d3780b2b-367d-4a87-83ea-5fc61b2dd3da" height="150px" target="_blank" />
### What was Expected?
#### Vertical aspect typing:
<img src="https://github.com/user-attachments/assets/18c04ccf-9b84-484c-9db4-eb80ea7b6f03" width="150px" target="_blank" />
<img src="https://github.com/user-attachments/assets/ef40199a-8d38-482d-963a-3ce4262c725d" width="150px" target="_blank" />
### Phone Model
Samsung Galaxy S21 5G
### Phone OS
Android 14, One UI version 6.1
### Audiobookshelf App Version
Android App - 0.9.76
### Installation Source
Google Play Store
### Additional Notes
#### Version Information:
<img src="https://github.com/user-attachments/assets/5be777f5-470c-4261-8ee6-cc6e5b514065" width="150px" target="_blank"/>
adam
added the bug label 2026-04-24 23:46:41 +02:00
I'm not able to reproduce this right now with the latest version of the app using a Pixel Pro 9 with Android 16. Can you confirm if the bug still exists?
@jpeel commented on GitHub (Oct 24, 2025):
I'm not able to reproduce this right now with the latest version of the app using a Pixel Pro 9 with Android 16. Can you confirm if the bug still exists?
It would appear as though the search function is now corrected, at least in 0.10.1-beta running server v2.29.0 (my current configuration).
@depwl9992 commented on GitHub (Oct 28, 2025):
It would appear as though the search function is now corrected, at least in 0.10.1-beta running server v2.29.0 (my current configuration).
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @depwl9992 on GitHub (Sep 18, 2024).
What was the Problem?
When using the search feature, I can type out text if my device is vertical, but when it's rotated to a horizontal aspect, any text typed (and hidden by the popup keyboard) is entered right-to-left, resulting in a reversed search string.
Steps to Reproduce the Issue
Example:
What was Expected?
Vertical aspect typing:
Phone Model
Samsung Galaxy S21 5G
Phone OS
Android 14, One UI version 6.1
Audiobookshelf App Version
Android App - 0.9.76
Installation Source
Google Play Store
Additional Notes
Version Information:
@jpeel commented on GitHub (Oct 24, 2025):
I'm not able to reproduce this right now with the latest version of the app using a Pixel Pro 9 with Android 16. Can you confirm if the bug still exists?
@depwl9992 commented on GitHub (Oct 28, 2025):
It would appear as though the search function is now corrected, at least in 0.10.1-beta running server v2.29.0 (my current configuration).