xcrun

I've upgraded OSX Lion to Mountain Lion and reinstalled the Command Line Tools (as the upgrade deleted them). From then xcrun does not work anymore. The xcode-select is set to /usr/bin, the binaries are in that directory too, but if I run xcrun with an argument (ex. xcrun gcc) it displays this: xcrun: Error: failed to exec real xcrun. (No such file or directory) I've tried setting the path again with xcode-select and reinstalled the CLT. Nothing helped. Any suggestions how to fix this? nick The only fix is hack apparently. I tried the script mentioned and it worked OSX 10.8 xcrun (No such file

When building a new iPhone app in Xcode, I'm getting this error: codesign error: code signing identity 'iphone developer' does not match any code-signing certificate in your keychain. once added to the keychain, touch a file or clean the project to continue. What's the fix? Gabe Hollombe The fix is pretty simple. In the Build Results window (which you probably got to by clicking the error icon in the lower right corner of your project window), change the pulldown menu from ‘Device - iPhone xxx’ to ‘Simulator - iPhone xxx’. (source: kickasslabs.com ) You need to be part of the $99 developer

I'm trying to automate the process of building apps for our clients using bash scripts running on a Mac Mini Server (OSX 10.7). My script is based on the spectacularly useful script from github originally posted at https://gist.github.com/949831 I'm building the app using xcodebuild, and then signing and embedding the mobileprovision file using xcrun. When I do all this with a mobileprovision file I manually installed into Xcode using the GUI (e.g. double-clicking) it works fine. If I simply try to use a mobileprovision file copied onto the server with SCP it fails (Code Sign error:

I am trying to Start Xcode with the custom toolchain and to be enabled to use the open source version of Swift. Steps are taken from Swift.org And I receive this error: xcrun: error: unable to find utility "launch-with-toolchain", not a developer tool or in PATH The open source Swift toolchain from https://swift.org/download/#apple-platforms requires the latest Xcode 7.2 (currently: beta 4). The location of the developer directory used by xcrun and other build tools must be set to this Xcode 7.2. This can be done from the command-line with sudo xcode-select -s /path/to/Xcode7.2-beta.app

Is there anyway that I can change a setting in xcode without opening xcode? I have an automated xcodebuild / xcrun process going on but I need to change 1 value: Targets > Select your target > Build Settings > Code Signing Resource Rules Path add : $(SDKROOT)/ResourceRules.plist I can't find any file where I might put this line... What You can do is to run: xcodebuild -target <target> -configuration <configuration> -showBuildSettings This command shows all the settings that are filled for target and configuration passed. Find the name of the key that contains $(SDKROOT)/ResourceRules.plist

I'm using GIT and am trying to push my code and getting the following error when using the Terminal . I don't use XCode , I'm using Android Studio . The command I tried using was: git branch Networking Error: xcrun: error: invalid active developer path (/Library/Developer/CommandLineTools), missing xcrun at: /Library/Developer/CommandLineTools/usr/bin/xcrun` I am running on El Capitan Beta 4 update if that helps in anyway . Instead of installing xcode you can install git from here and change the path in android studio to /usr/local/git/bin/git as shown in the image below. This way you save

Attempting: xcrun simctl in terminal yields: xcrun: error: unable to find utility "simctl", not a developer tool or in PATH I have Xcode 6.2 Beta. Any suggestions? I solved this problem by entering Xcode > Preferences > Locations And assigning the Command Line Tools This is in Xcode Version 7.2 beta (7C46t) If you need a GUI instruction See below!!! leo.tan In terminal, try this. xcode-select -s /Applications/Xcode.app /Applications/Xcode.app is your Xcode.app path. I had the same problem. My application was working well but suddenly in next run, it started throwing the "simctl" error. It