error: Unable to resolve build file: XCBCore.BuildFile

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?

For me it was the Build System. This answer fixed it for me. https://stackoverflow.com/questions/52401856/problems-after-upgrading-to-xcode-10-build-input-file-cannot-be-found — Marty, Apr 19 '19 at 00:47

Warren Stringer · Answer 1 · 2018-07-07T05:11:51.997

82

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

Short version

Shut down all but one workspaces
exit XCode and reopen XCode
XCode > Product > Clean Build Folder

Longer version

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

Thanks to @aferriss answer for the clue.

edited Jul 07 '18 at 05:11

answered Jul 06 '18 at 21:28

Warren Stringer

1,692
1
17
14

1

It seems this can also happen if a workspace shuts down uncleanly - short solution worked for me. – Rob Hogan Oct 08 '18 at 13:39

score 20 · Answer 2 · answered Jun 28 '18 at 03:58

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.

I tried various other approaches in the answers to this question, but removing the framework made that specific error go away (I haven't re-added it, yet) — clearlight, Jun 02 '19 at 13:11

score 15 · Answer 3 · answered Apr 24 '19 at 03:39

15

For me, XCode > Product > Clean Build Folder and restart Xcode then worked.

answered Apr 24 '19 at 03:39

wkm

347
3
6

3

Xcode 10.2.1, tried it today (6/2/19). Didn't resolve it. – clearlight Jun 02 '19 at 13:03
Xcode 13.3 issue fixed after this solutions. After reboot, the message told me which file is linked and not found, just had to delete ref – David Ansermot Mar 29 '22 at 13:24

score 12 · Accepted Answer · edited Jul 22 '19 at 23:58

12

This was the culprit for my experience of the same error: missing Command Line Tools setting

After setting the correct version of Command Line Tools (i.e., Xcode 10.2.1; see below) on my system, the error went away!

correct Command Line Tools setting

edited Jul 22 '19 at 23:58

zmag

7,825
12
32
42

answered Jul 22 '19 at 23:36

98chimp

168
1
4

score 9 · Answer 5 · answered Dec 05 '18 at 08:36

9

Just Restarted my Xcode and the problem went away

answered Dec 05 '18 at 08:36

Shubham Goel

1,962
17
25

score 7 · Answer 6 · answered May 16 '19 at 16:06

7

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.

answered May 16 '19 at 16:06

emp

3,350
1
22
19

5

+1 Removing and re-adding `*.framework` from `Linked Frameworks and Libraries` section resolved my issue as well – coletrain May 29 '19 at 15:58

score 4 · Answer 7 · answered Apr 26 '19 at 08:38

4

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

answered Apr 26 '19 at 08:38

Heestand XYZ

1,993
3
19
40

score 3 · Answer 8 · answered Sep 16 '19 at 09:21

If you have a File Group which is backed by a physical folder and that physical folder has been deleted then you will get the same error "Unable to resolve build file: XCBCore.BuildFile". In my case the physical folder has been removed (because I removed all "real" files from it) and in XCode group there was still one external project linked.

Solution: - created a new group (without a folder) in XCode - Moved external project reference there. - rebuilt the project

Error gone.

I don't know which folder disappeared and the message is not saying so: any idea how to resolve? — WestCoastProjects, May 27 '20 at 17:38

score 2 · Answer 9 · answered Jan 16 '19 at 20:34

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

score 2 · Answer 10 · answered Mar 23 '19 at 05:14

2

In my case, after trying all solutions in this question and some more (including updating Xcode 10.2 beta and even macOS), the only thing that worked was accessing the project bundle (right click > Show Package Contents) and remove everything except project.pbxproj:

project.xcworkspace
xcshareddata
xcuserdata

answered Mar 23 '19 at 05:14

djromero

19,551
4
71
68

Ironically I was getting some other weird error and doing what you said fixed that, but not the error I was getting. But it is slightly different than the questioner's error message. XCBCore.BuildFile (namedReferencesCannotBeResolved) – clearlight Jun 02 '19 at 13:07

score 1 · Answer 11 · answered Apr 03 '19 at 09:56

For me there was a different solution after none of the above worked. The problem started after using unlink for one of my packages. Then for some reason, the Package was still there under Libraries, but it was greyed. After deleting the greyed Library, everything started working again.

score 1 · Answer 12 · answered May 03 '19 at 19:01

1

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.

answered May 03 '19 at 19:01

Aaron

6,466
7
37
75

You saved my sanity, brother! This was driving me bugnuts for days until I saw your post, and solved it by changing my project's "Project Format" version to match the Xcode version. I posted an answer to someone else's question about this, and gave you a shout-out. https://stackoverflow.com/questions/63640191/unable-to-resolve-build-file-reference-to-missing-target-with-guid/65573196#65573196 – Bob Murphy Jan 05 '21 at 04:21

score 1 · Answer 13 · answered Aug 21 '19 at 22:58

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.

Jaeyo Keh · Answer 14 · 2018-11-05T02:31:50.517

0

I have the same problem. Because a folder not upload to Git server, git not allow upload empty folder, then I create a folder in project folder, and it work well. missing folder

edited Nov 05 '18 at 02:31

answered Nov 05 '18 at 02:26

Jaeyo Keh

1
3

score 0 · Answer 15 · answered Apr 26 '19 at 20:12

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.

score 0 · Answer 16 · answered Sep 18 '19 at 15:32

0

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

answered Sep 18 '19 at 15:32

Yulia

1,087
9
16

score 0 · Answer 17 · answered Oct 17 '19 at 20:47

0

Seems like there are a number of reasons for which one runs into the same error. For my case, it was not having the Submodule checked out locally. After I made sure all my Submodules were downloaded, the error went away.

answered Oct 17 '19 at 20:47

Vinod Madigeri

167
10

score 0 · Answer 18 · answered Feb 07 '20 at 22:53

I had correct Command Line Tools and cleaning did nothing for me.

While resolving a merge conflict, A Group named "Recovered References" had appeared in my project navigator. Probably due to a mistake I made during merging. The Group was empty and deleting it fixed my problem.

score 0 · Answer 19 · answered Apr 19 '23 at 07:02

0

Find UUID that is causing this error:

% grep -R "90ea71"
Delete a file, that contains the UUID:

% rm ./YourApp.xcworkspace/xcuserdata/yourusername.xcuserdatad/UserInterfaceState.xcuserstate

answered Apr 19 '23 at 07:02

Denis Kutlubaev

15,320
6
84
70

score 0 · Answer 20 · answered Apr 20 '23 at 18:18

For me, this error occurred while also accompanied by Xcode 10 Error: Multiple commands produce errors during the troubleshooting process.

In my case, I had a main project that had a reference to BFramework.xcodeproj which built a B.framework included in my main app bundle. BFramework.xcodeproj, in turn, had a reference to (and relied on) ANTLR4Framework.xcodeproj. The main app also had a reference to (and relied on) ANTLR4Framework.xcodeproj, to build the ANTLR4.framework and include it in the app bundle alongside of B.framework.

BFramework.xcodeproj had a relative path style reference to ANTLR4Framework.xcodeproj (which is the kind you probably want). The problem arose because my main app project had an absolute path style reference to the ANTLR4Framework.xcodeproj project. This means everything built and worked fine for the original project because they were both referencing the same ANTLR4Framework.xcodeproj project on the file system. When I duplicated the project in the Finder and opened it in Xcode, I began getting error messages like in Xcode 10 Error: Multiple commands produce. That was because BFramework.xcodeproj was referencing the newly duplicated ANTLR4Framework.xcodeproj while the main project was referencing the previous absolute path to the original ANTLR4Framework.xcodeproj. When I renamed the original project folder, that caused the absolute path reference to be broken, which resulted in the Unable to resolve build file: XCBCore.BuildFile (missingTargetProductReference... messages.

For me, removing the absolute path reference to the ANTLR4Framework.xcodeproj project from the main project and then adding it back as a relative reference solved the problem.

error: Unable to resolve build file: XCBCore.BuildFile

20 Answers20

Linked