Troubleshooting

Devicewing cannot find a simulator

Install Xcode 27.1 with the iOS 27.1 runtime (for the iPhone Duo) and the iOS 27.0 runtime (for the others). Devicewing uses the simulator you pick, else one of that device that is already running, else it makes one named “Devicewing” and the device name.

The app in front closed when Devicewing connected

Expected the first time Devicewing connects after a simulator starts. It restarts the simulator’s display server so the iPhone Duo’s cover screen accepts touches and the hardware buttons work. It does not happen again until the simulator restarts. Not now on the notice puts it off.

A Board device shows a warning triangle

With Sync on, it could not find a control with the same label as the one you touched, so it touched the same place instead. See Sync and the lead device.

An agent cannot find something on screen

The accessibility tree leaves some things out, such as rows of the Settings sidebar, Safari’s page content and SpringBoard alerts over an app. In apps, describe also checks a 30-point grid over areas no element claims, which takes a second or two. describe --quick skips that.

Typed text comes out wrong

type sends key presses through iOS’s hardware keyboard layout. When that layout is not US, or the text has a character no US key types, Devicewing pastes the text instead. Use --paste to always paste.

A push notification does not arrive

The app must have asked for notification permission and been allowed. Tap Allow on the prompt, for example with devicewing tap-element Allow.

Camera Control does nothing

No iPhone simulator has Camera Control, so it cannot be pressed.

Something stopped working after an Xcode update

Devicewing uses parts of Xcode’s simulator that Apple does not document, and they can change with Xcode releases. Email [email protected] with your Devicewing, macOS and Xcode versions.