Live evidence the coordinator runs serially on the connected iPhone. Each item names the exact command, the environment it needs, and the rendered error that proves the change. Do not paraphrase the JSON: paste it. Record the commit SHA the build under test was made from.
Build the CLI first, then stop any warm daemon so the run is on this commit:
pnpm build && pnpm clean:daemon
node --experimental-strip-types src/bin.ts daemon stop --all || trueenv -u AGENT_DEVICE_IOS_TEAM_ID -u AGENT_DEVICE_IOS_PROVISIONING_PROFILE \
node --experimental-strip-types src/bin.ts --json \
prepare ios-runner --platform ios --device "<physical iPhone name>"Expected: exit non-zero, one error object with
{
"code": "COMMAND_FAILED",
"message": "xcodebuild build-for-testing failed",
"hint": "Configure signing in Xcode or set AGENT_DEVICE_IOS_TEAM_ID for physical-device runs.",
"details": { "reason": "signing_no_development_team" }
}hint, logPath and diagnosticId are top-level, never inside details. Also record the Xcode
version (xcodebuild -version) so the signing_no_development_team fixture in
packages/platform-apple/src/runner/__tests__/runner-startup-failure-fixtures.ts can move from
shipped-sniff-trigger to captured and its xcodeVersion from unobserved to that version.
Paste the whole error so the fixture's output can become the capture and its command can be
recorded.
env AGENT_DEVICE_IOS_TEAM_ID="<your team id>" \
AGENT_DEVICE_IOS_BUNDLE_ID="com.apple.TestFlight" \
node --experimental-strip-types src/bin.ts --json \
prepare ios-runner --platform ios --device "<physical iPhone name>"Expected: same envelope shape with
details.reason: "bundle_identifier_already_registered" and a hint naming
AGENT_DEVICE_IOS_BUNDLE_ID. A registered-but-foreign identifier may surface the Failed registering bundle identifier line or the App Identifier ... is not available line; both rules produce this
one reason, so record which line xcodebuild printed.
These do not need the iPhone, but do need a real xcodebuild run; record output with the Xcode
version so the matching fixture's provenance can be upgraded:
# devtools_security_developer_mode_disabled (macOS admin state, no device work)
DevToolsSecurity -status
# signing_provisioning_profile_missing: point the runner build at a profile that is not installed,
# then read the reason off the same prepare command as above.
env AGENT_DEVICE_IOS_TEAM_ID="<your team id>" \
AGENT_DEVICE_IOS_PROVISIONING_PROFILE="no-such-profile-installed" \
node --experimental-strip-types src/bin.ts --json \
prepare ios-runner --platform ios --device "<physical iPhone name>"Expected: details.reason is signing_provisioning_profile_missing. If a different reason appears,
say which one did and treat the fixture as unconfirmed rather than editing the rule to fit.
xcodebuild reports a settings mismatch with a line that names a profile ("has conflicting
provisioning settings"). #2680 deliberately publishes build_failed_unclassified for it, because no
capture has proved which lever clears it. To reach it, pin a profile while leaving automatic signing
on:
env AGENT_DEVICE_IOS_TEAM_ID="<your team id>" \
AGENT_DEVICE_IOS_PROVISIONING_PROFILE="match-development" \
node --experimental-strip-types src/bin.ts --json \
prepare ios-runner --platform ios --device "<physical iPhone name>"Expected: either signing_provisioning_profile_missing (xcodebuild complained about the profile
first) or build_failed_unclassified. Paste the error and the xcodebuild -version either way: a
capture of the conflicting-settings line is what would let a follow-up name the cause, and the
capture must show which build setting disagrees before any hint naming a lever is written.
Build the CLI first, and stop any warm daemon so the run is on this commit (same preamble as the #2680 section above).
xcrun devicectl device info details --device "<udid>" --json-output /tmp/device-details.json
node -e 'const d=require("/tmp/device-details.json").result.deviceProperties;console.log(JSON.stringify({developerModeStatus:d.developerModeStatus,ddiServicesAvailable:d.ddiServicesAvailable}))'
xcodebuild -versionExpected: {"developerModeStatus":"enabled","ddiServicesAvailable":true} on a healthy device, plus
the Xcode version. Also record bootState and tunnelState from the same file: those two are what
make a ddiServicesAvailable: false an answer at all rather than a device that was not listening.
packages/platform-apple/src/core/__tests__/fixtures/ios-device-info-details.json holds this payload
and packages/platform-apple/src/runner/__tests__/runner-startup-failure-fixtures.ts records the two
state pairings, both at invented-shape until this capture moves them to captured. Paste the raw
values rather than a summary.
The committed payload is masked, and the mask is a rule with a test, not a one-time edit:
hardwareProperties.serialNumber and deviceProperties.bootedSnapshotName carry MASKED,
hardwareProperties.ecid is 0, and connectionProperties.tunnelIPAddress is a documentation-only
fd00: address. Everything the reader consumes — the toggle, the image, bootState, tunnelState,
OS build — stays verbatim. If you refresh this capture, apply the same mask in both the result
block and the mirrored properties block, and leave the states alone.
node --experimental-strip-types src/bin.ts --json prepare ios-runner --platform ios --device "<physical iPhone name>"Expected: success as before, and a ios_runner_session_startup diagnostic whose timings include
verify_device_readiness. No reason may appear on a healthy device: the probe reads, it does not
guess. Record the verify_device_readiness duration next to verify_host_dev_tools_security.
Turn the toggle off on a device you are willing to re-pair (Settings > Privacy & Security >
Developer Mode, then restart), and rerun the prepare ios-runner command above.
Expected: exit non-zero with
{
"code": "COMMAND_FAILED",
"message": "The iOS device reports that Developer Mode is turned off",
"details": {
"reason": "device_developer_mode_disabled",
"developerMode": "disabled",
"developerDiskImage": "unavailable"
}
}hint is top-level and names Settings > Privacy & Security > Developer Mode. Record what
developerDiskImage says; either value is acceptable as long as the toggle stays the reason.
This is the pairing the old hint got wrong, so it is the evidence that matters. Reach it with a device whose iOS build is newer than the installed Xcode supports, or before Xcode finishes installing device support for a freshly paired phone, with Developer Mode on.
Expected: details.reason is device_developer_disk_image_unavailable, details.developerMode is
enabled, and the hint names device support WITHOUT mentioning Settings > Privacy & Security. If
the toggle reason appears here instead, that is the bug this issue exists to fix: paste the whole
error and the /tmp/device-details.json payload rather than adjusting a rule.
Capture the details payload at the same moment as the refusal, and check it says
tunnelState: "connected" and bootState: "booted". A ddiServicesAvailable: false read any other
way is not this case: an asleep or unreachable device has the same field and no obstacle, and the run
must not name device support for it. The hint you get here is the one core/devicectl.ts owns and the
device report carries, so it is worded identically to the hint devicectl output produces for the
same complaint — paste both strings and confirm they match character for character.
Unplug the iPhone (or shut it down) after a session exists, then rerun the prepare ios-runner
command.
Expected: the failure names whatever the transport could not reach, and no details.reason of
device_developer_mode_disabled or device_developer_disk_image_unavailable appears anywhere in the
error. An unreadable device is never diagnosed. This is also the case that catches a sleeping phone
reporting ddiServicesAvailable: false: if the hint here says Let Xcode finish preparing this device, the corroboration rule has been lost, and pasting the payload with its tunnelState and
bootState is the evidence — do not adjust the rule to make the run pass.
With the iPhone's Developer Mode toggle off AND sudo DevToolsSecurity -status reporting the
developer-tools setting disabled, run the prepare ios-runner command.
Expected: one error, whose details.reason is device_developer_mode_disabled. The Mac's reason is
the other one (devtools_security_developer_mode_disabled) and must not be what you get: the phone's
fix needs no admin rights on the Mac, so the probe that can be acted on has to be the one that speaks.
Record which of the two appears; a captured pairing here is what would let a follow-up drop the
ordering argument.
Run any command that crashes the app under test, then a second command that fails for its own reason (for example a selector that no longer exists).
Expected: the second error carries no details.runnerFailureReason. Before this change it inherited
target_app_axruntime_coretext_crash from the first command's lines in runner.log. If the repro
is not reachable, say so; the pairing is covered by
packages/platform-apple/src/runner/__tests__/runner-failure-diagnostics.test.ts.