Xcode 10.2.1 Command PhaseScriptExecution failed with a nonzero exit code

Question

Showing Recent Messages:-1: mkdir -p /Users/spritzindia/Library/Developer/Xcode/DerivedData/Contigo-atftiouzrdopcmcpprphpilawwzm/Build/Products/Debug-iphonesimulator/Contigo.app/Frameworks

Showing Recent Messages:-1: rsync --delete -av --filter P .*.?????? --filter "- CVS/" --filter "- .svn/" --filter "- .git/" --filter "- .hg/" --filter "- Headers" --filter "- PrivateHeaders" --filter "- Modules" "/Users/pothi/Library/Developer/Xcode/DerivedData/Contigo-atftiouzrdopcmcpprphpilawwzm/Build/Products/Debug-iphonesimulator/IQKeyboardManagerSwift/IQKeyboardManagerSwift.framework" "/Users/pothi/Library/Developer/Xcode/DerivedData/Contigo-atftiouzrdopcmcpprphpilawwzm/Build/Products/Debug-iphonesimulator/Contigo.app/Frameworks"

Command PhaseScriptExecution failed with a nonzero exit code

I deleted derived data. i have tried :

keychain access -> right click on login -> lock & unlock again -> clear Xcode project

Restarted machine, no use

How do I resolve "Command PhaseScriptExecution failed with a nonzero exit code" error when trying to archive project.

And I am using those librarys

pod 'IQKeyboardManagerSwift'
pod 'SDWebImage', '~> 4.0'
pod 'KRPullLoader'
pod 'Paytm-Payments'

Answer 1

After trying all the solutions, I was missing is to enable this option in:

Targets -> Build Phases -> Embedded pods frameworks

In newer versions it may be listed as:

Targets -> Build Phases -> Bundle React Native code and images

• Run script only when installing

Answer 2

Go to

1. Keychain Access -> Right-click on login -> Lock & unlock again

2. Xcode -> Clean Xcode project ->Make build again

Answer 3

Run the following commands from the ios directory:

1. pod deintegrate
2. pod install
3. XCode Clean build

Or, One-Liner:

pod deintegrate; pod install

Answer 4

This could happen due to a recent issue with XCode 14.3 and cocoapods,

There are two solutions

1 - Update cocoapods as there is a recent fix: sudo gem update cocoapods reference: https://github.com/CocoaPods/CocoaPods/issues/11808

2 - The other workaround is to update all the generated ...-frameworks.sh files to add the -f flag to the call to readlink. In other words, need to replace:

source="$(readlink "${source}")"

with

source="$(readlink -f "${source}")"

For finding frameworks.sh path. Pods --> Target support files --> Pods-(Project_Name) --> frameworks.sh This second solution is from here: https://developer.apple.com/forums/thread/725230?login=true

Answer 5

I have faced the same issue in Xcode 13. I have updated the Crashlytics SDK after that I got the same issue. In my case I have followed the Solution2

Solution1:

I have removed the data from Run Script.

-> Targets ->go to Build Settings ->Click Run Script -> Remove script data

Solution2:

If script is mandatory to your project just select install builds only option.

Select For install builds only option

Script:

"${PODS_ROOT}/FirebaseCrashlytics/upload-symbols" -gsp "${PROJECT_DIR}/#####/GoogleService-Info.plist" -p ios "${DWARF_DSYM_FOLDER_PATH}/${DWARF_DSYM_FILE_NAME}"

In the above script ##### is the app name, if required replace with your app name. If not, use below script.

"${PODS_ROOT}/FirebaseCrashlytics/upload-symbols" -gsp "${PROJECT_DIR}/GoogleService-Info.plist" -p ios "${DWARF_DSYM_FOLDER_PATH}/${DWARF_DSYM_FILE_NAME}"

Solution 3

And one more importent thing is you must set the path of the file properly.

Find the below example path.

You have multiple google services plist piles, in this case you are maintaining 2 different files. Your google service info plist file was under FireBase, Dev. In this case you must add these files path properly. Otherwise you will get the same error.

"${PODS_ROOT}/FirebaseCrashlytics/upload-symbols" -gsp "${PROJECT_DIR}/#####/Firebase/Dev/GoogleService-Info.plist" -p ios "${DWARF_DSYM_FOLDER_PATH}/${DWARF_DSYM_FILE_NAME}"

Solution 3 file structure:

Answer 6

Warning: Legacy Build System is deprecated and will be removed in a further release.

Xcode -> File -> Workspace Setting -> change Build System to Legacy Build System.

Note - Its not the ideal solution.

Answer 7

For me, I was removing Crashlytics, Fabric and FirebaseCrashlytics. So there was a script (Run Script) for Fabric. So since app was running that first and I had removed the framework already, I was getting this error. So I removed the Run Script tab for Fabrics and then it worked perfectly fine.

Answer 8

Xcode 12.2 solution: Go to:

1. Build settings -> Excluded Architectures
2. Delete "arm64"

Answer 9

Solution in 2023

Step 1: Open xcode and search for the following line

source="$(readlink "${source}")"

The file directory would be : ios/Pods/Target Support Files/Pods-Runner/Pods-Runner-frameworks.sh

Step 2: Replace the searched line in the code with -f

Before

source="$(readlink "${source}")"

Change this to:

source="$(readlink -f "${source}")"

Answer 10

I was facing this issue because of Firebase Crashlytics. In Targets -> Build Phases -> Run Script

I had Firebase Crashlytics written like

${PODS_ROOT}/FirebaseCrashlytics/run

I changed that and put it in double quotes

"${PODS_ROOT}/FirebaseCrashlytics/run"

Answer 11

For me, the issue was with the node version that xcode was using. My project was building fine in Expo but not in Xcode after ejecting. I found my answer here: https://github.com/expo/expo/issues/8488

• check you have the latest version of node

  $ node --version

• delete the version in /usr/local/bin/

  $ rm /usr/local/bin/node

• re add a sym link

  $ ln -s $(which node) /usr/local/bin/node

Answer 12

Restart worked for me... Mac OS restart, not xCode restart...

Answer 13

The reason

This build phase also lets you provide a list of input and output files. The script always runs when no input and output files are provided. When input and output files are provided, the script only runs if it has never been run before, one of the input files has changed, or one of the output files is missing

If you are using cocoapods, you may not be required to have an additional run script .

The solution

So the solution is remove the script as follows:

Answer 14

I had a similar error

/{path to project root}/Pods/Target Support Files/Pods-{project name}/Pods-{project name}-frameworks.sh: Permission denied
Command PhaseScriptExecution failed with a nonzero exit code

In my case I had received a zip of a repo that included the Pods folder. It turns out that at some point between it being originally created and sent to me, the *.sh files in Pods/Target Support Files/Pods-{PROJECT}/ had all lost their execute permissions. Giving those files +x was the solution

For Example: chmod +x (File name in the error)

In my case: chmod +x Pods-TestExample-frameworks.sh

Answer 15

In Xcode 12.4, after hours of try found the solution to this.

Go to Target > Architectures Set Build Active Architecture Only to YES and Excluded Architectures to x86_64

Answer 16

In my case the error was caused by the lack of space on my machine. Deleting old builds fixed the problem.

Answer 17

In terminal go to project path and follow the below steps

1. pod deintegrate

2. pod cache clean --all

3. pod install

Answer 18

If your issue is run custom shell script cp embed pods frameworks fails than here is the answer for you

It seems like there is an issue on Xcode 14.3 and higher. There are open issues on iOS developer forum.

ref: https://developer.apple.com/forums/thread/725230?answerId=746897022#746897022

An idea could be to downgrade to 14.2 and see if it works.

Another workaround without downgrading: Open project in Xcode. Go to Pods -> Target Support Files -> Pods-YOUR_APP-Frameworks and change line 44 to below to

source="$(readlink -f "${source}")"

Answer 19

try this step if you need: Xcode 11.5 1- open terminal: cd Path_project 2- cd pod clean 3- pod install

if nothing change make this step

1- open Build Phases for target -> [CP] Embed Pods FrameWork check this field

Answer 20

Another reason for the error might be is that Xcode is running a script during the run phase.

If this is the case, you have 2 options:

1. Delete the script (makes sense if the script is NOT important)

2. Modify/update the scripts location path (Xcode might not be able to locate the script)

In my case, the script was important, so I modified/updated its location.

Originally, the script location path was written like this:

$SRCROOT/scripts/clean-assets.sh

Because the scripts path contained spaces (I moved the project to a new directory), I changed the path to this:

"$SRCROOT"/scripts/clean-assets.sh

By adding quotes to SRCROOT, changing it to "$SRCROOT", the error will go away.

Answer 21

If you experience this issue in flutter. Try running the application on a real iPhone device from other IDE like android studio or vs code.

The issue was flutter SDK missing iOS-profile-release.

So by running the flutter command

flutter run

It downloads the missing things before running and this solves the problem.

Answer 22

XCODE 14.3

There are a number of reasons for this error, I encountered it with rsync issue when archiving my project.

There is an issue with Cocoapods now, because Xcode 14.3 is now using a relative path in its symlink for frameworks.

Either wait for release of Cocoapods version 1.12.1 or make this simple change in your Pods-APPNAME-frameworks.sh file:

Replace:

if [ -L "${source}" ]; then
echo "Symlinked..."
source="$(readlink "${source}")"
fi

With:

if [ -L "${source}" ]; then
echo "Symlinked..."
source="$(readlink -f "${source}")"
fi

Note that -f was added.

You can find this file in

Pods > Target Support Files > Pods-'Your-ProductName' > Pods-YourProductName-Frameworks.sh

Open the file in any text editor and make the change.

Original Source of this solution can be found in this Link

Answer 23

If you are doing Unity Project. You can get this error.

Command PhaseScriptExecution failed with a nonzero exit code

The solution is very simple

https://forum.unity.com/threads/error-on-build.561706/

Pre-requisites: Have cocoapods installed

Not Needed: 1. Install "cocoapods" for installing run following line in your terminal: $sudo gem install cocoapods

2. Open your project folder using terminal
3. Run this line: chmod +x MapFileParser.sh
4. Run this line: chmod +x process_symbols.sh

It worked for me)

I think that installing "cocoapods" is not necessary, only step 3 and 4 enough to solve, but it does not work, you can try it.

Answer 24

solution for me, none of these arch -x86_64 pod install and etc does not work until I did these steps:

1. run sudo gem install ffi in terminal.

2. then run arch -x86_64 pod install and build again.

and worked fine.

Answer 25

For Xcode 11, React Native development environment. I usually have this problem when a dependency is not updated.

You can try following these steps, this usually works for me:

1- Delete your Podfile.lock (I like to use the command '-rm -rf Podfile.lock' on the terminal for this)

2- Delete your Pods folder (I like to use the command '-rm -rf Pods' in the terminal for this)

3- Delete your .xcworkspace

4- Pod install

5- Clear your project into XCode> Product> Clean Build Folder

Answer 26

I have a project in React Native and suddenly this error appeared. I was doing something with homebrew beforehand and this solved the issue for me:

brew update
brew upgrade
brew cleanup

Answer 27

I got the error while using react-native-config.
Got this error since I had an empty line in .env files...

FIRST_PARAM=SOMETHING

SECOND_PARAM_AFTER_EMPTY_LINE=SOMETHING

3 hours wasted, maybe will save someone time

Answer 28

For me the reason was while changing name of app I added a single quote ' in name. I tried different solution and ran into different errors, but at last, while renaming app, I did not include ' single quote and it solved the problem.

Answer 29

If you newer version of Xcode you can do check this box Targets -> Build Phases -> Run Script ->check box>For install builds only

Answer 30

There is an issue with Cocoapods now because Xcode 14.3 is now using a relative path in its symlink for frameworks.

Either wait for release of Cocoapods version 1.12.1 or make this simple change in your Pods-APPNAME-frameworks.sh file:

APPNAME is your Application name

you need to SEARCH and REPLACE:

  if [ -L "${source}" ]; then
    echo "Symlinked..."
    source="$(readlink "${source}")"
  fi

with

  if [ -L "${source}" ]; then
    echo "Symlinked..."
    source="$(readlink -f "${source}")"
  fi

Note that -f was added.

Answer 31

By mistake I had uninstalled carthage from my system. Adding that fixed the issue for me.

Step 1: Download & install latest carthage DMG here: Carthage

Step 2:

carthage update --platform iOS --cache-builds

Step 3: Run project & enjoy. :)

Answer 32

For me, the issue was with Sentry.

1. in Xcode navigate to targets->Build Phases
2. delete the Upload Debug Symbols to Sentry phase
3. clean the build folder and try the build again

Answer 33

I used flutter to create iOS project. When build for Simulator, failed with the same error message. It is solved by following work.

xCode 12.3 Build Settings->Build Active Architecture Only, set it to Yes.

Answer 34

I was able to resolve this error by remove file in Pods -> Targets Support Files -> Pods-AppName -> Pods-AppName-frameworks.sh. After removing that file again install pod using command pod install.

OR.

Try this:

-> quit xcode -> install pod(again) -> start xcode

Answer 35

Take Pods-resources.sh from project path and paste in Terminal

sudo chmod a+x "Pods-resources.sh file path here"

Example Usage:

sudo chmod a+x "/Users/path/Desktop-path/My Work-path/Pods/Pods-resources.sh"

Answer 36

Remove a space in fileName.

For example, from:

/Users/user/Desktop/My Projects/TestProject/

to

/Users/user/Desktop/MyProjects/TestProject/
                      ^ space removed

Answer 37

In my case I have removed Run Script from the Build Phase in XCode.

Answer 38

I tried most of above. I was developing in Flutter so what worked for me was pub cache repair.

Answer 39

When I encountered this error, it was only when I was archiving. Running and building worked fine but archiving kept throwing the error. What worked for me was updating my cocopods:

sudo gem update cocoapods

Answer 40

Actually I had this issue in building my first app looks like there is something changed in the new flutter version 2.5.3 the latest because when I downgrade to 2.5.0 I build on my simulator & my iPhone also with no issues

Answer 41

Nothing worked for me until going to VSCode(IDE APP), and ios/App/App.xcodeproj/project.pbxproj that file, and searched EXCLUDED_ARCHS = arm64, and delete that line,

I did the same thing from Xcode, like go to target>build settings, exclude arc thing, and deleted arm64 from there, didn't work before, but deleting from VSCode worked, weird

Answer 42

Delete these Folders/Files

1. PodFile
2. PodFile.lock
3. Pods
4. Runner.Xcworkspace

Select IOS device/Simulator From Android Studio If build Successfully then build app from XCode

If get new error then

1. open ios/podfile file
2. add this line "platform :ios, '12.0'"
3. open terminal
4. write "cd ios"
5. write "pod update"

Then build again from Android Studio If build Successfully then build app from XCode

Answer 43

1. delete node_modules folder
2. delete Pods folder under ios
3. run yarn cache clean
4. run yarn
5. run cd ios & pod install
6. enjoy build

Answer 44

If you need to run the project in a physical device, none of the answers worked for me in Xcode 13.3. What worked for me was deleting VALID_ARCHS = x86_64; from project.pbxproj everywhere. but this won't let you run in simulator

Answer 45

Facing the same issue check if the parent directory name of your project has no space for Example my project name todoapp is inside My App directory change it to MyApp and it should work.

Answer 46

Solution for Flutter users

In case your app was developed using Flutter, the above steps worked for me:

Run:

1. flutter run
2. flutter pub get
3. run pod install inside the iOS folder
4. build

Answer 47

for flutter developers: make sure that dart:html or dart:js packages are not being imported in any file.

Answer 48

I was struggling with a similar problem in Xcode 14 (error build: Command PhaseScriptExecution failed with a nonzero exit code). This error seems to be a very general description of some more detailed error but I didn't realize it for some time.

Finally I found the description of the error in Build log, but it was really frustrating to navigate there. I recommend you to read the detailed error first and then act. Xcode is not so intuitive... Follow this and navigate there. I hope that it saves time to someone.

Answer 49

More general debugging help

Note that you can double-click the error in the build log to get more details:

Then you will get a tab with the current build log containing more information. Read it really carefully to see if there is a more specific description of the problem there.

In my case I was using Kotlin Multiplatform Mobile and had an error in my build configuration flags there.

If double-clicking does not work: Apparently, you sometimes need to retry building by pressing Cmd + B before being able to double-click the message. I sometimes had to do this multiple times before I could inspect the logs this way.

Answer 50

Another possible problem solution for React Native developers: check if metro port is not busy!

When building in debug mode - make sure port 8081 for metro packager is free, not busy for other app (in my case antivirus agent after restart) or if previous metro service is not hanged there.

Check for processes listening on given port numbers:

sudo lsof -i -P | grep LISTEN | grep :$PORT

If found something on port 8081 - kill it with it's pid id

sudo kill -9 {PID_ID}

Answer 51

For me, the error is because of Port 8081 already in use, packager is either not running or not running correctly

Use the following answer to solve this problem:
https://stackoverflow.com/a/70046852/12280908

In Linux / Mac,

Open terminal and run the command to check whether any program running on the port 8081.

sudo lsof -i :8081

Assume that if you got output something like this,

COMMAND PID USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
node     59 root   18u  IPv4 609033      0t0  TCP localhost:8081 (LISTEN)

Then kill the program with ID 609033 using the following command,

sudo kill -9 59

Answer 52

Probably you should do as follow:

• Remove .xcworkspace and Pod folder
• Run pod install
• Delete derived data
• Clean all project (press alt before click on click)

I tried above things and it worked for me.

Answer 53

In my case was that I changed a line in a script of my Xcode project and that line was badly written (I forgot to add ";" at the end of the line). So I added the ";" and clean and build project.

Answer 54

What helped for me was: In Targets -> Signing & Capabilities > Uncheck Automatically manage signing (or check and uncheck if it was unchecked ) > build project

Answer 55

Build phases > Add > New Run Script Phase

Code:

# Type a script or drag a script file from your workspace to insert its path.
# skip if we run in debug
if [ "$CONFIGURATION" == "Debug" ]; then
echo "Skip frameworks cleaning in debug version"
exit 0
fi

APP_PATH="${TARGET_BUILD_DIR}/${WRAPPER_NAME}"

# This script loops through the frameworks embedded in the application and
# removes unused architectures.
find "$APP_PATH" -name '*.framework' -type d | while read -r FRAMEWORK
do
FRAMEWORK_EXECUTABLE_NAME=$(defaults read "$FRAMEWORK/Info.plist" CFBundleExecutable)
FRAMEWORK_EXECUTABLE_PATH="$FRAMEWORK/$FRAMEWORK_EXECUTABLE_NAME"
echo "Executable is $FRAMEWORK_EXECUTABLE_PATH"

EXTRACTED_ARCHS=()

for ARCH in $ARCHS
do
echo "Extracting $ARCH from $FRAMEWORK_EXECUTABLE_NAME"
lipo -extract "$ARCH" "$FRAMEWORK_EXECUTABLE_PATH" -o "$FRAMEWORK_EXECUTABLE_PATH-$ARCH"
EXTRACTED_ARCHS+=("$FRAMEWORK_EXECUTABLE_PATH-$ARCH")
done

echo "Merging extracted architectures: ${ARCHS}"
lipo -o "$FRAMEWORK_EXECUTABLE_PATH-merged" -create "${EXTRACTED_ARCHS[@]}"
rm "${EXTRACTED_ARCHS[@]}"

echo "Replacing original executable with thinned version"
rm "$FRAMEWORK_EXECUTABLE_PATH"
mv "$FRAMEWORK_EXECUTABLE_PATH-merged" "$FRAMEWORK_EXECUTABLE_PATH"

done

Xcode will refuse to sign them. The above script removes unused architectures.

Answer 56

From Xcode 12.2, you need to remove the $(VALID_ARCHS) build setting from your main and CocoaPods targets, and use $(ARCHS_STANDARD) for all targets. Also, switching to the Legacy Build System is no longer a good solution, since Xcode will deprecate this in a future release. Clear derived data after applying these changes, and before a new rebuild.

Answer 57

I switched from Firebase CocoaPods to Swift Package Manager.

The old symbols upload script still was listed in the 'Build Script' phase.

Delete this and replace with whatever is recommended. At time of publishing it was ' "${BUILD_DIR%Build/*}/SourcePackages/checkouts/firebase-ios-sdk/Crashlytics/run"'.

Answer 58

what worked for me was going to Excluded Architectures and then deleting arm64 on each of the options provided and then clean build

Answer 59

In my case, my VALID_ARCHS was containing x86_64. After deleting it, my project has built without problems.

Answer 60

In my case "pod 'FirebaseUI/Facebook'" was causing Firebase to install an earlier version (Terminal: "Installing Firebase 2.5.1 (was 8.10.0)").

Removing "pod 'FirebaseUI/Facebook'" from the pod file fixed it.

Answer 61

Solution for React Native: Run from project root

(Modify "PROJECTNAME" by the name of the project)

cd iOS

cd Pods/Target\ Support\ Files/Pods-PROJECTNAME

chmod 755 Pods-PROJECTNAME-resources.sh

Answer 62

error SyntaxError: 
Component has already been declared. (68:2)

See Xcode logs if you see the above error,then check your navigation I think you added a double component in your project navigation flow

Answer 63

Specifically for Flutter!

It turned out to be because I move a folder with .dart files to a new location and imports referencing the old directory were still in the code. Deleting those imports fixes the problem.

Unfortunately, with VSCode, all you get is a warning that the import is not used, not that it doesn't exits! Opening Xcode revealed these errors.

Answer 64

I encountered this error in the context of a React-Native project running on iOS. I did several things so it's hard to know which one fixed it:

• Make sure you don't have errors in your bash or zshrc profile -> I had a error related to my jdk. You will know if when opening a terminal window it shows an error/warning
• Make sure you don't have spaces in the path
• If you are using Firebase, make sure your GoogleService-Info file is in the ios folder and not in the ios>project folder
• Do not keep the project in an iCloud folder, especially if you are low on space. I suspect this was a big factor for mine

Finally, my worked when doing these and running react-native 0.67.2. The newer version on it's own didn't fix it, I had to do at least one of these other assertions to get it working.

Things to consider:

• Running the project in Xcode will usually give you more insight into the problem
• Clearing the Xcode build folder wasn't enough on it's own to fix it but when trying a potential solution it is important you do it (and potentially also pod deintegrate && pod install) to make sure there are no traces of the previous ios build.
• I am running node version 16.13, running node 17 gave me different errors and I wouldn't recommend it to date. I am running macOS Monterrey and Xcode 13.2.1, but I tried on BigSur and also Xcode 12.5.1 and the still got the error.

For react-native, this error is discussed in length here: https://github.com/facebook/react-native/issues/31181

Answer 65

For Mac M1, remove arm64 in build settings fix the issue on real device build. I add this string when run with simulator.

Answer 66

I am using multi development environments. One in the office and one at home. The office is the one that I continually use and keep in shape. The one at home I rarely use and hence it becomes out of sync. I am not speaking about the repo being out of date but rather the development environment itself.

So, cutting into chase, my error was more related to new updates resulting from deprecated/obsolete classes which are not available in mu home environment. in office I upgraded to Flutter 3.3 but at home I was still using Flutter 3.0. so there were few new things introduced in 3.3 which I started using and which do not exist in 3.0.

The solution was to upgrade Flutter and then build again. run flutter upgrade in terminal.

Answer 67

I encountered this issue while building the example ios project using react-native-builder bob

Two ways to fix the issue

1. https://stackoverflow.com/a/60090102/7152965 the result mentioned above
2. rename the index.ts file to index.js file in example directory

Answer 68

This issue is literally related to your Xcode build phase script.
In my case, In the Target -> Build Phases -> Bundle React Native code and Images, I found some issue in my build script for Sentry.
It was the path that node binary is located. My script wanted node to be in usr/local/bin/node but my path was opt/homebrew/bin/node something like that.
So I just uninstalled node via homebrew and installed node directly from their homepage.

Answer 69

I'm try After trying almost ALL ways of fixing this issue I came across this command:

flutter run -v > log.txt

This command creates file which logs all events of your build.

Among this long text I found I found a line with a word "error". I guess it's easier just to press cmnd + F and type "error" or "exception" to find the key lines.

Anyway it gave me a key that one of packages doesn't support null-safety. My solution was removing this package.

Answer 70

In my case, the problem occurred because I changed my Intel Core i5 processor to an Apple m2 processor.

Please follow the below steps -

Step 1 - Open Finder -> Applications -> Xcode (right click) -> Get Info -> Open with Rosetta check the box

Step 2 - Open Finder -> Applications -> Utilities -> Terminal (right click) -> Open with Rosetta.

Step 3 - Restart the machine. Then it will ask for Rosetta installation. Install Rosetta. Then run Xcode.

Answer 71

I bumped into this issue when upgrading react native from 0.68 to 0.69.

I was missing ios/.xcode.env.local file. Just added result of which node there for NODE_BINARY: export NODE_BINARY="/opt/homebrew/bin/node" there as in ios/.xcode.env and problem was fixed;

Answer 72

In XCode 14.3 release, this issue is causing most of the time. The below-mentioned solution works for me.

1. First you have to Clean Project using command+shift+k
2. Now re-install pods, and increase the library development target if required. (in Xcode 14.3, the minimum requirement is iOS<= 11.0)
3. Find source="$(readlink "${source}")" globally and replace with source="$(readlink -f "${source}")" on all the places.
4. Now try to archive.

if it does not works, then delete Podfile.lock and Pods folder from your project root path. and then start from 2ns step.

Answer 73

what helped me was what I put here, before there was a configuration from pods

Answer 74

XCODE 14.3

I got this error after upgrade both XCode (13.x => 14.3) and Flutter (2.1 => 3.10) when I tried to archive my project. Normally, I can archive a new flutter application without issues. The reason I got error, I think there was a significant difference between the two versions of flutter. The solution I have implemented below may be useful for those who get an error on a particular project.

Solution:

(We need old version of project which worked because we need the Runner folder which is in ios folder from this old project.)

1. Don't forget to backup your project first.
2. Remove the ios folder from the new project.
3. Open your project directory in terminal and execute flutter create . This command will create a new ios folder.
4. Open old version of project and copy the Runner folder from ios folder, and delete new Runner folder from ios folder in new project, and paste it old Runner folder there.
5. flutter clean
6. flutter pub get
7. cd ios
8. pod install

After these operations try archive again the project.

Answer 75

For me, the problem was the custom Framework linked to my project which was generated via the Swift OpenAPI Generator plugin.

I followed and implemented the tutorial, and had no issues building in Xcode 15, but when trying to run the app in Xcode 14, I got this error.

I fixed the problem by deleting all instances of my custom, OpenAPI generating framework in Targets -> Build Phases.

Answer 76

I had the same problem in Xcode 11.5 after revoking a certificate through Apple's developer homepage and adding it again (even though it looked different afterwards):

Every time I tried to archive my app, it would fail at the very end (not the pods but my actual app) with the same PhaseScriptExecution failed with a nonzero exit code error message. There is/was a valid team with an "Apple Development" signing certificate in "Signing & Capabilities" (project file in Xcode) and locking & unlocking the keychain, cleaning & building the project, restarting,... didn't work.

The problem was caused by having two active certificates of the same type that I must have added on accident, in addition to the renewed one. I deleted both the renewed one and the duplicate and it worked again.

You can find your certificates here or find the page like this:

• https://developer.apple.com/
• "Account" (at the top)
• Log in
• "Certificates, IDs & Profiles" (on the left)

Also check that there aren't any duplicates in your keychain! Be careful though - don't delete or add anything unless you know what you're doing, otherwise you might create a huge mess!

Answer 77

Fix Xcode Command PhaseScriptExecution failed with a nonzero exit code

The Xcode 11+ “Command PhaseScriptExecution failed with a nonzero exit code” error message can be concerning for developers. This may mean that an application or script is not running properly. Some potential solutions can be attempted to troubleshoot the issue.

Solution #1 Open the Xcode project folder in your Terminal app. Enter and execute the following command: pod deintegrate Execute this command: pod install Re-open Xcode > go to Product > Clean Build Folder. Run your app again.

Solution #2 Head over to Keychain Access. Select Lock & unlock again from the login option. Open Xcode > Clean Xcode Project > Run your build again. If neither of those solutions works, then it is possible to reach out to Apple for support.

Sources : Fix nonzero exit code

Answer 78

I was facing the same issue, spend days on this but still no results. Even I reinstalled the xcode, also deleted all the caches At the end I restored my mac. Also upgraded all the softwares to there latest. Hope this will solve your issue since it solved mine. The major issue behind this was it was not able to upload the debug sentry symbols, maybe i modified any major file. So restoring it solved the issue, since it was just a caching issue

Answer 79

If you are here because you recently updated XCode to v14.3 or 14.3.1 like me, a very simple solution is to go and download v14.2 and make your archives through this older version of XCode. Solves the problem in an instant. No need to do any hacking in the config files whatsoever. Until we wait for a fix in the new release of CocoaPods or XCode, this is the solution I chose.

https://developer.apple.com/download/all/?q=14.2