XCUITest text entry drops characte… | Apple Developer Forums

XCUITest text entry drops characters on physical iOS 27 devices since Xcode 27 GA (FB24932647)

Since Xcode 27 GA, text entry from a UI test on a physical iOS 27 device delivers only the first 3–4 characters and then stops, while the call still returns success. Taps and scrolls are fine. The same tests pass on Xcode 27 beta 1. Filed as FB24932647.

Broken: Xcode 27.0 (27A266a), 27.1 beta (27A9269), 27.2 beta 2 (27B5028f) Works: Xcode 27 beta 1 (27A5194q) Device: iPhone, iOS 27.0 (24A437)

Repro. We drive it through WebDriverAgent. The failing step is XCTest's own event synthesis in testmanagerd, which is the same path XCUIElement.typeText goes through.

Xcode 27.2 beta 2, run sudo xcodebuild -runFirstLaunch, reboot the device.
Type subjectline into a plain UITextField.
Read the field's value back.

Expected subjectline. Actual sub or subj, in every one of 16 attempts. In a recipient-style field the fragment appears and is then erased, so nothing survives. 0 of 32 attempts completed.

Device log, all within one second:

testmanagerd   Failed to load displays from CADisplay
testmanagerd   Failed to resolve displays. Defaulting to generic keyboard sender.
testmanagerd   Recap event action playback initiated
UIKitCore      hardwareKeyboardAttached = YES
UIKitCore      Moving from placement OnScreen to OffScreenDown
UIKitCore      Change to input view set: (empty)
testmanagerd   Recap event action playback completed

testmanagerd can't resolve a display, so it falls back to a generic keyboard sender that registers a virtual HID keyboard. iOS then treats that as a hardware keyboard and dismisses the software keyboard while the text is still being typed.

What changed. Comparing testmanagerd in the two DeveloperDiskImages: beta 1 derived the display from the app's identity (Computed display ID … from embeddedApplicationIdentifier … bundleID). GA removed that and added CADisplay enumeration with the generic fallback. That code is unchanged through 27.2 beta 2.

This is not 181945323, which is marked fixed in 27.2 beta 2. That one needs Device Hub and clears on its own.

Is anyone else seeing this on device?
Is there a supported way to type on device under Xcode 27 GA, other than staying on beta 1?