Resolving Command PhaseScriptExecution Errors in Xcode

When building and archiving projects in Xcode, you may encounter an error known as "Command PhaseScriptExecution failed with a nonzero exit code." This issue can arise due to various reasons, including problems with CocoaPods, framework integration, or script execution. In this tutorial, we will explore the common causes of this error and provide step-by-step solutions to resolve it.

Understanding the Error

The Command PhaseScriptExecution error typically occurs when Xcode is unable to execute a script during the build process. This script can be related to CocoaPods, framework embedding, or other custom scripts. The error message may not provide detailed information about the cause, making it challenging to diagnose and fix.

Solution 1: Enable Embedded Pods Frameworks

One common solution to this error is to enable the "Embedded pods frameworks" option in your target’s build phases. To do this:

1. Open your project in Xcode.
2. Select your target from the project navigator.
3. Go to the "Build Phases" tab.
4. Click on the "+" button at the top-left corner of the page and select "New Run Script Phase."
5. Name the new phase (e.g., "Embed Pods Frameworks").
6. In the script text area, add the following line: "${PODS_ROOT}/FacebookSDK/Scripts/embed_frameworks.sh"
7. Ensure that the "Run script only when installing" option is checked.

Solution 2: Update CocoaPods

Another solution is to update CocoaPods to the latest version. You can do this by running the following command in your terminal:

sudo gem update cocoapods

This will update CocoaPods and may resolve any issues related to outdated versions.

Solution 3: Modify Frameworks.sh Files

In some cases, you may need to modify the frameworks.sh files generated by CocoaPods. To do this:

1. Locate the frameworks.sh file in your project directory (e.g., Pods/Target Support Files/Pods-YourProject/frameworks.sh).
2. Open the file in a text editor.
3. Replace the line source="$(readlink "${source}")" with source="$(readlink -f "${source}")".
4. Save the changes and try building your project again.

Solution 4: Remove Script Data

If none of the above solutions work, you can try removing the script data from your target’s build settings:

1. Open your project in Xcode.
2. Select your target from the project navigator.
3. Go to the "Build Settings" tab.
4. Click on the "Run Script" option.
5. Remove any script data that is present.

Solution 5: Select Install Builds Only

Finally, you can try selecting the "Install builds only" option for your script:

1. Open your project in Xcode.
2. Select your target from the project navigator.
3. Go to the "Build Phases" tab.
4. Click on the "+" button at the top-left corner of the page and select "New Run Script Phase."
5. Name the new phase (e.g., "YourScript").
6. In the script text area, add your custom script.
7. Ensure that the "Run script only when installing" option is checked.

By following these solutions, you should be able to resolve the Command PhaseScriptExecution error and successfully build and archive your Xcode project.