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

Question

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:

I have tried:

Cleaning and deep cleaning (shift + alt + cmd + k)
Deleting the Derived Data folder
Restarting Xcode

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?

garrettmurray · Accepted Answer · 2019-07-18 00:49:08Z

32

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.

answered Jul 18, 2019 at 0:49

garrettmurray

3,3681 gold badge28 silver badges24 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

Cœur Over a year ago

The inhibit_all_warnings! issue was fixed in CocoaPods 1.7.5, but there are other issues introduced by Xcode 11 beta 4 regarding pods with a podspec that specifies a compiler_flags.

Cœur · Accepted Answer · 2019-07-25 08:53:03Z

20

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

edited Jul 25, 2019 at 8:53

Cœur

39k25 gold badges207 silver badges282 bronze badges

answered Jul 18, 2019 at 8:35

pingwinator

1,0098 silver badges8 bronze badges

6 Comments

Jordan Wood Over a year ago

I can't upvote this enough! Thanks for the timely info, Xcode beta 4 was only released yesterday!

Jordan Wood Over a year ago

FYI, the cocoapods PR for this feature is here.

garrettmurray Over a year ago

Thanks for the link, @JordanWood. I edited pingwinator's answer to include a link to the PR as well.

Wilson Gramer Over a year ago

It looks like this fix has now been shipped in version 1.7.5, so updating Cocoapods should resolve the issue.

ArisRS Over a year ago

for me <unknown>:0: error: unknown argument: '-w' still exist

|

Community · Accepted Answer · 2020-06-20 09:12:55Z

7

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

In Terminal run

sudo gem update cocoapods
And then, on your project directory

pod install

edited Jun 20, 2020 at 9:12

CommunityBot

11 silver badge

answered Jul 20, 2019 at 15:04

EBDOKUM

1,8464 gold badges17 silver badges33 bronze badges

3 Comments

ArisRS Over a year ago

<unknown>:0: error: unknown argument: '-w' still exist

Feldur Over a year ago

Any thoughts as to why this might not be working? I created a new iOS project, pod init, add Down as a pod, pod install, and it fails. Verified on 1.7.5.

Daniel Ryan Over a year ago

Looks like the Down pod is having issues: stackoverflow.com/questions/57089656/…

sriram neelamegam · Accepted Answer · 2019-11-27 06:42:32Z

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

answered Nov 27, 2019 at 6:42

sriram neelamegam

12 bronze badges

Collectives™ on Stack Overflow

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

4 Answers 4

1 Comment

6 Comments

3 Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

4 Answers 4

1 Comment

6 Comments

3 Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related