[gwdp]

Why

Keep Appium controller output and its simulator preview in separate log phases.

How

• Keep serve-sim output in its own preview phase while the Appium controller step stays active.
• Stream Appium output into its controller step.
• Clean up partial startup failures and remove Appium files even when shutdown fails.

Test Plan

• Fresh Devin review completed without findings.
• CI passed on the current head.
• Local Appium session started through EAS CLI, Universe API/workflow worker and the rebuilt build-tools. The website preview worked with serve-sim 0.6.3 on an iPhone 17 Simulator; an Appium client connected through ngrok and read the Settings UI. Appium output and serve-sim output were ingested under separate controller and preview phases.

Earlier and automated validation

After restacking, Codex ran 62 focused tests and built all 13 EAS packages successfully. Changed-file lint, formatting and changelog validation passed. Claude reviewed the earlier controller slices and found no correctness issues.

Earlier launch E2E covered Universe-generated steps through build-tools download/install/start to serve-sim on a real iOS Simulator, checking one app start, launch arguments and the deep link. Those runs used loopback cloud tunnel/reporting adapters and a pinned local build/device. The current local session used real ngrok tunnels. Hosted workers were not tested. On this machine, Appium's default capabilities select the first booted Simulator, so the test client explicitly selected the intended iPhone 17 UDID.

Screenshots

Authorship and LLM use

Gabe wrote the initial implementation, directed the iterations and requested the split once he was happy with the result. Codex made fixes, split the PRs and updated this description; Claude and Devin reviewed the broader work. The reviews led to redaction and shutdown refinements. Gabe reviewed the final code through #4601, including this Appium diff. Local Appium validation is described above; hosted execution remains untested.

[gwdp]

Codex separated Appium and simulator-preview logging, corrected cleanup and changelog details, and restacked this layer under Gabe's direction. Gabe reviewed the final code through #4601, including this Appium diff. Current-head CI is green. Earlier local Appium/website validation and screenshots are preserved; hosted execution was not tested.

— Codex

[douglowder]

eas-cli now uses changesets for changelogs (#4580). The required "Check for a changeset" check fails on PRs that edit CHANGELOG.md.

To update this PR:

1. Revert the changes to CHANGELOG.md.
2. Run yarn changeset, select the changed packages and the bump type, and write the summary.
3. Commit the new file in .changeset/.

The release adds the PR link and the author to the entry. If this PR needs no changelog entry, revert the CHANGELOG.md changes and add the "no changelog" label.

[gwdp]

Rebased this layer onto gwdp/serve-sim-agent-device-logs and moved its release note from CHANGELOG.md into its own changeset. Current-main behavior was preserved.

Validation: focused build-tools tests, changeset validation, changed-file lint/format and build-tools typecheck passed. No new native or hosted acceptance was run for this restack.

Published head: 18c09c0ae526fd499ab42140dea38075c44a9c7f.

— Codex

[github-actions]

✅ Thank you for adding a changeset!