Skip to content
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

Build error in Xcode 11 #100

Open
ataravati opened this issue Nov 2, 2019 · 5 comments
Open

Build error in Xcode 11 #100

ataravati opened this issue Nov 2, 2019 · 5 comments

Comments

@ataravati
Copy link

I get the following build error in Xcode 11.

sed: ./Pods/CSV.swift: in-place editing only works for regular files
Command PhaseScriptExecution failed with a nonzero exit code

@yaslab
Copy link
Owner

yaslab commented Nov 2, 2019

Are you editing the source code (.swift file) using the sed command in the build phase script? If so, you might be able to build by excluding the Pods directory from source code search.

By the way, the reason why the sed command fails is because ./Pods/CSV.swift is a directory, not a file.

@ataravati
Copy link
Author

Are you editing the source code (.swift file) using the sed command in the build phase script? If so, you might be able to build by excluding the Pods directory from source code search.

By the way, the reason why the sed command fails is because ./Pods/CSV.swift is a directory, not a file.

No, I'm not editing the source code. As soon as I add CSV.swift to my Podfile, I get that error when trying to build.

@yaslab
Copy link
Owner

yaslab commented Nov 2, 2019

Hmm, when I created a new Xcode project, there was no PhaseScriptExecution command. . .

When pod install is executed, two PhaseScriptExecution commands, [CP] Check Pods Manifest.lock and [CP] Embed Pods Frameworks were added by CocoaPods. These are working properly.


The environment I tried is as follows.

  • Xcode 11.2
  • CocoaPods 1.8.4
  • macOS 10.15.1

@ataravati
Copy link
Author

Here's my environment:

  • Xcode 11.1
  • CocoaPods 1.8.4
  • macOS 10.15.1

@ataravati
Copy link
Author

I upgraded Xcode to 11.2 and I still have the same issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants