XCode Beta 4 Build Error

[michaelgmcd]

Please help prevent duplicate issues before submitting a new one:

• I've searched other open/closed issues for duplicates before opening up this new issue.

When building with XCode Beta 4, Down (installed via CocoaPods) fails to build with the following error:

<unknown>:0: error: unknown argument: '-Wno-shorten-64-to-32'
Command CompileSwiftSources failed with a nonzero exit code

This issue was also posted by someone else on Stack Overflow

[mglass]

Commenting out this line in the Down.podspec file: spec.compiler_flags = '-Wno-shorten-64-to-32' worked for me, at least for now. No promises that there aren't any side effects though. I have a local version of the pod for various reasons, so this was fairly simple for me to do; your results may vary, but it will get you up and running again for the time being.

[barrypress]

I verified this happens with a clean iOS project, no content other than pod install of Down. I filed a bugrep with Apple.

I lack the understanding to know how to use the info of commenting out the link in the podspec, as I can't find a podspec file on the computer (did find podspec.json), and even then don't know how to make an edit take effect, so I can't verify the comment above works.

I do have pod --version 1.7.5, so the other input I found via google on pod vs. Xcode incompatibilities didn't help either.

[iwasrobbed]

Thanks for filing an issue, but this is best for StackOverflow since it's not specific to Down. There is already an existing answer that's linked to the original StackOverflow question: https://stackoverflow.com/questions/57085119/xcode-11-beta-4-error-command-compileswiftsources-failed-with-a-nonzero-exit-co

[barrypress]

What I think is true is that The podspec icludes no-shorten-64-to-32 But no-shorten-64-to-32 is apparently not a legal argument (any longer?) If you look at.CocoaPods/CocoaPods#9014 (comment)  <CocoaPods/CocoaPods#9014 (comment)>it's apparent that what cocoapods fixed isn’t this problem, and indeed I suspect if you were take the no-shorten-64-to-32 line out of the podspec this issue goes away. Thanks for considering this reply! Barry

…

On Jul 23, 2019, at 4:43 PM, rob phillips ***@***.***> wrote:

[mglass]

Thanks for filing an issue, but this is best for StackOverflow since it's not specific to Down. There is already an existing answer that's linked to the original StackOverflow question: https://stackoverflow.com/questions/57085119/xcode-11-beta-4-error-command-compileswiftsources-failed-with-a-nonzero-exit-co

The linked SO post does not actually apply here; I tried it before digging in further and it didn't resolve the issue.

[lilyball]

It's not that it's not legal anymore, it's that it was never legal for Swift files but Xcode prior to Xcode 11 beta 4 didn't pass per-file compilation flags to swiftc (and per-file compilation flags is apparently how CocoaPods was defining these flags).

[iwasrobbed]

Happy to accept a PR for this; it will likely just introduce a few warnings in the underlying c code

[ykphuah]

The workaround is not working, created a pull request:
#170