| β¦ | β¦ | @@ -83,12 +86,15 @@ export function SettingsListScreen(props: { | |
| 89 | 92 | onChangeText: (query) => | |
| 90 | 93 | workspace.dispatch({ type: "query", tab: "settings", query }), | |
| 91 | 94 | placeholder: "Search settings", | |
| 95 | + | active: searching, | |
π‘ Medium settings/SettingsRouteScreen.tsx:95
On Android, pressing Back after opening Settings search and dismissing the keyboard navigates away instead of closing search and restoring the full Settings index. Passing active makes the search controlled, which disables AppBar.android.tsx's hardware-back handler, and SettingsListScreen registers no replacement; register a focused back handler here or retain the AppBar handler.
π€ Copy this AI Prompt to have your agent fix this:
| 1 | In file @apps/mobile/src/features/settings/SettingsRouteScreen.tsx around line 95: |
| 2 | |
| 3 | On Android, pressing Back after opening Settings search and dismissing the keyboard navigates away instead of closing search and restoring the full Settings index. Passing `active` makes the search controlled, which disables `AppBar.android.tsx`'s hardware-back handler, and `SettingsListScreen` registers no replacement; register a focused back handler here or retain the AppBar handler. |
Note
π€ Composer responding on behalf of wSedlacek
Fixed. Controlled AppBar search opts out of the built-in Back handler, so SettingsListScreen now registers useHardwareBack while search is open: dismiss keyboard first, then cancel search before any navigation.
Sorry, I'm unable to act on this request because you do not have permissions within this repository.