You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Tap magnifying glass icon to search, type something to get results
Tap (software) back back button
What happens: entire search activity closes and app returns to the main torrent list.
Expected behaviour: only keyboard closes.
Logs
No response
qBitController version
0.8.5
qBittorrent version
4.5.5
Android version
14, can not repro on Android 11
Additional details
Keyboard can be closed by tapping enter on the keyboard. Even if one does this and then tap one of the torrents and then go back by tapping back button, the keyboard pops up again. On Android 11, the keyboard pops up only if was open while tapping a search result.
Something to do with onBackPressed() being deprecated in API level 33 (Android 13)?
The text was updated successfully, but these errors were encountered:
That search bar is a native Android component that handles back presses by itself. I assume this is a bug on Android's side.
Anyway, I re-coded the torrent list screen with Compose and implemented the search bar manually. It now functions correctly. This change will be included in the next version.
Bug description
Launch qBitController
Tap magnifying glass icon to search, type something to get results
Tap (software) back back button
What happens: entire search activity closes and app returns to the main torrent list.
Expected behaviour: only keyboard closes.
Logs
No response
qBitController version
0.8.5
qBittorrent version
4.5.5
Android version
14, can not repro on Android 11
Additional details
Keyboard can be closed by tapping enter on the keyboard. Even if one does this and then tap one of the torrents and then go back by tapping back button, the keyboard pops up again. On Android 11, the keyboard pops up only if was open while tapping a search result.
Something to do with onBackPressed() being deprecated in API level 33 (Android 13)?
The text was updated successfully, but these errors were encountered: