0

I recently upgraded my development environment to the following specifications:

  • Xcode Version: 15.2 (15C500b)
  • iOS Version: 17.2

My project is built using Ionic, and my current environment versions are:

  • Node.js: v14.21.3
  • npm: 6.14.18
  • CocoaPods (pod): 1.15.2

After the upgrades, I encountered a build error when trying to run my project on iOS. The error is "Command PhaseScriptExecution failed with a nonzero exit code."

enter image description here

In an attempt to fix this issue, I found several recommendations suggesting that I should modify the Pods-[your-project-name]-frameworks.sh script by changing the line source="$(readlink "${source}")" to source="$(readlink -f "${source}")". However, upon inspecting the file, I noticed that the -f option has already been added.

I've tried cleaning the project and rebuild, but the problem persists. I'm not sure what else I can do to resolve this issue. Could anyone provide further insights or solutions to fix this build error?

Thank you in advance for your assistance.

2
  • 1
    try: Go to build pahses tab -> expand [CP] embed pods frameworks -> tick / untick For installbuild only also tick / untick based on dependency analysis. Try this with multiple times. Commented Feb 26, 2024 at 14:36
  • 1
    @NajamUsSaqib Your trick worked somehow! Unbelievable 🤣 Commented Jun 12, 2024 at 13:11

4 Answers 4

2

Solved this issue by turning off 'User script sandboxing': Project -> Select your project -> Build Settings -> Filter -> User script sandboxing -> No

enter image description here

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

Comments

1

I managed to resolve the issue I was encountering with my Ionic project. The solution was quite straightforward. Here's what I did:

  1. First, I deleted the Pods directory located in ios/App.
  2. Then, I reran the synchronization process for my project.

Comments

1

Faced the same issue with my Flutter project. I checked the framework.sh file and it already had the "-f" flag.

However, I realized that I had forgotten to run "flutter pub get" which solved my problem. LOL.

1 Comment

What??? how this can even work. I don't get it.
0

I found this workaround helpful. I recently switched to nvm for using NodeJS. I had replaced #2 with #1 in below location.

Your_Project/ios/.xcode.env.local file

  1. export NODE_BINARY=/Users/sultanularefin/.nvm/versions/node/v18.20.4/bin/node
  2. export NODE_BINARY=/usr/local/bin/node

Comments

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.