142

When I try to build my app with Xcode, an error interrupts the build process:

Command CompileStoryboard failed with a nonzero exit code

Sometimes, it shows this error instead:

Command CompileSwift failed with a nonzero exit code

I have New Build System turned on.

What can I do to fix this?

Improve this question
4
  • 1
    In xcode 10 - stackoverflow.com/a/52722094/822420 it may help you
    – Ramkumar Paulraj
    Commented Oct 9, 2018 at 13:29
  • 20
    Everybody wrote down his own case, damit apple, what a frustrating environment is that xcode thing
    – yerlilbilgin
    Commented Feb 8, 2021 at 18:06
  • Also see here. Tldr the report navigator may not give all information you need. So it might be a good idea to look into the issue navigator...
    – mfaani
    Commented Mar 21, 2022 at 16:16
  • Apple has the worst development platform
    – novice
    Commented Apr 13, 2022 at 6:44

51 Answers 51

Reset to default
1
2
80

Closing Xcode for me didn't have an effect. Instead, I cleaned the project using CommandShiftK.

I also found another reason: I had a storyboard reference to another storyboard which I had removed. The quick fix was deleting this.

enter image description here

Improve this answer
2
  • Well closing your project does not clean it that's why it didn't work :)
    – arled
    Commented Feb 8, 2019 at 11:50
  • I to go this error. In my Cordova config.xml file the deployed-target was set to 11.0 - but after upgrading to Xcode 13.1 it recommend a bunch of project updates, one of which was setting the deployed-target=12.0. After accepting the recommended 12.0 change the next compile threw the above error. I then fixed the config.xml deployed-target to 12.0, performed a clean on my project, restarted Xcode, and the error was gone.
    – rolinger
    Commented Nov 8, 2021 at 16:39
51

I also facing same issue in xcode 10 and tried all the solutions provided but nothing working.

Then I deleted all the files and folders of the following folder :

~/Library/Developer/Xcode/DerivedData

and it worked like a charm.

Improve this answer
5
  • 17
    This answer worked. For copy and pastibility into terminal use this: cd ~/Library/Developer/Xcode/DerivedData && open .
    – tww0003
    Commented Oct 28, 2018 at 21:51
  • 1
    thank you, I have been looking for solution hours, you saved the day!
    – ikel
    Commented Jul 24, 2019 at 2:53
  • I can't even find this path. But did the trick with @tww0003 code.
    – Dpedrinha
    Commented Jan 26, 2020 at 0:26
  • @ Dpedrinha Yes because that is of my local system. I have updated path now you will be able to find it.
    – Krishna Meena
    Commented Jul 14, 2020 at 3:45
  • 2
    Din't work for me
    – Gulnaz Ghanchi
    Commented Nov 3, 2022 at 6:22
40

When you stop building a project when the compiler is in the middle of something "important", this error could appear. In that case, building the project again and letting it finish normally makes this error disappear.

Improve this answer
8
  • 11
    Didn't work for me. This error appeared when i try to localize the info.plist file.
    – Ricardo Mutti
    Commented Mar 5, 2018 at 20:41
  • 2
    Didn't work with me also , specially when i try to imbed framework I created before.
    – Abdulrahman Masoud
    Commented Sep 25, 2018 at 8:29
  • 3
    Didn't work. Also tried to clear build folder using command + alt + shift + k. No reaction.
    – atereshkov
    Commented Sep 25, 2018 at 19:33
  • 2
    Cleaning first (CMD+SHIFT+K) then building (CMD+B) worked for me
    – user5306470
    Commented Jun 4, 2019 at 21:21
  • 1
    The hint was very helpful for me, even if it didn't help immediately. In the menu Product / Build for I found 'Build For', which finally solved the problem.
    – Ronald Hofmann
    Commented Apr 19, 2021 at 9:11
30

This is a known issue with Swift 4.2 and Xcode 10. I found an article here that fixed it for me: https://github.com/Yummypets/YPImagePicker/issues/236

In short, go to your projects build settings, and add a user defined setting named SWIFT_ENABLE_BATCH_MODE and set its value to NO.

Previously, I tried each of the methods suggested here (rebuild, exit Xcode, clean and rebuild, purge Derived Data files). None of them worked.

Once I added the user define build setting per the article, Swift then told me the true error. In my case, it was a missing }, but it could be any number of problems.

Improve this answer
2
  • I tried this and no result.... Anyother ways @cdeerinck
    – Pavan Gangireddy
    Commented Nov 2, 2021 at 5:51
  • I did find this useful. I had an error in a DispatchQueue and couldn't' see the error until I using this, the logs then pointed me to the lines inside the dispatch queue and that allowed me to then find it was just a problem with an unwrapped optional failing to get it's type. Really simple. Get rid of your dispatch queues and you may see the error without having to set SWIFT_ENABLE_BATCH_MODE
    – Dan M
    Commented Jul 14, 2022 at 1:39
15

I encountered this error when I was upgrading my project from Swift 4 to 5. I first updated all my pods to their latest versions. When I built, some pods showed this error.

The following steps resolved this issue for me:

  1. Removed all pods from Podfile
  2. Executed pod install to remove all installed pods
  3. Executed pod deintegrate to remove support for CocoaPods
  4. Deleted Podfile.lock and .xcworkspace from my project so no CocoaPods anymore
  5. Now my project is a pure Xcode project
  6. Opened my project from the regular .xcodeproj file
  7. Changed Swift Version of my project to Swift 5
  8. Cleaned the project (cmd+shift+K)
  9. Quitted Xcode
  10. Restored all pods to my Podfile
  11. Executed pod install to reintegrate CocoaPods and add my pods
  12. Opened the project from the .xcworkspace file
  13. Cleaned and rebuilt
  14. Some old pods that were still using Swift 4.0 (SlideMenuControllerSwift in my case) were set to Swift 5.0, caused many build errors in their code. I corrected it back to Swift 4.0 by opening the Pods project and selecting its target.
  15. Cleaned again, rebuilt.

Now I have only errors in my own project code related with difference in Swift version I made. My job now is to fix them.

Improve this answer
2
  • 1
    What if we use Carthage instead of Pod?
    – IgorGanapolsky
    Commented Sep 2, 2020 at 17:54
  • I'm sorry I have not used Carthage before. I even moved to Swift Package Manager now.
    – Mostafa Al Belliehy
    Commented Dec 18, 2021 at 4:56
12

This error happened to me when I forgot to change entity Properties before creating NSManagedObject subclass. Solved by:

  1. delete Entity+CoreDataClass.swift and Entity+CoreDataProperties.swift.
  2. under "class" of the entity model inspector, change "module" to Current Product Module and "codegen" to Manual/None.
  3. recreate the NSManagedObject.

image

Improve this answer
1
  • What is CoreDataClass?
    – IgorGanapolsky
    Commented Sep 2, 2020 at 17:53
11

I had the error Command LinkStoryboards failed with a nonzero exit code, and found that I was using a reference to a non-existent storyboard. I had recently changed the name of a storyboard file, so changing the reference from the 'old' name to the 'new' name solved it for me.
You may not have exactly the same error as me, but an easy way to find a more detailed explanation of the error is to:

  • Show the issue navigator (while the build time error is showing)
  • Click the error: Click the error in the issue navigator
  • Then, you should see more about your error: Command LinkStoryboards failed with nonzero exit code


I hope this helps. Please, I am aware that I am answering from experience of a different error than this question was asked about, but I believe this advice should help you conquer similar problems!

Improve this answer
11

For me cleaning the project (Command + Shift + K) and restarting xCode worked for me

Improve this answer
9

If you have multiple targets, where two or more targets have files with the same name, check the target membership of those files in Files inspector. The error occurs when multiple instances of the equally named file have set the target membership for the same target.

Improve this answer
1
  • This led me into the correct investigation path. After reviewing all files, I noticed that some "didn't" have the Target Membership they were supposed to have (no idea why). I checked the checkbox in that file's inspector and suddenly everything is building again. Go figure.
    – Alex
    Commented Jul 17, 2022 at 21:11
7

Since this issue looks to have dozens of possible solutions and the root cause could be very vague, I'll throw my situation into the ring. Half of my pods were failing with some sort of CompileSwiftSource failure, but only on archive. I was still able to build for device and simulator just fine. I tried a lot (if not all) of the solutions suggested here with no luck. One of the pods had a slightly different error before the CompileSwiftSource error so I went to updating and trying to fix that single pod. It was the Cache library for iOS which hadn't been updated in a while. There was a fork that resolved the issue with updating to Xcode 10.2 that I was able to update to and after that, all of the other issues took care of themselves. So look for a single outlier in your pods if you're getting a bunch of them erroring out and start there.

Improve this answer
7

Switching to the legacy build system fixed the issue for me

Improve this answer
2
  • How can we switch back to legacy build system in Xcode 11.3?
    – Jayprakash Dubey
    Commented Dec 2, 2020 at 6:15
  • 2
    File > Workspace Settings > Check legacy
    – Charlton P
    Commented Mar 4, 2021 at 17:29
3

In my case, I was clean build folder then restart my mac then it's work.

Improve this answer
0
3

I had the JSONwebtoken pod installed and that was causing issues. I needed to delete the CommonCrypto folder that is in the JSONWebtoken pod folder. Here is a ->link<- explaining the issue. This started happening in Xcode 10.

Improve this answer
3

I tried a lot of the options discussed here.

  • Delete and reinstall pods
  • Clean Build Folder
  • Delete Derived Data
  • Add SWIFT_ENABLE_BATCH_MODE and set its value to NO
  • Restarting Xcode and Recompiling
  • Restarting iMac and Recompiling
  • set Compilation Mode to Incremental
  • Changed build settings: SWIFT_COMPILATION_MODE = singlefile and SWIFT_OPTIMIZATION_LEVEL = "-O"

Nothing worked. I'm using Xcode Version 11.0 beta (11M336w).

Finally I downloaded a fresh copy and replaced the one I had previously installed. It was the same exact version. That did the trick.

Improve this answer
3

In my case it was about having a file named Location. after some digging I find out that it was about having two file with the same name (weird). Cause I don't, however, it's been solved by removing the file and adding another file with a different name.

filenames are used to distinguish private declarations with the same name
Improve this answer
3

This can also occur when you have two swift files with the same name. For example, two ContentView.swift files

Improve this answer
2

In my case, I used too complicated initializations inside a class extension. It suddenly broke my build.

class MyClass { }
extension MyClass {
static var  var1 = "", var2 = "", var3 = "", var4 = "", ...., var20 = ""
}

Resolved:

class MyClass { }
    extension MyClass {
    static var var1 = "",
    static var var2 = "",
    static var var3 = ""
    static var var4 = "", ...., 
    static var var20 = ""
    }
Improve this answer
2

In my case it was empty assets catalog, when I delete it everything was fine again.

Improve this answer
2

Command CompileSwift failed with a nonzero exit code

This error happens when you are migrating your code from Xcode 9 to Xcode 10+. It due to any class name is conflicting with existing apple classes. For Example: State, Event etc.

  1. So first change the class/structure name if any existing in your code like "State" to "StateDetail"

  2. If Info.plist is added in target, remove tick mark from it so it will not copy app bundle (Latest Xcode10 security reason).

    • Select Info.plist file and uncheck under "Target Membership" in right side Identity inspector

And build code again!!!

Improve this answer
2

In my case, the problem was that I assigned a .swift class to the viewController in the storyboard, while the project was Objective C.

Improve this answer
2

I got this error while trying to run my unit tests in a submodule. What I have done is:

Change the simulator => Clean the project => Build the project => Run unit tests.

After this, my unit tests ran without any issue.

Improve this answer
1

I have the issue like that and my solution is change a little thing in Build Settings:

SWIFT_COMPILATION_MODE = singlefile;
SWIFT_OPTIMIZATION_LEVEL = "-O";

it work to me

Improve this answer
1

Alright, I was having the same problem with Xcode 10. I usually use a storyboard for every view, that way if someone is helping it's easier to fold code in. I needed to make one of the view on one storyboard the initial view Controller.

Improve this answer
2
  • Please explain this further, i don't get this answer completely
    – Mohsin Khubaib Ahmed
    Commented Nov 7, 2018 at 7:49
  • So, you can have more than one storyboard, and in a multiview app I use a storyboard on every view, for modularity and that way if someone is working on another part of the app it's a lot easier to pull in those changes. On the ViewControllers there is an option to make it the initial view controller for that storyboard that loads when you call storyboard.loadInitialView() and on one storyboard that option wasn't clicked and when I clicked it it went away.
    – jimistephen
    Commented Nov 8, 2018 at 12:24
1

In my case it was renaming a file to an existing file in other folder(Group) by mistake, just rename it to what it was then the error disappeared

Improve this answer
1

The targets should be specified with related data such as appicon

Improve this answer
0
1

For me the problem was that on my Podfile I didn't put use_frameworks!. I just uncomment that line, run pod install on the terminal again. And it got fixed.

It was commented since the app was entirely made on Objective-C. Since the app now uses Swift I had to make that change on the Podfile

Improve this answer
1

I had the same error Restarting Xcode and Recompiling Fixed the issue for me.

Improve this answer
1

I got the same error when linking separate storyboards. The error, "Command CompileSwiftSources failed with a nonzero exit code." is shown because I simply forgot to set the view controller inside the second storyboard that I am linking as 'an initial view controller'.

Improve this answer
1

Read various article and tried many things. An easy procedure that worked in my case:

  • removed Pods folder
  • pod install
  • product, clean build folder
  • product, build
Improve this answer
1

In my use case I had used the function "Refactor to Storyboard" in Xcode 13. It created the new refactored story board fine but failed to add it to bundle resources.

So my fix was to:

  • Select the target project in Xcode Navigator
  • Choose the build phases tab
  • Expand Copy Bundled Resources to see if new storyboard was added. If not, just add it to the list and rebuild.
Improve this answer
1
2

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.