Built-in binary validation error

Question

Since yesterday, Xcode has been doing stupid things while trying to run my WatchKit app on my iPhone. This gives me an error:

Built-in binary check error.

Error: warning: is there a directory

This is not very useful, and it seems he is complaining about the profile profiling of my Watchkit target. I think I configured it correctly by following this answer .

This is how I set up my profiles. Three application identifiers and six profiles (three for development and three for distribution).

Main application:

WatchKit Extension:

WatchKit Watch App:

Answer 1

I had my own structure, connected and integrated into the WatchKit extension and application. Removing the frame from General> Embedded Binaries from WatchKit Extension fixed this for me. I had to delete my Build folder and restart Xcode.

Answer 2

I was able to solve the problem by properly setting up the Provisioning Profiles.

With Xcode 6.2 I was able to complete development / debugging builds with auto-dialing and no additional PPs for development on the portal, but using the preparation team.
Now with Xcode 6.3 I had to add 3 explicit PPs for development on the portal and assign them in the project settings.

Answer 3

I am also struggling with this error. For me, sometimes he builds, sometimes it is not. Here's how I can currently archive the WatchKit app. I do not claim any knowledge about why this works, only that it works for me.

• Clean Shift-Command-K
• Quit Xcode
• Delete files in ~ Library / Developer / Xcode / Derived data
• Reopen Xcode and Archive

Answer 4

UPDATE: I had this problem in another project and managed to solve it by removing spaces in my target app names and WatchKit app extensions. Therefore, before my target names were APPNAME WatchKit App and APPNAME WatchKit Extension , changed them to APPNAMEWatchKitApp and APPNAMEWatchKitExtension fixed!

ORIGINAL: Just to add my two cents, I struggled with this problem for several weeks. I narrowed it down to including CocoaPods in the project, but without a more descriptive error, I have no idea why.

I know that my provisioning profiles are correct because an empty project (including the WatchKit landing page) successfully archives them. There are no static libraries in my WatchKit extension, lest there be a problem.

As a result, the only thing that works reliably is to use xcodebuild + xcrun in the terminal to build and archive my project. This article explains xcode well in the terminal.

Answer 5

For me, the only way to fix this was to remove all spaces from the schema name and view the application name.

To change the schema name: (for example, the "amazingapp RC" schema)

1) Click on the circuit in xCode (where you select the device / simulator)
2) From the list, select: "edit schema"
3) When a new modal open click "duplicate scheme" in the lower left corner.
4) Choose your own name without spaces and save.
5) Now click on the control circuit and select the old one.
6) Remove it by clicking the "-" button

Now it's time for the extension name:

1) Click on the circuit in xCode (where you select the device / simulator)
2) Select an expansion scheme
3) Click "edit schema"
4) Select "Archive" (release) at the bottom of the left section

5) Enter the username without spaces in the "Archive name" field
6) Close.

Now build-> clean, build-> archive, and you should be good to go.

Answer 6

I followed @dogsgod's suggestions, revoked all my certificates, etc., more than 6 profiles, no luck. After this, for almost 6 hours, another team member checked this and it worked (allowing xcode to fix problems for them). Make sure that groups are enabled for all application identifiers (I use groups to exchange data between the clock and the main application)

So, I thought this was just my xcode.

Then I went to git, cloned it, and then compiled it just fine.

Perhaps everything in my gitignore got rid of the fact that the files blocked me. Or perhaps because I pulled it out after they committed it. It's almost just voodoo at this point, but it worked

Answer 7

In my case, these were my Xcode settings.

I had the settings DerivedData -> Advanced Settings (Build Location) on "Custom" = "Regarding Workspace".

I changed it to Unique and it made it work.

Hope this helps someone.

Answer 8

EDIT : In a day, I can share another thought. Although git cloning works, the problem occurs after some changes are made. This makes me wonder if the problem is due to poor file formatting (like non-unix-like EOF or the like) or just an error in Xcode. In any case, my workflow currently looks like this:

 1) git clone to another directory 2) archive 3) if there is an error, I need to fix it, 4) git commit & git push 5) repeat steps 1 & 2 ... 

Which is annoying, but this is the only way I can archive my project and upload it to the App Store ...

ORIGNAL POST: I also encountered this error. My project uses CocoaPods, several goals and build schemes, and group rights. Sometimes I can’t build, although this is a fix (see below), but the archiving problem persists for a longer time. After two days of fighting it, my resume looks like this:

I followed all the answers and I see that sometimes I do:

1) clean project

2) (optional - not required) restart Xcode

3) delete the contents of the data folders.

allows me to compile and run the application. But I still can’t archive. Sometimes it seems that I have to do it twice.

In addition to the above, I tried (and could not archive) the following sentences:

• rename the target names (and containing folders) to NOT include spaces, Extension and WatchApp goals do not have spaces in their names, but the project will not be archived (without changes)
• I checked that there are no embedded binaries in Extension Target (watchApp does not have this option)
• I tried to change the deployment target (the default was iOS 8.3 for Xcode 6.4) for both 8.2 and 8.4 without any luck in archiving.
• I updated the AppID and all training profiles for both "adHoc" and "release schemes" were also out of luck.
• and I checked that there are no spaces in the current scheme that I am trying to archive, but it still does not change anything.
• I even tried the last sentence, that is, changed the default location of the Derived Data folder, but, as I suspected, it did not change anything.

Interestingly, in fact, HAVE WORKED is Mike Manh's suggestion: check the repo on another folder .

After cloning the repo into a new empty folder, everything suddenly worked. This leads me to conclude that there may be some remaining files / broken links / something else in my current project folder. I guess this could happen when I tried to reinstall the watchKit development branch into the current main branch. Which began to silence me with crazy conflicts, and I finally interrupted the permutation. Perhaps this was the moment when the archive option ceased to function normally.

Answer 9

I had the same problem. In Xcode 6. * I fixed it by clearing the DerivedData folder. But in the new Xcode 7, this did not help. So I removed the spaces in WatchKit Extension and WatchKit App ("planckMailiOS WatchKit App" → "planckMailiOSWatchKitApp" and "planckMailiOS WatchKit Extension" → "planckMailiOSWatchKitExtension").