Why is it such a pain to test apps on the Apple Watch?

I can like NEVER test on my device because loading takes forever, does nothing, or just closes itself.


When I first started (about a month ago), I waited for over 5 minutes watching the spinner on the watch app and eventually gave up and worked on the app more. Also note it's such a simple app. Nothing complicated. I relauch, loads forever, does nothing. No image, just about 4 buttons.


Restart Xcode, Apple Watch, phone, doesn't matter. This is the reason I quit watch development in the first place. Then about a week later I launched the app and it worked in less than a minute. But now I'm back to watchOS development and it's loading forever. I sometimes by accident start typing so the watch display turns off, and then when I look at it, it cancels the entire load and does nothing. Sometimes when I launch it, my watch does nothing. It installs the app on the watch but it never even opens it, yet Xcode says it's running. What is going on??


I just tested it again and waited for over 6 minutes on the loading spinner before the app closed itself. Clicked the app again; loaded and closed itself. No errors on the console. Nothing.


Why is it such a pain to test on a real device?? Is there an alternative?


It works fine on the simulator by the way. Loads in like less than 30 seconds.


I'm using Xcode 8.3.2 on an iPhone 7 Plus iOS 10.3.1, Apple Watch 42 mm Series 2 watchOS 3.2

Apps immediately closing on the device, but running fine on the simulator can be due to embedded binaries missing the non-system-frameworks you link to.

Why is it such a pain to test apps on the Apple Watch?
 
 
Q