Clock Face running on simulator not on watch

[BlackCat7]

I am developing a clock face that runs fine n the simulator and sideloads just fine. I then get a terminating unresponsive app message with information on why. I am now going through each of my backups trying to figure out what is causing this, but is there any way to know why without having to backtrack and redo everything until I pinpoint the issue?

[Gondwana]

This is a bit of a long-shot, but...

The simulator runs at the speed of the computer that's executing it. I've found that it can be about 100 times faster than the watch for some tasks. A clockface needs to start up within a few seconds (5?) or it will be terminated on the watch for being unresponsive. This slowness may not be apparent on the simulator because it can be so much faster. Ergo, go through your code looking for anything that could be time-consuming.

A related issue is that you could have written your code to block until it received sensor data, a message, etc. Those events can take a while, again leading to your clockface seeming unresponsive. Refactor if so.