error: Unable to resolve build file: XCBCore.BuildFile

Question

error: Unable to resolve build file: XCBCore.BuildFile (missingTargetProductReference(\"3bf83096e50de72a94699e9afc1133ebe3512682230d04680075c283a974e273\")) (in targ         


        

Answer 1

In my case, it was a simple issue of a missing file.

Checked all secondary error messages. Error report said that my bridging-header.h file was not being found. Checked the path of the missing file from the target settings (just search for .h to get the right setting key). Fixed the new path and error went away.

The cause: I had reorganized my folders after a system crash and added a second level to my project location.

Answer 2

For XCode 10 Beta: Problem occurs when I have two workspaces open that share the same project directories. Solution was

Short version

1. Shut down all but one workspaces
2. exit XCode and reopen XCode
3. XCode > Product > Clean Build Folder

Longer version

1. Shut down all but one workspace
2. XCode > Preferences > Locations > Derived Data > goto directory ~/Library/Developer/Xcode/DerivedData
3. Clear out subdirectories from DerivedData
4. exit XCode and reopen XCode
5. XCode > Product > Clean Build Folder

Thanks to @aferriss answer for the clue.

Answer 3

Just Restarted my Xcode and the problem went away

Answer 4

I came across this same error while using openframeworks 0.10 with xcode 10 recently. It seems like it was caused by having multiple openframeworks projects opened at a time. If you close them all one by one, and then reopen the one you'd like to work on, it should resolve the error. Hoping this is just an xcode-beta thing.

Xcode used to tell you that there as a workspace integrity problem, and you could just ignore it. But it seems like it's returned. There's some discussion about this issue here.

Answer 5

In case this helps, I had a new repo and the Libraries weren't correctly linked.

I opened Xcode, cleaned, and went through, one by one, through Libraries on the menu. I clicked on it, which opened the info panel on the right, and pressed the small folder button, and found the path designated and clicked and opened, to make Xcode recognize those Libraries. Path names were often

/node_modules/react-native/Libraries/(something)/(something).xcodeproj

Answer 6

My solution was that I was using the wrong Xcode version for the project I was working with. It still required 10.1 and I was attempting to run in 10.2. I instead opened it in 10.1 and the error went away while successfully compiling.