Quick update. We've had substantial success applying the Audio-streaming concept to a "relay runner" app. The relay runner is installed and launched separately from the app-under-test, and acts as a relay station between the app-under-test and the external equipment. Initially we had some system-imposed limits to its run duration but that seems to be sorted out. The app-under-test connects to localhost, and the relay runner connects to the external IP address. It's been operating continuously for over a week now with good success.

Thanks for the reply Quinn. We've spent the time looking into the options you suggested. Am I right in assessing that each needs some level of code modification of the app under test? We're reluctant to add test hooks that would end up in released product, esp networking code, because this app is a medical device that already has FDA trial approval based on SBOM documentation showing no networking libraries (and thus a low cybersecurity risk rating), and no operating differences between tested and released .ipa files. Modifying the iPad's environment is kosher which is why the helper app was helpful.

Here's the bug identifying information. Mar 6, 2026 at 4:13 PM – FB22152886 iPadOS 26.3 breaks test automation ability to communicate on local network.

Xcode 26.2 + iPadOS 26.3.1 = broken Xcode 26.3 + iPados 26.2.1 = works Xcode 26.3 + iPadOS 26.3 = broken Xcode 26.3 + iPadOS 26.3.1 = broken

The combinations we've confirmed are: Xcode 16.x + iPadOS 18.x.x = works Xcode 26.2 + iPadOS 18.x.x = works. Xcode 26.2 + iPadOS 26.2.1 = works. Xcode 26.2 + iPadOS 26.3 = broken. Have we tried Xcode 26.3? No - honestly I was neck deep in troubleshooting when Xcode 26.3 came out last week. And we're a med device company so we typically don't rush to update tools because we need to maintain specific development environments. I know you're thinking "what could it hurt at this point?" lol. I'll test that today.