Add tvOS simulator support#292
Conversation
mobilecli can now list and drive tvOS simulators, not just iOS ones. - Recognise tvOS runtimes when parsing the simulator runtime string and report the `tvos` platform. Version parsing now also handles tvOS, watchOS, and xrOS. - Pick the DeviceKit runner bundle id and process name based on the platform, so the `devicekit-tvosUITests` runner is found on tvOS. - Install the arm64 tvOS runner artifact during agent install, with its own version and checksum entries. - Map the tvOS Siri Remote buttons (UP, DOWN, LEFT, RIGHT, SELECT, MENU, PLAY_PAUSE) in the WDA press-button client. - Include tvOS devices when resolving device model metadata. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
WalkthroughThis PR adds tvOS simulator support to the agent installation pipeline and simulator device abstraction. New constants define the tvOS agent version, runner bundle ID, and artifact checksum. The simulator runtime parser is extended to handle tvOS/watchOS/xrOS strings, and new helpers derive the platform identifier, runner bundle ID suffix, and runner process name per platform. The 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
cli/agent.go (1)
270-283: 🎯 Functional Correctness | 🟠 Major | ⚡ Quick win
runtime.GOARCHblocks Rosetta-on-Apple-Silicon installs. An amd64 CLI build still maps tox86_64, so the tvOS branch rejects the arm64 simulator runner even on a supported Apple Silicon host. Use host/simulator architecture here instead.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@cli/agent.go` around lines 270 - 283, The tvOS install path in installAgentOnSimulator is using runtime.GOARCH to decide the runner architecture, which incorrectly rejects Apple Silicon hosts running an amd64 CLI under Rosetta. Update the architecture selection logic in installAgentOnSimulator so it uses the actual host/simulator architecture rather than the Go build architecture, and keep the tvOS arm64-only check aligned with that value so supported Apple Silicon installs are not blocked.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@cli/agent.go`:
- Around line 31-33: The pinned tvOS archive checksum in the install mapping is
still tied to a locally built artifact, so the new tvOS path in
downloadAndInstallAgent() cannot verify the GitHub release successfully. Update
the checksum/version entry used for the devicekit-tvos-Sim-arm64.zip artifact to
match the published release before shipping, or add an explicit early error in
downloadAndInstallAgent() / the tvOS install path that reports the runner is not
published yet instead of attempting the install.
---
Outside diff comments:
In `@cli/agent.go`:
- Around line 270-283: The tvOS install path in installAgentOnSimulator is using
runtime.GOARCH to decide the runner architecture, which incorrectly rejects
Apple Silicon hosts running an amd64 CLI under Rosetta. Update the architecture
selection logic in installAgentOnSimulator so it uses the actual host/simulator
architecture rather than the Go build architecture, and keep the tvOS arm64-only
check aligned with that value so supported Apple Silicon installs are not
blocked.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: 90092912-a644-496c-a26a-41e70ca2ab3c
📒 Files selected for processing (5)
cli/agent.godevices/common.godevices/ios.godevices/simulator.godevices/wda/press-button.go
| // tvOS simulator runner is published from the same devicekit-ios release. | ||
| // Update this checksum whenever the tvOS runner artifact is rebuilt/republished. | ||
| "devicekit-tvos-Sim-arm64.zip": "49061f17046055c7e89dbf27067a59ab0bffd9d7d14d63031d5411c5963ccb81", |
There was a problem hiding this comment.
🎯 Functional Correctness | 🟠 Major | ⚡ Quick win
The pinned tvOS checksum makes the new install path unreleasable.
downloadAndInstallAgent() only accepts the archive fetched from the GitHub release after SHA-256 verification. The PR notes this hash is still from a locally built tvOS artifact, so the new tvos install flow cannot succeed as shipped. Please update the checksum/version pair before merge, or fail earlier with an explicit “runner not published yet” error.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@cli/agent.go` around lines 31 - 33, The pinned tvOS archive checksum in the
install mapping is still tied to a locally built artifact, so the new tvOS path
in downloadAndInstallAgent() cannot verify the GitHub release successfully.
Update the checksum/version entry used for the devicekit-tvos-Sim-arm64.zip
artifact to match the published release before shipping, or add an explicit
early error in downloadAndInstallAgent() / the tvOS install path that reports
the runner is not published yet instead of attempting the install.
There was a problem hiding this comment.
It's mentioned there in the comment.
There was a problem hiding this comment.
@setoelkahfi Acknowledged — I did see the comment.
My concern is that the note documents the limitation, but the code path in cli/agent.go will still try to download and verify the tvOS artifact at runtime. If that checksum is still for a locally built archive, the agent install flow for tvOS will fail rather than degrade gracefully.
So I’d still consider this open unless one of these happens before merge:
- the checksum/version is updated to the published artifact, or
- the tvOS install path returns an explicit early error like “tvOS runner not published yet”.
(•ㅅ•)ゞ
|
@setoelkahfi thank you so much for this PR. I'll take a look. I see you also updated mobile-mcp, thank you so much for this! This also means mobilewright may inherit this automatically :). I'll review. |
What
mobilecli can now list and drive tvOS simulators, not just iOS ones.
Changes
tvosplatform. Version parsing also handles tvOS, watchOS, and xrOS.devicekit-tvosUITestsrunner is found on tvOS.agent install, with its own version and checksum entries. The tvOS runner is arm64-only for now.Notes
The tvOS runner checksum currently points at a locally built artifact. Update it once the runner is published from a devicekit-ios release.
Testing
mobilecli deviceslists a booted tvOS simulator withplatform: tvos, andio buttonpresses move its focus as expected.Related