iOS Simulator vs. watchOS Simulator

Question

DrMickeyLauer OP

Created Apr ’17

Replies 3

Boosts 0

Participants 2

For some reason, I can't seem to run the watchOS and the iOS app in parallel in their respective simulators.

If I build the apps with the watchOS scheme, then the iOS simulator starts up, but the app does not. If I want to run the (watchOS-scheme-compiled) iOS-app manually, it closes immediately. The same (but vice versa) happens when I chose the iOS scheme. In that case the watchOS app hangs during startup in the watchOS simulator.

How are we supposed to debug WatchConnectivity in that case? Or are my targets just messed up and it should work usually?

Answered by DrMickeyLauer in 225640022

Ok, found it by now. I had missing some frameworks in the "Embedded binaries" section of my iOS app – this usually is only a problem when running on a device, but for some reason with watchOS they obviously change the way the respective iOS companion app gets started to facilitate installation of the watchOS extension. Anyways, it's good now.

Boost

Answer 1

KMT OP

Apr ’17

Which version Xcode?

0

Answer 2

DrMickeyLauer OP

Apr ’17

Moreover – and I suspect that this is related, thus I post it in this thread here – my watchOS app only correctly launches every other try. It's always reproducible that the main interface does not startup on the 1st try. I see that +load gets called, but for some reason the main interface does not come up. Killing the app and restarting it again does make it work, but – like I said – only every 2nd time.

0

Answer 3

DrMickeyLauer OP

Apr ’17

Accepted Answer

Ok, found it by now. I had missing some frameworks in the "Embedded binaries" section of my iOS app – this usually is only a problem when running on a device, but for some reason with watchOS they obviously change the way the respective iOS companion app gets started to facilitate installation of the watchOS extension. Anyways, it's good now.

0