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
{{ message }}
Repository navigation
Commit f87fa1c
Browse filesBrowse the repository at this point in the historyBrowse files
fix(ios): tap a visible Back control on header-less screens and refuse without a blind tap
In-app back looked for a back control only in the navigation bar and in
the header band. A screen with its header hidden (a React Native
native-stack screen with headerShown: false) keeps its back control in the
content, and React Native exposes a Pressable without a role as an untyped
element. Back missed it, tapped the empty top-leading point, saw no change,
and refused.
The runner now accepts a hittable button or untyped element whose whole
label is "Back", anywhere on screen, after the header candidates.
The top-leading tap now runs only when XCTest rejected a query or the
channel is penalized, as the docs already state. A readable tree that names
no back control refuses without tapping whatever sits top-leading.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
'Show foreground app/activity (Android and HarmonyOS; iOS and macOS answer per session)';
288
288
constbackCommandDescription=
289
-
'Navigate back in the app or through system navigation. Use in-app for the app navigation stack and system when the platform back behavior is required. On iOS, a single-screen iPhone or an iPad whose app provably fills its screen can use a top-leading tap when the app tree is unreadable, with before/after visual verification. A capture failure reports an unknown outcome.';
289
+
'Navigate back in the app or through system navigation. Use in-app for the app navigation stack and system when the platform back behavior is required. On iOS, in-app back taps the header back control or a visible control labeled exactly Back, and refuses on a readable screen that has neither. A single-screen iPhone or an iPad whose app provably fills its screen can use a top-leading tap when the app tree is unreadable, with before/after visual verification. A capture failure reports an unknown outcome.';
290
290
consthomeCommandDescription=
291
291
'Send the selected device to its home screen. This leaves the app session open but moves the foreground away from the app.';
-`back` uses app-owned back navigation: visible in-app back UI on Apple targets, and the back keyevent on Android. `--in-app` names this default explicitly.
127
-
- On iOS, a single-screen iPhone or an iPad whose app provably fills its screen, `back` can use a top-leading tap when the app tree is unreadable. It compares the screen before and after the tap. If the screen cannot be captured, the command reports an unknown outcome; inspect the screen before you retry.
127
+
- On iOS, `back` taps the header back control. On a screen without one, it taps a visible control labeled exactly `Back`, wherever it sits. When the app tree is readable and has neither, `back` refuses with `in-app back control is not available` and taps nothing; use `back --system` for the edge-swipe gesture.
128
+
- On a single-screen iPhone or an iPad whose app provably fills its screen, `back` can use a top-leading tap when the app tree is unreadable. It compares the screen before and after the tap. If the screen cannot be captured, the command reports an unknown outcome; inspect the screen before you retry.
128
129
-`back --system` sends system back input: the Android back keyevent, the iOS back gesture, or the tvOS Siri Remote Menu button. macOS has no system back, so it reports unavailable.
129
130
-`orientation portrait|portrait-upside-down|landscape-left|landscape-right` works on iOS and Android mobile targets only. On ADB-backed Android it turns auto-rotate off, and the lock persists after the session ends until something turns it back on. A foldable iPhone simulator (iPhone Duo) refuses `portrait-upside-down`, and refuses every rotation in a scoped simulator set (`--ios-simulator-device-set`).
130
131
-`orientation auto` hands rotation back to the sensor on ADB-backed Android, local or Limrun (`accelerometer_rotation=1`, `user_rotation` untouched), and reports `orientation: "auto"`. It does not wait for the display to rotate, because there is no target rotation: the sensor decides, and an emulator usually settles on portrait. Every other backend refuses `auto` with `UNSUPPORTED_OPERATION`.
0 commit comments