Thank you for the suggestion. I will download Xcode 27 beta and see what happens. I want to add that, after eight months of not being able to connect, Xcode 26.4 started to connect with my Watch in April '26. I still receive the error, but the communication is established after a few minutes. Current versions of software involved: Xcode 26.4 running from an M4 Mac mini running macOS Tahoe 26.2.1. Watch Series 10 (running watchOS 26.4) paired to an iPhone 16 Pro running iOS 26.5.

Thank you for your reply! This was first reported in August 4, 2025 (FB19367415). No resolution has been found.

However, I did not find any code related to that particular session :-(

WWDC24's sample code is located at https://developer.apple.com/sample-code/wwdc/2024/

The same behavior has been present in my Mac mini M2 since at least November 8, 2023 (was running Xcode 15.0.1). It persists after updating to macOS Sonoma 14.2.1 and Xcode 15.1. The behavior comes up when I start running Xcode (immediately reports "non-responsive"). When I finally manage to go beyond macOS's request to eject the disk image manually because it can't be ejected, Xcode and its Simulator work fine. It would be good to find out what is going on!

Hello! You can find the target in the same way you found it from the iOS app. Press the "+" to add a target, choose "iOS", and then scroll down until you find the "Application" area (below the "Application Extension" and "Test" areas; see below). Just make sure you name the same way as your initial watchOS app. I did not see any difference in the end result when I compared it with an "iOS app with Watch App" project. Good luck with your development!