Build fails with "Command failed with a nonzero exit code"

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.

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.

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.

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.

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.

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.

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:
  
• Then, you should see more about your error:

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!

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

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.

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.

Switching to the legacy build system fixed the issue for me

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

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.

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.

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

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

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 = ""
    }

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

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!!!

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

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.

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

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.

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

The targets should be specified with related data such as appicon

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

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

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'.

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

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.