error: Unable to resolve build file: XCBCore.Build

Question

error: Unable to resolve build file: XCBCore.BuildFile (missingTargetProductReference("3bf83096e50de72a94699e9afc1133ebe3512682230d04680075c283a974e273")) (in target 'MyTarget')

Xcode 10 is giving this error immediately when trying to build our project. It's not immediately clear what is causing it.

How can I resolve it?

Answer 1

The key here is missingTargetProductReference, or you might get namedReferencesCannotBeResolved. Xcode can't find something.

This happened after upgrading to Swift5/Xcode10.

I found that removing linked frameworks and then re-adding them fixed the issue.

Answer 2

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 3

I had an embedded Xcode project that was not found (light blue). Deleting it and dropping it in again solved the issue.

Answer 4

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 5

I've faced the problem in Xcode 10.1.2. Xcode restarting and the clean project solve it in my case.

Answer 6

The problem is that on new xcode 10.2 there is a new BUILD Configuration, you need to change to LEGACY.

You can check how to change it here: https://medium.com/xcblog/five-things-you-must-know-about-xcode-10-new-build-system-41676cd5fd6c . CHECK THE GIF

So if you have a newer version of xcode different than the one used when the project was working probably this is what is causing the issue.