Just thought I should also share what I did for a solution to this issue. I followed the solution outlined in https://stackoverflow.com/a/10823483/666943 but converted the ruby script to shell. At the end I basically installed ios-sim via homebrew and replace the Run Script in the Build Phases of my Test target with the following: if … Read more
You have to set the ONLY_ACTIVE_ARCH to NO if you want xcodebuild to use the ARCHS parameters. By passing these parameters, you can force the proper architecture. xcodebuild ARCHS=i386 ONLY_ACTIVE_ARCH=NO -configuration Debug -workspace MyProject.xcworkspace -scheme MyLib See this reference for details.
Switch Apple Git to Git, the problem will go away. Run brew install git to do it. Relate link: https://blog.smittytone.net/2021/05/21/how-to-fix-xcodebuild-macos-terminal-slow-downs/ Another option is to accept the Xcode License sudo xcodebuild -license accept You can find this referring to the reference in the linked article.
Ok, so nearly 6 (billable) hours later, I’ve gotten the build to work correctly in Xcode and on the command line (and on the build server, the whole point of this exercise). Along the way I would fix one problem just to cause another – I would apparently fix the linker/Ld problem, only to cause … Read more
Apple got back to me with a solution. As of Xcode 7 we should use xcodebuild instead of PackageApplication to produce the .ipa file. xcodebuild has a new -exportArchive option to create an .ipa that works more like Xcode Organizer. So we should now: build an archive with xcodebuild archive create the .ipa with xcodebuild … Read more
I’m not sure if this is a new option but the 5.0 release of xcodebuild has an option -derivedDataPath which allows you to specify the directory you’d like all the build products to sit in. For instance, passing -derivedDataPath build creates the folder build relative to where you ran xcodebuild from, and you can find … Read more
Based on the Bryan Mussial answer The root cause is that the default behavior of Schemes is to keep schemes ‘private’ until they are specifically marked as shared. In the case of a command-line initiated build, the Xcode UI never runs and the xcoderun tool doesn’t have its own cache of Schemes to work with. … Read more
checking the “shared” box in the “Manage Schemes” dialog moves the schemes to Project.xcodeproj/xcshareddata/xcschemes/Scheme.xcscheme so even if you have a clean checkout that has never been opened via the xcode ui, this will work. we use this so that buildbot can build our apps
You’ll find (and you can watch during the build) the complete build output in the Log Navigator. That’s the right most icon of the small icons just below the Run and Build buttons.