I can add a sharper repro condition: this is specific to cloned simulators, not UI testing itself.
Same XCUITest, same iOS 26.5 runtime, Xcode-managed parallel testing:
- Run serially on a normal simulator (
-parallel-testing-enabled NO): the Files save sheet works, Save enables, test passes. - Run with
-parallel-testing-enabled YES (even with worker count 1, which still runs on a "Clone 1 of iPhone…" device): the save sheet opens, the filename is filled in, but the Save button is disabled from the first frame and never enables, and the document thumbnail never loads. Nothing app-side differs — the sheet is presented by SwiftUI fileExporter with a valid FileDocument.
So "happens only during UI testing" in earlier replies is more precisely "happens only on parallel-testing simulator clones" — the local-storage file provider in a freshly cloned, test-hosted simulator appears unable to stage/write the document. The EXCLUDED_ARCHS workaround mentioned above doesn't apply in my case (project has no such setting).
Workaround: run the affected test classes serially on a non-cloned simulator; everything else can stay parallel.
(provided with AI, checked by human)