-
Notifications
You must be signed in to change notification settings - Fork 224
Xcode 10 beta: CompileSwiftSources failed with a nonzero exit code #111
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
As suggested in #102, this was solved by deleting the CommonCrypto directory. |
If we delete CommonCrypto, then how to use it. Can you please provide the solution. |
@jonblatho There's no CommonCrypto directory under Pods/JSONWebToken. Which directory do you mean? |
I have same issue |
@nagarajaghantasala With Xcode 10/Swift 4.2, CommonCrypto is exposed natively as part of Swift (for Apple platforms only), rendering the included modulemap unnecessary and causing a name collision. Removing the modulemap solves the collision. @Ast3r10n I can't reproduce that. I just pulled the JWT pod into a fresh project and the CommonCrypto directory is located under Pods/JSONWebToken: The Podfile used:
@EdwardSun123 Not sure which issue exactly you’re referring to, but hopefully some of the above information helps. Some PRs in this repo also offer more permanent solutions to the issue. |
I looked for the CommonCrypto directory but it just isn't there. EDIT: I was looking in the wrong place. The directory is there, but I still find it easier to just remove the redeclaration. |
In my case I connect an actual iphone not simulator and run the app once on it, It solved the problem. But connect iphone firstly, then choose it from the menu of simulators, then press run button. |
Running on real device showed me the exact error. Thanks @GergesEid |
You may have another reason causing this error. Regards. You are welcome @ergunkocak |
The following build error occurs in Xcode 10 beta:
Here is the full invocation:
This occurs in the JSONWebToken project when using CocoaPods. No further information is provided.
The package does compile:
$ swift build
(with a warning for accessingString.characters
)The package does not compile:
Same error both times.
The text was updated successfully, but these errors were encountered: