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 b813505
Browse filesBrowse the repository at this point in the historyBrowse files
fix(ios): address review round on the sole-screen route and nightly legs
- Help and docs: scope the top-leading back fallback to iOS (a single-screen
iPhone, or an iPad whose app provably fills its screen); Android uses a back
keyevent.
- Fixture: anchor the regression back control to the view's leading edge and
the safe-area top with a 64-pt height so it stays under the bounded fallback
sweep (x <= 44, y in [56, 96]) on landscape iPhones with side insets.
- Tests: restore iPad window-route coverage by closing the sole-screen route
through the probe's own unknown path (primaryApp answers nothing) and
dispatching back through the resolved window.
- Tests: assert .windowed exactly, and non-finite frames as .unknown.
- Shared rule: a non-finite frame component is an unknown read, not a window;
the bridge keeps the capture and the runner's evidence seam answers Unknown.
- Nightly: each leg asserts the booted simulator's family, the iPad leg records
a result bundle and asserts its seven selected tests executed, and the iPad
device name matches the models the macos-26 image ships for iOS 26.2 (M5).
Copy file name to clipboardExpand all lines: apple/runner/AgentDeviceRunner/AgentDeviceRunnerUITests/UnitTests/RunnerTests+XCTestEventBridgeTests.swift
'Show foreground app/activity (Android and HarmonyOS; iOS and macOS answer per session)';
289
289
constbackCommandDescription=
290
-
'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 a single-screen device where the app provably fills that screen, an unreadable app tree can use a top-leading tap with before/after visual verification. A capture failure reports an unknown outcome.';
290
+
'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 screencan use a top-leading tap when the app tree is unreadable, with before/after visual verification. A capture failure reports an unknown outcome.';
291
291
consthomeCommandDescription=
292
292
'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.
121
-
- On a single-screen device where the app provably fills that 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.
121
+
- 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.
122
122
-`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.
123
123
-`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.
124
124
-`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