With Xcode 27.1 (27A9275) and an iOS 27.0.1 (24A446) physical device, the UI-test runner starts, then fails about 60 seconds later with com.apple.dt.XCTest.XCTFuture, code 1000: “Timed out while enabling automation mode.” No business test method starts (0 methods started). What is the officially supported, targeted diagnostic entry point for this XCTest initialization boundary? Specifically: What supported configuration and logging level expose the runner sending an automation-mode RPC, device testmanagerd receiving it, testmanagerd sending a reply, and the runner receiving that reply? Which timestamps and session/request correlation fields associate those events across the runner and testmanagerd? Can collection be limited to one device, one test attempt, these processes, and a short time window? What minimal text fields are necessary? Can unrelated-app data, screenshots, audio/video, runner environment values, credentials, and personal information be excluded? Please specify any required setup and how to disable or remove it afterward. We need a supported entry point and a precise, minimal privacy scope before changing configuration or collecting broader diagnostics. A general CoreDevice or sysdiagnose workflow alone does not establish that these RPC send/receive events will be recorded.

Supported targeted diagnostics for XCTest automation-mode initialization timeout

With Xcode 27.1 (27A9275) and an iOS 27.0.1 (24A446) physical device, the UI-test runner starts, then fails about 60 seconds later with com.apple.dt.XCTest.XCTFuture, code 1000: “Timed out while enabling automation mode.” No business test method starts (0 methods started).

What is the officially supported, targeted diagnostic entry point for this XCTest initialization boundary? Specifically:

What supported configuration and logging level expose the runner sending an automation-mode RPC, device testmanagerd receiving it, testmanagerd sending a reply, and the runner receiving that reply?
Which timestamps and session/request correlation fields associate those events across the runner and testmanagerd?
Can collection be limited to one device, one test attempt, these processes, and a short time window? What minimal text fields are necessary?
Can unrelated-app data, screenshots, audio/video, runner environment values, credentials, and personal information be excluded? Please specify any required setup and how to disable or remove it afterward.

We need a supported entry point and a precise, minimal privacy scope before changing configuration or collecting broader diagnostics. A general CoreDevice or sysdiagnose workflow alone does not establish that these RPC send/receive events will be recorded.