Follow-up: could Apple clarify the supported testing boundary before we change our test methodology? In https://developer.apple.com/forums/thread/840302, the author reports receiving an October 24 Apple Feedback response saying "SFSpeechRecognizer is not supported on Simulator." I understand that SFSpeechRecognizer is a different API from our reproducer. Our test instead calls XCUISiriService.activate(voiceRecognitionText:) with an already recognized text string. That string reached the testing activation path, after which SpringBoard logged: "No network. Not starting the request for SASRequestSourceTesting" Could Apple please clarify: Is this public, text-driven XCUISiriService path supported for ordinary classic Siri requests on a native Apple silicon iOS 26.5 Simulator with Xcode 26.6? Our original environment and evidence are described above. If it is supported, which documented prerequisite or public diagnostic distinguishes the cause of this specific request-start network refusal? The later, separate URLSession HTTPS success does not establish Siri endpoint reachability or the original failure's cause. If it is unsupported or limited, what Apple-supported physical-device workflow and public automation APIs should we use for end-to-end Siri testing, and which parts can reliably remain Simulator tests? Apple's CarPlay Simulator documentation separately excludes Siri testing: https://developer.apple.com/documentation/carplay/using-the-carplay-simulator We are keeping that CarPlay limitation distinct from support for the standalone XCUISiriService text call. This distinction materially affects our testing methodology. We would appreciate an explicit support statement for the text-driven path rather than assuming that the SFSpeechRecognizer limitation also applies. No additional Siri activation has been performed.