question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[Maverick] Command CompileSwiftSources failed with a nonzero exit code

See original GitHub issue

Describe the bug

Running the boilerplate with Xcode Version 13.4.1 (13F100) produces these two errors:

image
ExpoModulesCore Group
Command CompileSwiftSources failed with a nonzero exit code

CompileSwiftSources normal arm64 com.apple.xcode.tools.swift.compiler (in target 'ExpoModulesCore' from project 'Pods')

( a bunch of output )

remark: Incremental compilation has been disabled: it is not compatible with whole module optimization
Command CompileSwiftSources failed with a nonzero exit code
FBReactNativeSpec Group
Command PhaseScriptExecution failed with a nonzero exit code
Node found at: /var/folders/8j/349q4sb50qv8zwvxk751kdsw0000gn/T/yarn--1660789716516-0.8769200455720108/node
/Users/jh/Code/ignite-cli/boilerplate/ios/Pods/../../node_modules/react-native/React/FBReactNativeSpec/../../scripts/react_native_pods_utils/script_phases.sh: line 83: /var/folders/8j/349q4sb50qv8zwvxk751kdsw0000gn/T/yarn--1660789716516-0.8769200455720108/node: No such file or directory
Command PhaseScriptExecution failed with a nonzero exit code

Ignite version

Maverick

Additional info

No

Issue Analytics

  • State:closed
  • Created a year ago
  • Comments:15 (15 by maintainers)

github_iconTop GitHub Comments

1reaction
jamonholmgrencommented, Sep 1, 2022

By the way, running yarn will output this:

Auto-generating `.xcode.env.local` with
$NODE_BINARY=/var/folders/8j/349q4sb50qv8zwvxk751kdsw0000gn/T/yarn--1661999583968-0.618588229915737/node

But then it runs fine.

So, I guess this means that sometimes you’ll just need to remove that file and re-yarn.

rm ./ios/.xcode.env.local
yarn
0reactions
jamonholmgrencommented, Sep 26, 2022

Fixed (better) in #2214.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Uncategorized Command CompileSwift… - Apple Developer
I got an Xcode error that says "Uncategorized Command CompileSwiftSources failed with a nonzero exit code". I notice that in the toolbar next...
Read more >
Command CompileSwiftSources failed with a nonzero exit ...
When I clean the project and build it the following error appears: CompileSwiftSources normal x86_64 com.apple.xcode.tools.swift.compiler ...
Read more >
command compileswiftsources failed with a nonzero exit code ...
Describe the bug Running the boilerplate with Xcode Version 13.4. 1 (13F100) produces these two errors: ExpoModulesCore Group Command CompileSwiftSources ...
Read more >
Command CompileSwiftSources failed with a nonzero exit code
Describe the bug. An error upon runtime of "Command CompileSwiftSources failed with a nonzero exit code". To Reproduce
Read more >
Command CompileSwift failed with a nonzero exit code in ...
After updating to the latest version of Xcode at the moment (version 10.0) the project is unable to build because it found some...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found