CODEWITHSUNDEEP
xcodecocoapodsxcode11
Daniel Ryan
Daniel Ryan

Reputation: 7102

Xcode 11 beta 4 error: Command CompileSwiftSources failed with a nonzero exit code

I've downloaded the latest Xcode beta 4. When I build I'm getting the same error with 3 of my pods:

Command CompileSwiftSources failed with a nonzero exit code
<unknown>:0: error: unknown argument: '-w'
<unknown>:0: error: unknown argument: '-Xanalyzer'
<unknown>:0: error: unknown argument: '-analyzer-disable-all-checks'

This is the MarqueeLabel pod logs: enter image description here

I have tried:

I can't see the error listed in the release notes. https://developer.apple.com/documentation/xcode_release_notes/xcode_11_beta_4_release_notes

Does anyone know what the problem is or a workaround?

Upvotes: 35

Views: 6700

Answers (4)

sriram neelamegam
sriram neelamegam

Reputation: 1

Resolved for me!!!!

The issue is actually i created two files with same name. So after i renamed one of a file and error cleared.

Upvotes: -1

pingwinator
pingwinator

Reputation: 999

CocoaPods had a fix for this that got released as part of CocoaPods 1.7.5.

Below is the answer preceding the 1.7.5 release:

If you need to use Xcode 11 Beta 4 in the mean time, you could install a patched version of CocoaPods from that pull request:

1. Open Gemfile, replace gem 'cocoapods' with

gem 'cocoapods', :git => 'https://github.com/dnkoutso/CocoaPods.git', :branch => "swift_compiler_warnings"

2. Run bundle install and bundle exec pod install

Keep in mind, this is a temporary solution.

Upvotes: 20

EBDOKUM
EBDOKUM

Reputation: 1846

The latest version of CocoaPods (1.7.5) has this issue fixed!

  1. In Terminal run

    sudo gem update cocoapods

  2. And then, on your project directory

    pod install

Upvotes: 7

garrettmurray
garrettmurray

Reputation: 3368

There is a known issue with Cocoapods and Xcode 11 Beta 4 where inhibit_all_warnings! causes arguments to be set for Swift which do not compile. Removing this inhibit resolves the issue, and Swift warnings can be inhibited with SWIFT_SUPPRESS_WARNINGS = YES on targets instead.

Upvotes: 32

Related Questions