I tried to create a Carthage framework using v0.23.0 and Xcode 8.3.3.
When I ran the command "carthage build --no-skip-current", it led to the following error message:
"*** xcodebuild output can be found in /var/folders/h4/1slt67613tx6c_xdd4ffp9nw0000gn/T/carthage-xcodebuild.mOvSot.log
xcodebuild timed out while trying to read
"
Here is my machine's settings:
xcrun version 32.
Xcode command line tool version:
xcode-select version 2347.
xcodebuild -version:
Xcode 8.3.3
Build version 8E3004b
Carthage version:
0.23.0
Please advise.
Thank you,
Helen
I was getting the same problem when I switched to Xcode 9.
After a carthage build or update the following message came up.
xcodebuild timed out while trying to read AWSiOSSDKv2.xcodeproj
I tried to open the xcodeprok using Xcode, close Xcode and then rerun carthage build. The problem was gone.
I believe that it has to do with something that was missing and added once i opened the project in Xcode.
After carthage update I have to reopen the xcode project that timed out and rerun carthage build this time.
Related
I have an already working react-native project, with bitrise and fastlane deploy also configured.
I used to build the app with the xcode 12.5 version, but with the new apple updates, it was necessary to upgrade the xcode version, because the app started not to build with this xcode version. So I changed the bitrise stack to the same used on my local machine (xcode 13.2.1 on OSX BigSur).
But now, the build is failing with this message:
[14:04:40]: Exit status: 65
[14:04:40]:
[14:04:40]: Maybe the error shown is caused by using the wrong version of Xcode
[14:04:40]: Found multiple versions of Xcode in '/Applications/'
[14:04:40]: Make sure you selected the right version for your project
[14:04:40]: This build process was executed using '/Applications/Xcode-13.2.1.app'
[14:04:40]: If you want to update your Xcode path, either
[14:04:40]:
[14:04:40]: - Specify the Xcode version in your Fastfile
[14:04:40]: ▸ xcversion(version: "8.1") # Selects Xcode 8.1.0
[14:04:40]:
[14:04:40]: - Specify an absolute path to your Xcode installation in your Fastfile
[14:04:40]: ▸ xcode_select "/Applications/Xcode8.app"
[14:04:40]:
[14:04:40]: - Manually update the path using
[14:04:40]: ▸ sudo xcode-select -s /Applications/Xcode.app
[14:04:40]:
And after sometime researching, I found the xcversion plugin for fastlane, to select the properly xcode version. And added the following line to my Fastfile
...
xcversion(version: "13.2.1")
...
And added the following gem to my Gemfile
...
gem "xcode-install"
...
But the same error happens, even with the changes above. Does anyone already faced this problem?
So I currently am building my project and running tests fine when using xcode 13.2.1 run with rosetta.
However, when I successfully add an xcode server bot and added a preintegration script as below, the following error occurs: "Could not find 'Alamofire' for 'x86_64-apple-ios-simulator', found arm64."
I have tried many different project settings, but this seems similar to the error that I get when I attempt to run my project using xcode without rosetta. I have a feeling the build system that the xcode server bot is using doesn't make use of the same rosetta settings that are used when I build from xcode.
Does anyone know of a way in which I could get the xcode server bot to build the cocoapods project while producing the necessary x86_64 version of Alamofire for the simulator?
#!/bin/sh
cd $XCS_PRIMARY_REPO_DIR
export PATH="$PATH:/opt/homebrew/bin/"
echo "Working Dir: $XCS_PRIMARY_REPO_DIR"
echo "Loading Bash Profile"
source ~/.bash_profile
echo "INSTALLING COCOAPODS"
brew uninstall cocoapods
brew reinstall cocoapods
echo "INSTALLING PODS"
~/.rvm/wrappers/ruby-3.0.0/pod install --verbose
I am building an Xcode project using Travis CI. Whenever Travis build the project, everything succeeds up to this message:
Collecting info for testables...
After that, the build times out and errors.
My .travis.yml file looks like this:
language: objective-c
osx_image: xcode7.3
xcode_project: Project.xcodeproj
xcode_scheme: Project
xcode_sdk: iphonesimulator9.3
I am using Xcode 7.3.1 on the macOS Sierra beta.
It looks like you’re running into a known issue with xctool and Xcode 7.3, which is causing your build to fail. You could try replacing Xcode 7.3 with Xcode 7.2 in your .travis.yml, or you could replace xctool with xcodebuild using the sample script below in your .travis.yml.
script:
- xcodebuild build test -project {test-project} -scheme {test-scheme} | xcpretty
Either option should help you get around the error.
I'm experiencing weird behaviour with my iPhone CI job (running in TeamCity). Every once in a while our build fails without any indicative error in the build log. The build reaches the last stage of codesign validation and I get ** BUILD FAILED ** message immediately after.
These are the last lines of the log of a good and bad builds -
Bad Build
[15:00:56] : [CodeSign] /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/usr/bin/Validation /Library/TeamCity/buildAgent/work/dc055fa257f562be/DerivedData/MyProject/Build/Products/AdHoc-iphoneos/MyProject.app
[15:00:58]W: [Step 3/6] ** BUILD FAILED **
Good Build
[14:09:13] : [CodeSign] /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/usr/bin/Validation /Library/TeamCity/buildAgent/work/dc055fa257f562be/DerivedData/MyProject/Build/Products/AdHoc-iphoneos/MyProject.app
[14:09:13] : [Step 3/6] ** BUILD SUCCEEDED **
Because it's running in a CI I looked for user interaction problems (opening the keychain...etc') but usually xcodebuild spews the relevant errors.
Is there any other log I can dig into to find the cause of the build failures?
EDIT:
Seems I had the same problem like build failed jenkins iOS no error.
I also had a similar problem, in my case it was caused by the fact I'm using both Xcode 7.2 and Xcode 6.4 side by side. When the simulator of Xcode 6.4 is open (iOS Simulator 8.4) and I try to start a test from the commandline using Xcode 7.2 I get this 65 error.
Eg. when iOS Simulator 8.4 is open:
# sudo xcode-select -s "/Applications/Xcode 7.2.app/Contents/Developer"
# xcodebuild test CODE_SIGN_IDENTITY="" CODE_SIGNING_REQUIRED=NO ONLY_ACTIVE_ARCH=NO -workspace "/path/to/MyWorkspace.xcworkspace" -scheme "MyProject" -destination "platform=iOS Simulator,name=iPhone 6,OS=9.2"
(cut)
** TEST FAILED **
# echo $?
65
Solution is to kill the simulator before starting the test:
# killall "iOS Simulator"
# killall "Simulator"
The process is called "iOS Simulator" for XCode 6.4 and earlier and called "Simulator" for later XCode versions.
Had the same problem as build failed jenkins iOS no error
tl;dr - CopyPNG failed because of two images with the same name.
You need to remove platform ios - cordova platform rm ios, and then add platform - cordova platform add ios. now build ios - cordova build ios
I hit this when updating to Xcode 8, in my case it was because I had set the PROVISIONING_PROFILE_SPECIFIER setting incorrectly
For Xcode version 13
The following is what worked for me, this is aimed at Xcode version 13, hoping to be helpful
My React native project was cloned, i was able to run the app in android, but while running on iOS it showed error code 65.
After trying most of the solutions and failing, i got it fixed finally. This is what worked for me, and could be useful for some people hopefully.
Clone the project again(not necessary, just telling you what was done)
npm install
pod install (in iOS directory)
If Xcode shows error code 65, if there is legacy deprecation issue --> go to Xcode -->file --> workspace settings --> Check the box at the end of the window saying "do not show diagnostic issue about build system deprecation
run the project again
This is what fixed it for me.
My issue came up after updating to the latest version of Xcode. To resolve, I performed the following steps.
Completely quit Xcode and the Simulator. I had a zombie Simulator process running that I found and closed through Activity Monitor. Be sure no processes for Xcode or Simulator are running.
In Xcode, open the project found in the ios folder of your react-native project.
Xcode may suggest some recommended updates to modules. I accepted their recommendations.
Close Xcode, relaunch your react-native app
I'm moving my first steps in MonoMac.
But I stopped right at the beginning due to some configuration error. I've created a new ManoMac project in MonoDevelop, and then tried some other sample MonoMac xamarin projects from GitHub, but I always get this error compiling:
Error: Can't run /Developer/usr/bin/ibtool (no such file).
ibtool exited with code 1
My configuration:
Operating System:
Mac OS X 10.7.3
MonoDevelop 2.8.6.5
Runtime:
Mono 2.10.8 (tarball Mon Dec 19 17:43:18 EST 2011)
GTK 2.24.5
GTK# (2.12.0.0)
Mono for Android not installed
Apple Developer Tools:
Xcode 4.3.1 (1176)
Build 4E1019
Monotouch: 5.2.5
MonoDevelop.MonoMac 2.6.0.0
All my Monotouch projects compile fine, and I have no problem with the last XCode (following the Xamarin guidelines I successfully upgraded XCode and moved it from the obsolete Developer folder to the Application folder, and downloaded the updated developer command line tools from apple).
I've tried reinstalling MonoDevelop, but with no success. I always get: "Error: ibtool returned error code 1."
Any help is appreciated.
This problem is caused by the Xcode 4.3 installer not updating the Xcode symlinks correctly to point to the active Xcode version. You can fix it with the following command:
sudo xcode-select -switch /Applications/Xcode.app
This upcoming MonoDevelop 2.8.8 release contains a fix for this. You can get it from the beta update channel.
It looks like the MonoMac addin was never updated to work with Xcode 4.3.
A temporary workaraound is to setup symlinks in the proper places in /Developer.
I found the way in the MonoMac forum:
http://mono.1490590.n4.nabble.com/MonoMac-and-XCode-4-3-ibtool-error-Solution-td4403822.html
I report it here:
When using MonoMac and Xcode 4.3, the current MD beta build fails with an ibtool error.
The solutions is to type the following commands in the Terminal console:
sudo rm /usr/bin/ibtool
and then:
sudo ln -s /Applications/Xcode.app/Contents/Developer/usr/bin/ibtool /usr/bin/ibtool
Now it compiles fine.
I got a similar error running Xamarin on Xcode 6.2 and I solved the problem by re-installing the same version of Xcode again replacing the old version per the suggestion on this post: xcode-select active developer directory error on OSX Mavericks.
I may have caused this problem as I was renaming XCode Application. I have several versions installed and was trying to keep them all straight.