Command Compileswift Failed with a Nonzero Exit Code in Xcode 10

Command CompileSwift failed with a nonzero exit code in Xcode 10]

Currently my build is working.
Here you are the steps I tried until it finally worked:

1. Search in the whole project the word CommonCrypto.
2. If you have a Pod containing that header import, remove this Pod from the Podfile and perform a pod install.
3. Clean and build the project.
4. Add again the Pod to the Podfile and perform a pod install.
5. Clean and build the project again using a real device if possible.

And If you don't have that Pod, maybe you can try by making the same steps with some old Pod that you may encounter in your project.

Added information: also If you have some code error inside a Pod, first you need to solve that code problem and then try to compile again the project.

I'm going to copy the changes made in my project.pbxproj. I know it's not very helpful but it's the only thing that have changed in the git difference commit:

Removed: BDC9821B1E9BD1B600ADE0EF /* (null) in Sources */ = {isa = PBXBuildFile; };
Added:   BDC9821B1E9BD1B600ADE0EF /* BuildFile in Sources */ = {isa = PBXBuildFile; };

I hope this can help,

Regards.

Command CompileSwiftSources failed with a nonzero exit code XCode 13

I had this problem surface in Xcode 13.0.

Mohamed Tarek's solution worked for me, but…

I was using cocoapods, so I needed a solution not blown away by pod install; or more specifically fixed with pod install.

Adding the following to the bottom of the Podfile resolved it.

post_install do |installer|
  installer.pods_project.targets.each do |target|
    target.build_configurations.each do |config|
    # some older pods don't support some architectures, anything over iOS 11 resolves that
      config.build_settings['IPHONEOS_DEPLOYMENT_TARGET'] = '12.0'
    end
  end
end

Building with Xcode 12.5 fails with CompileSwift failed with a nonzero exit code and Segmentation fault: 11

I didn't find the solution for this with Xcode 12.5 but everything works fine on Xcode 13 beta.

So, installing Xcode 13 fixed this issue for me.

---

Related Topics