-
Notifications
You must be signed in to change notification settings - Fork 24.4k
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
Command PhaseScriptExecution failed with a nonzero exit code - Error when Archive on Xcode 14.3 #36762
Comments
Having the same issue. Apple M2 Pro, Xcode 14.3. |
+1 |
1 similar comment
+1 |
Facing the same issue. rsync error: some files could not be transferred (code 23) at /AppleInternal/Library/BuildRoots/97f6331a-ba75-11ed-a4bc-863efbbaf80d/Library/Caches/com.apple.xbs/Sources/rsync/rsync/main.c(996) [sender=2.6.9] Command PhaseScriptExecution failed with a nonzero exit code UPDATE |
duplicate of #36739 |
@kelset The patch reported in the problem you cited, does not solve my problem. I had a very strange issue where the pods frameworks script would fail to copy the framework files when archiving a build (building worked fine). |
re opening - but it looks like it's not a react-native problem, but cocoapods, so not really anything we can do about it CocoaPods/CocoaPods#11828 --- I'll pass it along |
While trying to upgrade step by step from 0.69.1 to 0.71.5 step by step I have not gotten fastlane to build the latest week. iOS simulator runs fine. I have applied the target deployment version patch and set my Gemfile for
which resolves to CocoaPods/CocoaPods@3ac99be. Given these changes a clean out and pod-reinstall I'm still seeing symlink issues after running this darling command:
from the ios folder. The log output from fastlane is saying:
Which to me clearly indicates a still present symlink issue. Are we still convinced this is a cocoapods-issue or how RN uses cocoapods or the script? Also, cocoapods does not accept issues with RN/Flutter, as per their new issue template. I am not sure where to start to make this a reproducible issue without RN.
|
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
Yes, same issue here after upgrading to Xcode 14.3. Cocoapods is broken in this release. Anyone been able to resolve? |
Same issue. React Native 0.65. |
check for spaces as you are naming the project folders. Use space alternatives. |
This help me to fix the issue. https://developer.apple.com/forums/thread/725230 Please have a look, may be this will help..! |
For everyone still having this issue, I recommend to follow the instructions in this link and add a post install script for now. |
Hi, anyone are experience these issue? Processing Info.plist ▸ Running script ‘[CP] Embed Pods Frameworks’ ▸ Generating ‘App.app.dSYM’ ** ARCHIVE FAILED ** The following build commands failed: PhaseScriptExecution [CP]\ Embed\ Pods\ Frameworks /Users/runner/Library/Developer/Xcode/DerivedData/App-azlyibamtvkrbhfwntgmcwffjqtw/Build/Intermediates.noindex/ArchiveIntermediates/App/IntermediateBuildFilesPath/App.build/Release-iphoneos/App.build/Script-9592DBEFFC6D2A0C8D5DEB22.sh (in target ‘App’ from project ‘App’) (1 failure) |
@RenzoPH have you tried updating cocoapods to version 1.12.1? Updating to the mentioned version solved all my issues |
Fixed this by updating updating - set -e
+ set +e P.S. Tried switching node from nvm to brew but that didn't made any difference. |
Thanks! Worked for me! |
God, you saved me!!!!!!!! |
Issue present here too. "react-native": "0.72.4", It started out of the blue after updating xcode, basically. |
Thanks @rdnsan
This works for me and it does not generate the ios/.xcode.env.local file. |
also you can try to delete |
Thanks @batuhanbag
This worked for me |
Solved by the below steps (in MAC) 1 remove ios/.xcode.env.local |
I found these steps below to consistently resolve this error. What's strange is I started getting this error for completely new/empty RN projects, and only recently. To resolve it I had to attempt to build the project first in xcode, have it fail, then do all these steps, then it would work the second time. Doing these steps in this order before the first build didn't seem to work. This was using RN 0.73.8 and node 20. I didn't try to test each step individually, so maybe it can be simplified. cd ios |
i had same issue i fix it by changin path of node binary in .xcode.env |
deletion of ".xcode.env.local" was only solution for me |
This works for me |
|
In my case, I deleted |
delete ios/.xcode.env.local file and install pod again it work my side |
In my case I had to create |
Hello everyone, if you encounter errors in Xcode during the "[CP] Embed Pods Frameworks" phase, and have ruled out issues with the ".xcode.env" file, as well as upgraded to CocoaPods version 1.12, you might want to check out my solution. I found that the root cause was that both the My environment info:
|
This work for me |
this worked for me: |
I am also facing the same issues, create new project then when i run the project same issues. Tried all like:
None of the above work. But like you have said i just remove the space in my folder worked. Thanks. |
|
Yes, This work for me |
Also I found compiling from the command line (eg |
I have resolved the issue on both Machine Intel mac(MacOS 13.6 and Xcode15) as well as on Silicon M3 chip(MacOS 14.6 and Xcode 16) .
|
Exatamente o que aconteceu comigo! Vi seu comentário e como já havia tentado de tudo, fui verificar o nome da pasta pai, e la estava o nome com espaço. coloquei um traço no nome e tentei rodar novamente e simplesmente RODOU o projeto de boa! kkkkk nem acredito! Obrigada pela informação! |
I don't understand how this make any sense as the command returns the path to the executable and hard coding the path to node executable is simply writing the output of the command. |
In my case, it was .xcode.env.local. There, the NODE_BINARY was hardcoded to the node path (pointing to homebrew installation) but i had deleted that node and installed the new version using nvm, so i replaced it with
|
Solved th problem looking at this video :https://youtu.be/FmZm0MeE5NE It took two months to solve it!! Added -f and it worked!! |
Check the directory path to see if there is a directory named with spaces? This causes the wrong path when running the project |
Issue: Hermes engine > Command PhaseScriptExecution failed with a nonzero exit code Solution: Get node path by command: Reopen Xcode. Clean Build Folder and Build. |
Guys this worked for me. Check if you have a space in your folder name! |
So ridiculous but it works thanks :) |
Description
Hi Guys, I'm trying to perform an archive using 0.71.5 but I'm getting an error.
The error occurs in Build phase "[CP] Embed Pods Frameworks", when he runs the script with:
"${PODS_ROOT}/Target Support Files/Pods-MyApp/Pods-MyApp-frameworks.sh"
React Native Version
0.71.5
Output of
npx react-native info
System:
OS: macOS 13.3
CPU: (8) arm64 Apple M1
Memory: 79.22 MB / 16.00 GB
Shell: 5.9 - /bin/zsh
Binaries:
Node: 16.13.1 - ~/.nvm/versions/node/v16.13.1/bin/node
Yarn: 1.22.17 - ~/.nvm/versions/node/v16.13.1/bin/yarn
npm: 8.1.2 - ~/.nvm/versions/node/v16.13.1/bin/npm
Watchman: 2022.11.14.00 - /opt/homebrew/bin/watchman
Managers:
CocoaPods: 1.11.3 - /Users/leonardo.felipe/.rbenv/shims/pod
SDKs:
iOS SDK:
Platforms: DriverKit 22.4, iOS 16.4, macOS 13.3, tvOS 16.4, watchOS 9.4
Android SDK:
API Levels: 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33
Build Tools: 29.0.2, 30.0.2, 30.0.3, 31.0.0, 32.0.0, 32.1.0, 33.0.0
System Images: android-32 | Google APIs ARM 64 v8a, android-33 | Google APIs ARM 64 v8a
Android NDK: 22.1.7171670
IDEs:
Android Studio: 2021.2 AI-212.5712.43.2112.8609683
Xcode: 14.3/14E222b - /usr/bin/xcodebuild
Languages:
Java: 11.0.14.1 - /usr/bin/javac
npmPackages:
@react-native-community/cli: Not Found
react: 18.2.0 => 18.2.0
react-native: 0.71.5 => 0.71.5
react-native-macos: Not Found
npmGlobalPackages:
react-native: Not Found
Steps to reproduce
Snack, code example, screenshot, or link to a repository
Investigating the problem I noticed that the problem occurs in the "Symlinked..." of the script Pods-MyApp-frameworks.sh
The Workaround above was suggested for the issue below and has now been merged into the cocoapods repository.
I believe we will need an RC with this FIX pointing to the new version of cocoapods as soon as it is released.
CocoaPods/CocoaPods#11808
CocoaPods/CocoaPods#11828
The text was updated successfully, but these errors were encountered: