RobotyThe iPad could edit locally, but the chooser hid that option
A first development installation offered Connect a Mac while omitting Keep editing here. The repair made the visible choices match the workflow the device could already support.
Covers October 16, 2026. Reconstructed later from available records.
The message said the iPad could edit, save and review a task locally. The chooser beneath it offered one action: Connect a Mac.
The missing action was Keep editing here. It existed in code, but its cancel role caused it to disappear from the iPad confirmation popover. Earlier fixture checks had not exposed the contradiction between the explanation and the available choice.
A useful path behind the wrong presentation
Our October 16 check began with Roboty's development app absent from a ninth-generation iPad. We installed it without resetting an existing user's container. This was a clean development installation, not an App Store or TestFlight acquisition test.
The assisted walkthrough reached the basics lessons and returned from a full guide without losing the selected lesson. Choosing simulation then exposed a real limitation: this iPad could not execute it locally. Editing and review were still available, but the chooser made a Mac connection look like the only next step.
We replaced the popover with a native sheet containing an explicit local-editing button. In the repaired installed build, both choices appeared and Keep editing here returned to the same draft.
A fresh installation exposes different assumptions
The entry used iPhone-specific companion wording, so it became device-neutral. A migration prompt also appeared without an original unpaired draft to recover. That action now requires the original source file. A recovery option should have something to recover.
We installed the repaired build over the first one. Relaunch retained the first-use decision and opened Workspace directly, without the unnecessary migration prompt. A name entered on the iPad stayed visible above the keyboard. Done dismissed it, and returning through Experiments and Back to goal preserved the edited name.
That checked retained draft state, not a newly saved revision, pairing or robot operation. It did not establish every layout, full VoiceOver behavior or on-device simulation.
The repair did not require adding a new editing capability. It required making a supported local path appear as an actual choice. Code and explanatory text had described that possibility already. The installed screen had to offer it too.