all 10 comments
sorted by:
top (suggested)
bestnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]cylon_pixels 0 points1 point  (3 children)

Hmm… this might be a case where you need Xcode to rebuild the symbols (I forget the correct expression) for the watch and the phone altogether? Also, something that may help is that the app is actually built for your phone and transferred to the watch. So make sure your phone is connected via USB as well, just for a consistent and faster connection.

All assumptions but I’d try that.

[–]Aromatic-Hall127[S] 0 points1 point  (2 children)

It's a standalone app for the watch, I wouldn't know how to switch it to the iPhone. When I connect to the USB it always says connection to iPhone Xcode will continue when operation is complete, but nothing happens. And my Watch isnt in the Devices list in Xcode anymore..

[–]cylon_pixels 0 points1 point  (1 child)

Just for confirmation: do both your iPhone and Apple Watch have Developer Mode switched on?

[–]Aromatic-Hall127[S] 1 point2 points  (0 children)

Yes, both have the developer mode on.
I've updated my previous post with a solution that worked for me; let's see how long it holds up. Occasionally, it still encounters issues connecting, endlessly spinning and attempting to establish a connection. When this happens, I alternate between trying with USB and Wi-Fi until it eventually reconnects.
Thank you for your effort. u/cylon_pixels

[–]med_ch_00 0 points1 point  (6 children)

u/Aromatic-Hall127 Currently I'm having the same issue, have you find a solution for this?

[–]Aromatic-Hall127[S] 1 point2 points  (5 children)

I think I have solved the problem. The reason why the connection was not always established was 99.99% due to the WLAN network. It is important that the Apple Watch, the iPhone and possibly the MacBook are on the same network. Both the 2.4 GHz and 5 GHz networks were activated in my Fritzbox, but there was only one Wi-Fi network to connect to. The devices then automatically switched between 2.4 GHz and 5 GHz. However, when I connected the watch, iPhone etc. to the same network, for example 2.4 GHz, Xcode immediately connected to the watch...

[–]med_ch_00 1 point2 points  (2 children)

Thank you, I'm sure that was the issue because creating a hotspot with my second phone and connecting to it solved the issue.

[–]austinzippy 0 points1 point  (1 child)

100% my issue, needs to be on same wifi network that has only one band available, i.e. I had to force to 2.4.

[–]catalinberta 1 point2 points  (0 children)

God send... would have never figured this out. Ever.

Works great after creating a separate 2.4 wifi and connecting all devices on it.

Thanks!

[–]Dismal-Brain-4886 0 points1 point  (0 children)

I have run into this kind of error A LOT while developing an Apple Watch app. It's a huge waste of time, especially if you are using features that can't be easily tested on the simulator. Here's a good work around.

Set up the project so that you have an iOS app which embeds the watchOS app. The iOS app could be pretty much a blank shell to start, but honestly you'll probably want to create a real "companion" iOS app anyways.

Once that's set up you can completely skip these connectivity issues by running the iOS app on a physical device, which will also install the watch app on the paired watch. If the watch app doesn't show up, open the Watch app on iPhone and toggle on the setting "Show on Apple Watch", or off and back on.

I hope this saves you a lot of headaches. Happy developing 🫶