0
votes

I'm submiting support for Apple Watch for my app. App on Watch simulator works fine but my app is rejected due to following reason:

We discovered one or more bugs in your app when reviewed on Apple Watch. Specifically, your app is failing to launch on the Apple Watch device.

This is weird since my app works fine with watch simulator. So my question is should watch binary be in embedded binaries in main iOS app?

Screenshot of my current settings

1

1 Answers

1
votes

No, in watchOS 2, the WatchKit extension should not be an embedded binary of the iOS app. It runs on the watch itself, not on the host device.

The extension is an embedded binary of the watchOS app. The iOS app embeds the watch app, and the watch app embeds its extension.

About the simulator:

Testing on the simulator doesn't guarantee that the app will also work on an actual device. You should also test on the real hardware device to catch issues which wouldn't be revealed by the simulator.

Simulator is designed to assist you in designing, rapidly prototyping, and testing your app, but it should never serve as your sole platform for testing. One reason is that not all apps are available in the simulator. For example, the Camera app is available only on hardware devices and cannot be replicated in the simulator.

In addition, not all bugs and performance problems can be caught through testing in Simulator alone.

Since your computer has a faster CPU and more memory than the actual watch, it's very possible for your app to perform better on the simulator, but perform poorly or fail on an actual device.