I got
error: can't exec 'codesign' (No such file or directory) after I upgrade to Xcode 5.0.
when I try to run the app on the real device.
My codesign file is under /usr/bin.
but somehow, xcode could not locate it.
There are some errors in my /etc/launchd.conf file. I correct the issue in launchd.conf file. and I restarted my computer, everything works fine.
My launchd.conf looks like this now.
setenv PATH /usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/Users/emmychen/bin:$PATH
export PATH=$PATH:/Users/emmychen/bin
Related
My project is running fine in Xcode 11.3 but recently when I upgraded to Xcode 12 app is not getting installed in simulator and showing the error - Could not install at this time.
Failed to get FD to bundle executable....
I suddenly had the same problem, after years of work on the same project across several versions of Xcode and MacOS.
On Xcode 12.4 and MacOS 10.15.5, although everything was working fine, suddenly I got this error popup "Failed to get FD to bundle executable" while trying to Run the project on a(ny) Simulator.
I tried all the proposals I could find online, including changing the Executable Type (which had never changed) or clear the empty env vars defined in the Build settings (there weren't any). Uninstalling/reinstalling Xcode didn't help. Upgrading to MacOS 10.15.7 didn't either. Of course the Apple Support has been of no use at all (they replied with a few general FAQ links about how to use Simulator).
The only thing that worked for me was to checkout the project in a different folder...
The weird thing is, if I rename again my new folder to the initial folder name, it does the error again! It sounds to me like a MacOS bug and/or an Xcode bug.
Error running `xcrun simctl install 95F3A7B0-67B3-490E-B798-D1CBBF813B83 /Users/yakjuly/.expo/ios-simulator-app-cache/Exponent-2.21.3.tar.app`: An error was encountered processing the command (domain=IXUserPresentableErrorDomain, code=1):
Unable To Install “Expo Go”
Please try again later.
Failed to get FD to bundle executable at /Users/yakjuly/Library/Developer/CoreSimulator/Devices/95F3A7B0-67B3-490E-B798-D1CBBF813B83/data/Library/Caches/com.apple.mobile.installd.staging/temp.Nf39ZM/extracted/Exponent-2.21.3.tar.app/Expo Go
Underlying error (domain=MIInstallerErrorDomain, code=4):
Failed to get FD to bundle executable at /Users/yakjuly/Library/Developer/CoreSimulator/Devices/95F3A7B0-67B3-490E-B798-D1CBBF813B83/data/Library/Caches/com.apple.mobile.installd.staging/temp.Nf39ZM/extracted/Exponent-2.21.3.tar.app/Expo Go
I have this problem when I get started with react native.
The issue for me is the file in /Users/yakjuly/.expo/ios-simulator-app-cache/Exponent-2.21.3.tar.app is broken. After I delete this file and re-run the command. it succeeds installing app in iOS simulator.
What solved this for me was the following:
close emulator
clean project and build folder
Shortcut: Command+Shift+K
GUI: Menu Bar -> Product -> Clean/Clean Build Folder
restart emulator
Xcode 13.2.1
The following steps helped me -
1. Select simulator
2. Goto Device
3. Select -> Erase All Content and Settings...
Hopefully, now you will be able to install and run the app on your simulator.
I'm developing an iOS App using Firebase SDK, The app runs perfectly on the simulator, but when I try to run it on an actual device I'm getting an error like this
Also when I'm trying to archive it. I forgot to tell that I used cocoapods to install Firebase SDK. Thanks!
I had this error because the xcode version.
I have created the project using the xcode beta version, then i updated it and got this error.
hours later, when I gave up trying to resolve this error, when trying to install another pod, this error occurred:
/Library/Ruby/Gems/2.3.0/gems/cocoapods-1.5.3/lib/cocoapods/command.rb:118:in git_version': Failed to extract git version fromgit --version("xcrun: error: active developer path (\"/Applications/Xcode-beta.app/Contents/Developer\") does not exist\nUsesudo xcode-select --switch path/to/Xcode.appto specify the Xcode that you wish to use for command line developer tools, or usexcode-select --installto install the standalone command line developer tools.\nSeeman xcode-select` for more details.\n") (RuntimeError) ...
when trying to run the
pod-install command
Then I ran the sudo
xcode-select command --switch path / to / Xcode.app
which was prompted for the error, and the Firebase-related error was miraculously fixed. Hope it could helps someone.
I archive a binary with Xcode 7, then I validate the binary and when I try to submit to the iOS Appstore, I get the following errors:
Could not make parent directory for: /Users/DEC/.itmstransporter/softwaresupport/bin/Frameworks/MZXMLMarshalling.framework/Resources/Info.plist
Could not configure software support.
An exception has occurred: /Users/DEC/.itmstransporter/softwaresupport/bin/Frameworks/MZXMLMarshalling.framework/Resources/Info.plist (No such file or directory)
The session's status is FAILED and the error description is 'failed to open ssh session. (16)'
The app runs perfectly in the iOS simulator and on the iPhone 5(iOS 8.3)
and it doest seems like there is an error in the code.
I also try the uploading with the application loader but the same happens.
I think it could be something about xcode 7 or ios 9 because i didnt have this problems before.
Thanks for your help.
This seems to solve the issue:
$ cd ~/.itmstransporter
$ rm update_check*
$ mv softwaresupport softwaresupport.bak
$ cd UploadTokens
$ rm *.token
(from http://blog.csdn.net/sqc3375177/article/details/49175691)
I have a .app file that I copied to my mac in a local directory (Ex: /appium/test.app) and I pointed appium to the .app file. I'm getting the following error when running in the simulator:
Could not save new Info.plist
Error: ENOTDIR, not a directory
Can any one resolve my issue? Correct me if i am doing any fundamental wrong.
I've gotten that error if I start the Appium server via the Mac App and point it at an .app directory in the Settings of the app.
You should try running Appium from the command line.
Someone recently posted a similar issue at can't exec 'codesign' (No such file or directory)
However, for whatever reason, it has received a down-vote rather than something helpful. So I am going to try to post this myself, with some additional data in hopes that some kind SO'er has been through this or just knows what the problem is.
I have a project that builds fine under Xcode 4.x, but ever since installing Xcode 5 DP2 (and DP3,4 and 5) and now the released version, I get this error when trying to build or archive to anything but the simulator:
CodeSign /Users/cb/Library/Developer/Xcode/DerivedData/MyApp-bdtrjmwxxokvesathmrttgwwesfq/Build/Intermediates/ArchiveIntermediates/MyApp/InstallationBuildProductsLocation/Applications/MyApp.app
cd /Users/cb/Development/MyAppCore/FrontEnd/Mobile/iOS/MyApp
setenv CODESIGN_ALLOCATE /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/codesign_allocate
setenv PATH "/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/usr/bin:/Applications/Xcode.app/Contents/Developer/usr/bin:$PATH:/usr/local/mysql/bin:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin"
Using code signing identity "iPhone Developer: CB (D4HZSHL6DF)" and provisioning profile "MyApp_DEV" (BB1C0589-147E-4E12-945D-8FB093B70C70)
codesign --force --sign F5...B73 --resource-rules=/Users/cb/Library/Developer/Xcode/DerivedData/MyApp-bdtrjmwxxokvesathmrttgwwesfq/Build/Intermediates/ArchiveIntermediates/MyApp/InstallationBuildProductsLocation/Applications/MyApp.app/ResourceRules.plist --entitlements /Users/cb/Library/Developer/Xcode/DerivedData/MyApp-bdtrjmwxxokvesathmrttgwwesfq/Build/Intermediates/ArchiveIntermediates/MyApp/IntermediateBuildFilesPath/MyApp.build/Release-iphoneos/MyApp.build/MyApp.xcent /Users/cb/Library/Developer/Xcode/DerivedData/MyApp-bdtrjmwxxokvesathmrttgwwesfq/Build/Intermediates/ArchiveIntermediates/MyApp/InstallationBuildProductsLocation/Applications/MyApp.app
If I open Terminal and cd to
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/
and then run the command from there, it executes just fine. So the tools seem alright, as do the provisioning profiles. The problem seems to be with Xcode itself.
It should be noted that I have deleted Xcode completely, as well as my codebase, along with all provisioning profiles and certs. I re-checked-out my code, and re-installed Xcode 5 from a fresh download, entered Apple ID into Xcode and re-created/fetched the certs and profiles, and still have the same issue.
I also went in to the project file itself and removed duplicate PROVISIONING_PROFILE entries per a couple of answers I found, to no avail.
I can build this same project from 2 other machines using Xcode 5, so it is something happening specifically on my box, or with my particular installation, it would seem. But other than that, I am stumped.
Has anyone seen/fixed this, or have any ideas of where to look for an answer?
Thanks for any input!
I copied codesign from /usr/bin/
to:
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin
and it worked for me.
Try this:
For Mountain Lion before starting signing process Please run below command as first command.
For Xcode 4.x:
export CODESIGN_ALLOCATE="/Applications/Xcode.app/Contents/Developer/usr/bin/codesign_allocate"
For XCode 5:
export CODESIGN_ALLOCATE="/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/codesign_allocate"
Solved my problem, thanks for the help. The issue was with my path. I had set my path via /etc/launchd.conf and I was driving myself insane trying to edit my path via ~/.bashrc etc. Make sure /usr/bin is in the path that xcode picks up. This page reminded me: http://overwatering.org/blog/2012/08/setting-path-osx-mountain-lion/
If you added the flag --deep to "Other code signing Flags" i.e. using cut copy paste, it may happen that an "invisible" char was added. In this case the error message is like:
/usr/bin/codesign --force --sign "" --deep --entitlements (...)
No such file or directory
If you see those two quotes "" then there is an invisible char before '--deep' in your compiler settings.
In this case the compiler throws the error message "No such file or directory".
(/usr/bin/codesign seems to not be existing, but it is (!))
To resolve this issue go to build settings, search for 'Other code Signing Flags', delete all entries, and retype them manually (no cut copy paste).