Apple Watchkit simulator issue: SPErrorInvalidBund

Question

When I open my existing Watchkit app (Xcode 6.2), it compiles correctly, the simulators are launched (iPhone+Watch), followed by the meaningful error:

Error Launching 'xxx Watchkit Extension' SPErrorInValidBundleNoGizmoBinaryMessage

I have this issue with all simulators (iPhone 5/5S/6/6+ - 38mm/42mm)

Any ideas what the issue can be?

It seems for some reason the application does not want to run on the simulator, even though it used to. The iPhone application included in the same project does run, as do other Watchkit sample applications.

Answer 1

I've tried everything posted thus far in this thread but still couldn't get it to work. I resorted to backtrack to the point when it was working and retrace every single action that I've done to figure out at which point it breaks...

As it turned out, the WatchKit App's info.plist file does not like any custom plist entry, at least that is what I've found out in my case. I've added an entry called "MyAppBundlePrefix" and it caused the "Error Launching 'xxx Watchkit Extension' SPErrorInValidBundleNoGizmoBinaryMessage"

I wish XCode would offer a little bit more specific detail for that error but it took me about 5 hours to find it out by brute force way.

Answer 2

I checked all bundle identifiers multiple times but couldn't get rid of the issue. Neither did cleaning the build folder work out.

However, I was able to sort it out by turning off Game Center at the Capabilities of my WatchKit Extension.

Turning it on for the iOS host app seems to work fine, but turning it on for the WatchKit Extension results in the SPErrorInvalidBundleNoGizmoBinaryMessage error when attempting to run the WatchKit App in the simulator, while it completes building without any complaints.

I'm developing a game for Apple Watch and was looking forward to support Game Center. It was actually my plan from the very beginning to communicate with the hosting iOS app to do so, but then I saw Game Center listed in the Capabilities of the WatchKit Extension itself, so I expected to be able to deal with it right there. However, as it doesn't seem to work, I'm going to stick to my original plan to support it through the hosting iOS app.

Xcode Version 6.2 (6C131e)

EDIT: Same issue with Xcode Version 6.3 (6D570)

Answer 3

Did you change the bundle ID of your app? If so you may need to manually update the WKAppBundleIdentifier in the WatchKit Extension and also the WKCompanionAppBundleIdentifier in the WatchKit App.