fix: test case 11 and 12 flaky tests

.maestro/tests/room/jump-to-message.yaml

@@ -15,8 +15,9 @@ tags:
       PASSWORD: ${output.account.adminPassword}
 
 # should jump to an old message and load its surroundings
+# Search instead of scroll: this fixture keeps sinking in the activity-sorted list
 - runFlow:
-    file: '../../helpers/navigate-to-room.yaml'
+    file: '../../helpers/search-and-navigate-room.yaml'
     env:
       ROOM: 'jumping'
 - extendedWaitUntil:
@@ -61,7 +62,7 @@ tags:
 
 # should load messages on scroll
 - runFlow:
-    file: '../../helpers/navigate-to-room.yaml'
+    file: '../../helpers/search-and-navigate-room.yaml'
     env:
       ROOM: 'jumping'
 - extendedWaitUntil:
@@ -82,7 +83,7 @@ tags:
 
 # should search for old message and load its surroundings
 - runFlow:
-    file: '../../helpers/navigate-to-room.yaml'
+    file: '../../helpers/search-and-navigate-room.yaml'
     env:
       ROOM: 'jumping'
 - extendedWaitUntil:
@@ -188,7 +189,7 @@ tags:
 
 # should navigate to a thread from another room
 - runFlow:
-    file: '../../helpers/navigate-to-room.yaml'
+    file: '../../helpers/search-and-navigate-room.yaml'
     env:
       ROOM: 'jumping'
 - extendedWaitUntil:

.maestro/tests/room/room-last-message-thread-50-plus.yaml

@@ -13,8 +13,9 @@ tags:
       PASSWORD: ${output.account.adminPassword}
 
 # should open a room where the last message is a thread containing more than 50 messages.
+# Search instead of scroll: this fixture keeps sinking in the activity-sorted list
 - runFlow:
-    file: '../../helpers/navigate-to-room.yaml'
+    file: '../../helpers/search-and-navigate-room.yaml'
     env:
       ROOM: 'maestro_test_load_threads'
 - extendedWaitUntil:

.maestro/tests/room/room.yaml

@@ -35,6 +35,14 @@ tags:
       id: message-composer-input
     timeout: 60000
 - inputText: ':joy'
+# Typing ':' alone lists every emoji, and 'joy' is already among the first ones, so waiting on
+# autocomplete-item-joy alone can match that unfiltered list, where the row sits outside the
+# visible area of the list and the tap lands on the keyboard instead. 'joystick' only shows up
+# once the debounced search for 'joy' resolves, so it tells us the list is the one we want.
+- extendedWaitUntil:
+    visible:
+      id: autocomplete-item-joystick
+    timeout: 60000
 - extendedWaitUntil:
     visible:
       id: autocomplete-item-joy
@@ -161,7 +169,13 @@ tags:
 - tapOn:
     id: emoji-searchbar-input
 - inputText: 'laughing'
-- hideKeyboard
+# iOS already dismisses the keyboard when the search results show up, and hideKeyboard fails
+# when there's no keyboard to dismiss
+- runFlow:
+    when:
+      platform: android
+    commands:
+      - hideKeyboard
 - extendedWaitUntil:
     visible:
       id: emoji-laughing