“iPhone 16 pro”

Developing on the watch is stupid fragile. Seriously. XCode needs to set up a secure tunnel to the watch using wifi but the watch regularly turns off or looses its wifi. There is so much magic here that like I said, embarassing to the watch team at apple. Here are options that work for me: The watch will often disconnect from the router even though it is on. My first solution is to go into Settings -> WiFi and make sure it is connected to the router. This works about 70% of the time. If it doesnt, you can try toggling developer mode on the watch to get to the Trust Computer which sometimes works. Turn on your hotspot on your phone, then connect your mac and your watch to it and hope this works. You have about a 50% chance here. If your home network is a mesh network, then make sure that the APs have handed off so that all the devices are on the same AP. I can not prove this other than through observation. So yes, turn on and off the wifi on all the devices. Supposedly, you can actually turn on you

Well here we are and I have encountered the same Issue. Disconnected the watch from Xcode, rebooted Xcode, rebooted the phone, the watch and everything else connected to the Mac. For some odd reason the watch re-paired to Xcode and initially there was a message on the Devices and Simulators saying that there was something wrong with the Tunnel (I've probably got that wrong but it was not happy) but then inexplicably the message Copying blah blah blah appeared in the Xcode devices window so now I am just waiting for that to finish. I'm now about an hour into this palaver and hopeful that I can finally update my App.

I have the same issue. I reinstalled the Application, checked all Targets , Unadded and added my Dev Profil, turned Devmode on and off on my iPhone, deleted Derivated Files . cleaned the Project and tried it with Wifi Off+Cellular. I personally thing its due to a malfunction of a server. The appllications all work on the Simulator

Same here on Vision Pro. Reinstalled everything on a clean headset with same results: “This app can't run and must be verified.” Lost 4 hours!!

I'm having the same problem. It worked on my test iPhone until 7 PM UTC, but now it only works on the emulator.

I have the same problem, I can install my app in my physical Iphone. I'm getting the message an Internet conection is requiered, but I have Internet conecction.

oh nooooo I just spent the past few hours troubleshooting this from so many angles... even wiped my phone + MacBook 😑 still not luck as of 2:18pm PT btw.

Tried so many things. Frustrating, because I thought it was a local issue. After trying on different iPhones, different accounts, I started doubting it is an Apple issue. Then I found this topic.

would’ve been great to know before i went digging in derived dependencies, revoked half my certificates and devices, went digging through my phone’s dev mode configurations… 😅😅😅

Same issue here, cannot launch my build on my phone, stuck in a verify loop.

Same issue here since this evening (March 10, 2026) on both iPhone and iPad, paid Apple Developer Program account. After extensive troubleshooting — new certificates, new provisioning profiles, device restarts, testing on both Wi-Fi and cellular — I can confirm this is server-side. https://ppq.apple.com is returning 502 Bad Gateway intermittently. It sometimes responds with OK, which makes the issue harder to diagnose as it appears to be working when checked manually. Awaiting a fix from Apple.

Same error, for ~2hrs now. But curl returns successful, confusingly. curl -v https://ppq.apple.com Host ppq.apple.com:443 was resolved. IPv6: (none) IPv4: 17.33.192.136, 17.33.193.105, 17.33.194.109 Trying 17.33.192.136:443... Connected to ppq.apple.com (17.33.192.136) port 443 ALPN: curl offers h2,http/1.1 (304) (OUT), TLS handshake, Client hello (1): CAfile: /Library/Frameworks/Python.framework/Versions/3.13/lib/python3.13/site-packages/certifi/cacert.pem CApath: none (304) (IN), TLS handshake, Server hello (2): (304) (IN), TLS handshake, Unknown (8): (304) (IN), TLS handshake, Certificate (11): (304) (IN), TLS handshake, CERT verify (15): (304) (IN), TLS handshake, Finished (20): (304) (OUT), TLS handshake, Finished (20): SSL connection using TLSv1.3 / AEAD-AES256-GCM-SHA384 / [blank] / UNDEF ALPN: server accepted h2 Server certificate: subject: CN=ppq.apple.com; O=Apple Inc.; ST=California; C=US start date: Jan 21 17:47:41 2026 GMT expire date: Feb 17 18:28:16 2027 GMT subjectAltName: host ppq.ap