Collectives™ on Stack Overflow

Find centralized, trusted content and collaborate around the technologies you use most.

Teams

Q&A for work

Connect and share knowledge within a single location that is structured and easy to search.

I'm trying to develop an extension of my app for the Apple Watch.

Instead of install the app on the watch, I have this error:

AppName Failed to install AppName, error: Invalid Bundle - No Apple Watch Binary

In my info.plist files...

For the extension, I have:

<key>CFBundleIdentifier</key>
    <string>com.mycompany.AppName.watchkitextension</string>
<key>WKAppBundleIdentifier</key>
    <string>com.mycompany.AppName.watchkitapp</string>
For the WatchKit app, I have:
<key>CFBundleIdentifier</key
    <string>com.mycompany.AppName.watchkitapp</string>
<key>WKCompanionAppBundleIdentifier</key>
    <string>com.mycompany.AppName</string>
And for my app, I have: 
<key>CFBundleIdentifier</key>
    <string>com.mycompany.AppName</string>
Did I miss something?
                This solution only worked on 1 project for me. The other app continues to have the same error
– hitme
                Jun 7, 2015 at 18:06
For me the problem was fixed by adding the watch app to my iOS target's Embed Watch Content section. 
I'm using Xcode 7 and watchOS 2.0. It was building fine on the device, but the simulator was giving me this error.
Steps:
Find your iOS target
Click Build Phases
Ensure your watch app (.app) is included in "Target Dependencies" and "Embed Watch Content"
                It's a possible explanation. Indeed, I work on 2 projects with the same settings. One for test the watchkit frameworks, and the other project is the real project. I didn't check the executable file. I will try this as soon as possible. Thank you
– ejanowski
                May 1, 2015 at 12:58
                Where do you find your explicit "Executable File" name? I can't seem to have any luck with this solution
– JLoewy
                May 2, 2015 at 8:19
                Try adding it using the + in the watchkit's plist. It should come up in autocomplete as you're typing (case sensitive: "Executable file").
– Sohail
                May 2, 2015 at 18:58
                An addendum: I continued to have issues with installation despite getting past this error. My watchkit app was stuck on "Installing..." forever within the iPhone watch app. I ended up fixing these issues by going through my product names/bundle names and ensuring that none of them were the same.
– Sohail
                May 2, 2015 at 19:00
In my case, I got it when building app for WatchOS2. I fixed by setting the schemes like this:
The Watch Extension Scheme builds
    3 Target: iPhone (2 dependencies) + Extension (no dependencies) + Watch App
Running Extension Scheme on iPhone simulator -> works!
In my case it was an Info.plist configuration error. The Bundle identifier was different to the NSExtension -> NSExtensionAttributes -> WKAppBundleIdentifier. 
Setting the same value fixed the error.
Resets of watch/xcode/iphone doesn't help sometimes, as it described in other answer.
One more case to solve this:
This error appears, when I change iPhone language of my iPhone to not English (in my case - Russian) language.
When I set back English - everything start works as usual!
The bundle id of iOS app is prefix of watch app & extension' bundle id.
Value of WKCompanionAppBundleIdentifier in Info.plist of your watch app matches bundle id of your iOS app.
iOS app, watch app & extension should signed by the same cert.
There must be a build phase in iOS app target:
Destination: Products Directory
Subpath: $(CONTENTS_FOLDER_PATH)/Watch
Click +, add your watch app target.
        
Thanks for contributing an answer to Stack Overflow!
Please be sure to answer the question. Provide details and share your research!
But avoid …
Asking for help, clarification, or responding to other answers.
Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.