Xcode 8.0 Command /Applications/Xcode-beta.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/swiftc failed with exit code 1

Question

When I compile my code on Xcode Version 8.0 beta 4 (8S188o) I get this single error bringing the compilation to failure:

Command /Applications/Xcode-beta.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/swiftc failed with exit code 1

I tried to clean the project and wipe the derived folder but that did not change things. What is it and how may I know more about it?

When I try to compile on the terminal the error being reported is:

Invalid bitcast\n %.asUnsubstituted = bitcast %swift.error* %13 to i2, !dbg !438\nLLVM ERROR: Broken function found, compilation aborted!\n

see this ocne http://stackoverflow.com/questions/26156561/xcode-6-0-1-command-applications-xcode-app-contents-developer-toolchains-xcoded — Anbu.Karthik, Aug 04 '16 at 10:22
Ys, thanks, I did. Yet there are a number of assorted answers. I tried setting the optimisation to none in release, but that changed nothing. — Fabrizio Bartolomucci, Aug 04 '16 at 10:25
And most of them refer to issues now correctly detected by the compiler. — Fabrizio Bartolomucci, Aug 04 '16 at 10:27
The issue seems due to the not found files. I tried to compile a project without this issue and it did it jut fine. — Fabrizio Bartolomucci, Aug 04 '16 at 12:18
By doing git add * and then committing the warning disappeared but no so the error. — Fabrizio Bartolomucci, Aug 04 '16 at 13:16
Not so myself. I have two projects I am not able to compile with no hint about what is wrong about them. — Fabrizio Bartolomucci, Aug 04 '16 at 13:39
@FabrizioBartolomucci Were you using Core Data Code Generation? Did you find a solution to your problem? — Frizlab, Sep 04 '16 at 21:19
Nope, no CoreData, the problem went away by itself though probably due to some remote fixing of Xcode by Apple, I do not know for sure. — Fabrizio Bartolomucci, Sep 05 '16 at 12:56

score 53 · Answer 1 · answered Feb 01 '17 at 17:13

53

Happened to me, when I had two classes with the same name in my project. After deleting the redundant one, error disappeared.

answered Feb 01 '17 at 17:13

Adam Bardon

3,829
7
38
73

1

Same for me. Just FYI, the appcode shows exactly where the problem is. – mihatel Aug 31 '17 at 11:54
We can only hope for the same feature in XCode :) – Adam Bardon Aug 31 '17 at 11:59
1

This is most common mistake. Thank you for your answer – Fatih TAN Nov 01 '18 at 13:15

score 19 · Answer 2 · edited Dec 29 '18 at 07:32

19

If you look above the error, Xcode will tell you which ViewController is added/declared twice, navigate to it and remove the reference. Build and you're good to go.

edited Dec 29 '18 at 07:32

Cœur

37,241
25
195
267

answered Mar 06 '17 at 15:36

Giggs

851
10
16

score 16 · Answer 3 · answered Oct 20 '17 at 17:34

I am going to tell you my silly mistake, the error is showing the issue and It took 3 hours to me to understand. look into below error

look into above 2 lines of error, the problem is shown, Obviously, In my case Xcode is complaining that Location.swift and Customer.swift file is missing, look into my project hierarchy, the same issue can understand.

It's my advice to everyone that first understand the error and then look into issues. I removed my desktop files, which were referenced in the project, and therefore compile error occurred.

score 15 · Answer 4 · answered Sep 05 '16 at 20:08

15

Clean your project that fixed my project Product/clean

answered Sep 05 '16 at 20:08

Jeylani Osman

199
3
13

score 13 · Answer 5 · answered May 25 '17 at 07:30

13

I got this error for core data models that i've created manually.And it got resolved by changing particular entity's 'Codegen' attribute to 'Manual/None' under Data Model Inspector.

answered May 25 '17 at 07:30

Shyam

417
4
16

score 4 · Answer 6 · edited Dec 29 '18 at 07:33

4

If you change any file folder location or change any Objective-C Bridging file path. Then it's happened some time.

Update your Bridging path.
Clean your project alt + Shift + Command + K
Quit Xcode completely Command + Q
Open project again and wait for Xcode to index files.

edited Dec 29 '18 at 07:33

Cœur

37,241
25
195
267

answered Feb 08 '18 at 05:22

Md Imran Choudhury

9,343
4
62
60

score 3 · Answer 7 · answered May 11 '17 at 17:02

I got this error when I was trying to run an xcode project. A swift file wasn't being found and complied correctly, even though clearly in the xcode project file you can see the swift file and when you click on it in finder the file comes up as a separate xcode swift file. I solved this by:

Deleting the problematic swift file
Creating a new swift file with the same name
Xcode prompts that the file is already created, press replace
copy/replace the code/etc. in the file
Clean the project (for good measure)
Run the project

score 2 · Accepted Answer · answered Sep 05 '16 at 08:04

2

The problem went away by itself for mysterious reasons. Instead of the whimsical linking error I got a new bunch of errors due to Swift 3 fling which the app compiles and run fine.

answered Sep 05 '16 at 08:04

Fabrizio Bartolomucci

4,948
8
43
75

I still have stuck in this problem and make clean + Close Project + and try manual and generate . Still the same problem in Archive . My Xcode 8.2.1 and using Swift 3.0 , Could please share the answer for this problem – wod Feb 01 '17 at 21:31

score 2 · Answer 9 · answered Sep 23 '16 at 19:10

2

The solution that worked for me is I had to delete the .xcdatamodeld file in my project and create a new one. This solved it.

answered Sep 23 '16 at 19:10

PlateReverb

654
1
7
21

score 2 · Answer 10 · answered Jun 06 '17 at 10:41

2

I got this error and resolved by changing Xcode command line tools,

Goto Xcode -> Preferences -> Choose Locations tab

Choose required Command Line Tools from drop down, run the project error has been fixed.

answered Jun 06 '17 at 10:41

Mohammed Rizwan N

21
2

score 1 · Answer 11 · answered Jul 13 '17 at 09:44

1

In my case the error triggered when Xcode could not find a file/folder from the external Framework and dependency. In such a case just pod update / pod install do the job.

answered Jul 13 '17 at 09:44

Oskar

2,522
32
37

score 1 · Answer 12 · answered Aug 13 '17 at 22:22

1

Try removing inactive file(deleted file) from Build phases...

answered Aug 13 '17 at 22:22

Cwalker815

186
2

score 1 · Answer 13 · answered Mar 06 '18 at 10:18

Based on @Mohammed Rizwan N answer

If error not gone, do the clean project and close Xcode. Then click right button on .xcodeproj/.xcworkspace file and choose appropriate Xcode version.

In my case, I tried to run a project in Xcode9/Swift4, while the project was written on Xcode8/Swift3

score 1 · Answer 14 · answered Sep 26 '18 at 10:01

1.Go to build settings and check the path of the info.plist file and bridging header file.

2.If not sure they are correct , from the left side drag and drop the files into respective fields .This creates the path automatically .

Clean the project and build again .

score 0 · Answer 15 · answered Dec 08 '16 at 22:40

0

I created 3 new groups and put my MainVC under one of those groups. After I deleted one of the new groups I created, the error went away after I cleaned my project.

answered Dec 08 '16 at 22:40

Kevin Curry

1

score 0 · Answer 16 · answered Jul 10 '17 at 02:36

0

Please update your entire log which suggests the error, mine is telling me I have duplicated classes in file

answered Jul 10 '17 at 02:36

Mogician Ha

85
1
2
10

score 0 · Answer 17 · edited Dec 29 '18 at 07:34

0

For me it was ,

Product > alt + Clean Build Folder

OR

alt + Shift + Command + K

edited Dec 29 '18 at 07:34

Cœur

37,241
25
195
267

answered Sep 11 '17 at 18:26

iUser

1,075
3
20
49

score 0 · Answer 18 · edited Dec 29 '18 at 07:33

This is mainly because xcode is not getting the exact path of any file or duplication of file name under linking area.

In my case I have added bridge header file under Resources file and added the path in BuildSettings->Objective-C bridge header-> bridgehearfilename.h

You should specify the exact path of that file in this section.

eg: BuildSettings->Objective-C bridge header-> Projectfolder/Resources/bridgehearfilename.h

Correct your file paths in the build settings then Clean and build the project.

score 0 · Answer 19 · answered Oct 16 '17 at 18:39

0

Try closing Xcode, cleaning the project and building again.

At first, cleaning wasn't enough. I had to actually close it and try again.

answered Oct 16 '17 at 18:39

dustinrwh

888
1
14
16

score 0 · Answer 20 · answered Dec 04 '17 at 13:06

I faced this issue when I resolved git conflict for the project file, which was for adding and removing some files.

What I found out is Xcode creates the folder named folder named "Recovered References", just search this from bottom left search option from Xcode and delete it. After you delete it you will only get an error for missing files. Resolve that by adding files again by right-clicking and selecting add files option. Once you are done with it project compiles with no error.

score 0 · Answer 21 · answered Feb 17 '18 at 22:52

0

Happened to me when I found two swift files with the same name within the project, even if the classes have different names.

answered Feb 17 '18 at 22:52

Hatim

1,516
1
18
30

score 0 · Answer 22 · answered Feb 27 '18 at 04:41

0

In my case error came when I moved my bridging-Header.h file from one folder to another. and when I checked in Build Settings -> Objective-C Bridging Header it was showing old path. Then I moved that file back to previous folder.

answered Feb 27 '18 at 04:41

Khushboo Dhote

198
3
13

score 0 · Answer 23 · answered Jun 26 '18 at 14:25

0

My problem was that my machine was running out of available space. Restarting it cleaned up ~8GB of temporary files, but I guess you can also delete something instead.

answered Jun 26 '18 at 14:25

budiDino

13,044
8
95
91

score 0 · Answer 24 · answered Sep 21 '20 at 15:42

Do these 3 steps:

Clean Project: Shift+Command+K
Make sure low disk space shouldn't be on your mac
Focus on the upper lines of this error...Try reading them again...Paste those files that are missing or having some light icon in xcode project navigator and delete those files with light icon.

Hope you will fix the error.

score 0 · Answer 25 · answered Oct 12 '20 at 06:41

0

I tried to run a project in Xcode12/Swift4, while the project was written on Xcode8/Swift3 so I install Xcode version 11.7 and run this work for me.

answered Oct 12 '20 at 06:41

Muhammad Ahmad

388
4
9

Xcode 8.0 Command /Applications/Xcode-beta.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/swiftc failed with exit code 1

25 Answers25

Linked