xcode-dev-loop
WHEN building, testing, or visually verifying an Xcode project from the command line — xcodebuild runs, Swift Testing result reading, simulator install/launch, and screenshots; NOT for authoring Swift source or tests; returns the canonical build/test/inspect loop.
mintuz · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add mintuz/skills --skill xcode-dev-loop技能说明
name: xcode-dev-loop description: > WHEN building, testing, or visually verifying an Xcode project from the command line — xcodebuild runs, Swift Testing result reading, simulator install/launch, and screenshots; NOT for authoring Swift source or tests; returns the canonical build/test/inspect loop.
Xcode Dev Loop
The command-line loop for an Xcode project: discover, build in the background, read the results correctly, launch on a simulator, then capture screens.
This loop runs and inspects an Xcode project. It does not author Swift source or tests.
Send that work to app:swift-testing, then come back here to run it.
1. Discover Before You Guess
- Find the container first. List the checkout for a
.xcworkspaceor a.xcodeproj. - List the schemes of a workspace with
xcodebuild -list -workspace <name>.xcworkspace. - List the targets, build configurations, and schemes of a project with
xcodebuild -list -project <name>.xcodeproj. Use this form when you need a target name. - Build and test with the same container flag you listed with, and always name the scheme:
xcodebuild test -workspace <name>.xcworkspace -scheme <Scheme>. Thetestaction fails without a scheme. - List simulator UDIDs with
xcrun simctl list devices available -j. Resolve the UDID once, then reuse it. - Never address a simulator by name. Duplicate names ("iPhone 17 Pro Max") cause "No booted simulator named …" failures. Only the listing output separates two devices that share a name, so give the listing command beside the UDID whenever you replace a name.
- When a scheme needs a runtime that the default Xcode does not have (for example a
watchOS beta), export
DEVELOPER_DIR=/Applications/Xcode-<version>.app/Contents/Developerfor the whole session. Everyxcodebuildandxcruncall must select the same Xcode, not only the first call.
2. Build and Test in the Background
-
Never let
xcodebuildhold the foreground. A clean build or a test run routinely exceeds the 600 s command timeout. A command killed at the timeout leaves no verdict. -
Start the run in the background. Redirect its output to a log file in the scratchpad. Keep a handle whose exit status you can read later.
-
Prefer the harness's background facility (
Bashwithrun_in_background: true) and the task handle it returns. -
When only a plain shell is available, make the run record its own exit status. A later shell cannot
waitfor another shell's child, so wait for that status file instead. Give every attempt its own log and status path; a status file left by an earlier attempt ends the wait at once and reports the wrong result:( xcodebuild ... > "$LOG" 2>&1; echo $? > "$LOG.status" ) & # start it until [ -f "$LOG.status" ]; do sleep 5; done # wait, in a later call -
Use
CODE_SIGNING_ALLOWED=NOfor simulator builds. -
Pin the destination as
platform=iOS Simulator,id=<udid>. -
When only one target matters, scope the test run with
-only-testing:<TestTarget>. -
Never wait with a chained foreground
sleep; the harness blocks it. -
Wait on the handle you kept with the harness's blocking wait (
Monitor, or the task-output wait), or wait for the.statusfile with the loop above. Read the exit status first. Read the log's terminal marker second. Do not wait by grep alone: the loop keeps polling whenxcodebuildexits before it writes a marker.
3. Read Results Correctly (Swift Testing Is Not XCTest)
- Swift Testing does NOT emit XCTest's
Test Case ... passedlines. Executed 0 tests, with 0 failuresis the empty XCTest summary. It proves nothing.- The real verdict is
✔ Test run with N tests in M suites passedplus** TEST SUCCEEDED **. Check that N is greater than zero. A pattern that also matches zero proves nothing. - Grep once with the full set of terminal markers:
\*\* BUILD SUCCEEDED \*\*,\*\* BUILD FAILED \*\*,\*\* TEST SUCCEEDED \*\*,\*\* TEST FAILED \*\*,Testing failed:, and^error:. Judge the marker together with the exit status. - To confirm which suites ran, match both spellings: XCTest prints
Test Suite '.*' started, and Swift Testing prints aSuite .* startedrecord. Match them case-sensitively as printed. - Always pass
-resultBundlePath, and give every attempt its own path.xcodebuildfails when the path already exists. - On failure, read
xcrun xcresulttool get test-results summary --path <bundle>. It gives the structured crash reason, such asTest crashed with signal abrt. The log may repeat it as an underlying error, but the bundle is the reliable source. Do not re-run blind. - Treat
The test runner hung before establishing connectionand diagnostic-collection timeouts as a suspected environmental fault, not a proven diagnosis. Shut down only the simulator you pinned:xcrun simctl shutdown <udid>. Then retry once with a new result-bundle path. Usexcrun simctl shutdown allonly when the user says the whole device set is disposable. - Pass
TEST_RUNNER_<NAME>=<value>on thexcodebuild testcommand. Xcode strips the prefix and gives the variable to the test runner process. A UI test target's app under test does not receive it; setXCUIApplication.launchEnvironmentfor that case. test-without-buildingreuses the product built earlier. It can report a success that excludes your latest source change, so rebuild withxcodebuild testbefore you trust a pass.
4. Install, Launch, and Drive
- Install the build you just made before you launch it. Never launch whatever is already on the device: it can come from another branch.
- Boot the pinned device before you install:
xcrun simctl bootstatus <udid> -bboots it when it is shut down and waits for the boot to finish.simctl installneeds a booted device. Do not callxcrun simctl bootfirst: it fails on a device that already runs. - Know the product path before you install. Pa