Problem provisioning iPhone after 3.0.1 update - iphone

I used to be able to run my application on my iPhone that was running 3.0. After I updated to 3.0.1 I get the error:
No Provisioned iPhone OS Device is Connected.
I followed Apple's guide in the terminal:
ln -s /Developer/Platforms/iPhoneOS.platform/DeviceSupport/3.0\ \(7A341\) /
Developer/Platforms/iPhoneOS.platform/DeviceSupport/3.0.1
but that didn't help.

Make sure that you don't paste it into Terminal as you currently have it (and as Apple have it in their PDF). It should be one line, not two.
ln -s /Developer/Platforms/iPhoneOS.platform/DeviceSupport/3.0\ \(7A341\) /Developer/Platforms/iPhoneOS.platform/DeviceSupport/3.0.1
not
ln -s /Developer/Platforms/iPhoneOS.platform/DeviceSupport/3.0\ \(7A341\) /
Developer/Platforms/iPhoneOS.platform/DeviceSupport/3.0.1

Allow you need to do is duplicated the folder at /Developer/Platforms/iPhoneOS.platform/DeviceSupport/3.0\ \(7A341\) and rename it to 3.0.1

Related

xcrun: error: unable to find utility "xctest", not a developer tool or in PATH

I am using Xcode command line tools instead of XCode app in my MAC.
When i use swift --version
I get Apple Swift version 5.2.2 (swiftlang-1103.0.32.6 clang-1103.0.32.51)
I cloned a project with
git clone https://github.com/apple/example-package-dealer.git
cd example-package-dealer
swift run Dealer
I gives me this error:
error: terminated(72): OLDPWD=/Users/sayansen/Work/EdgeAnalytics/Trial TERM_PROGRAM=Apple_Terminal PWD=/Users/sayansen/Work/EdgeAnalytics/Trial/example-package-dealer SHLVL=1 SSH_AUTH_SOCK=/private/tmp/com.apple.launchd.9lwBmlYTAx/Listeners HOME=/Users/sayansen LIBRARY_PATH=/usr/local/lib __CF_USER_TEXT_ENCODING=0x1F5:0x0:0x0 XPC_SERVICE_NAME=0 TMPDIR=/var/folders/kn/v4zm474x52n8zrycxs7nh5c40000gn/T/ LOGNAME=sayansen SHELL=/bin/bash TERM_PROGRAM_VERSION=433 _=/usr/bin/swift PATH=/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/share/dotnet:~/.dotnet/tools:/Library/Frameworks/Mono.framework/Versions/Current/Commands:/Applications/Wireshark.app/Contents/MacOS CPATH=/usr/local/include SDKROOT=/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk XPC_FLAGS=0x0 TERM=xterm-256color USER=sayansen LC_CTYPE=UTF-8 TERM_SESSION_ID=B285E686-2802-48C6-B8CE-03CA8F2314BF xcrun --sdk macosx --find xctest output:
xcrun: error: unable to find utility "xctest", not a developer tool or in PATH
I am not using XCODE.
I already did this:
sudo xcode-select -s /Library/Developer/CommandLineTools
But not helpfull.
How to solve this error without installing XCode?
Assuming you already have Xcode installed:
Start Xcode, select "Preferences -> Locations". Chances are that your Command Line Tools are not set. Select the suggested Xcode-tools location and you are done.
Additional:
You could check with:
xcode-select -p
which tools are set, mine showed:
/Library/Developer/CommandLineTools
After the location in the preferences was set, it showed:
/Applications/Xcode.app/Contents/Developer
(as it should)
Xcode -> Preferences (or command+,)
Locations tab -> Command Line tools section:
Select a tool there and you are done.
Just a wrong path, all the stuff still can be done w/o invoking GUI:
~/% sudo xcode-select -s /Library/Developer/CommandLineTools
~/% sudo xcode-select -p
/Library/Developer/CommandLineTools
~/% sudo xcode-select -s /Applications/Xcode.app/Contents/Developer
~/% sudo xcode-select -p
/Applications/Xcode.app/Contents/Developer
The latest -s command fixes xcrun: error: unable to find utility "xctest" …

installing Perl modules Statistics::Multtest [duplicate]

I just upgraded from Yosemite to El Capitan (and replicated the problem upgrading from El Capitan to Sierra), and when I try to type for example git status inside a terminal, I get the following error:
xcrun: error: invalid active developer path
(/Library/Developer/CommandLineTools), missing xcrun at:
/Library/Developer/CommandLineTools/usr/bin/xcrun
I don't have Xcode installed, never did.
Anyone have a solution?
Found the fix for the problem here.
xcode-select --install
This will bring up a prompt to install the necessary command line tools.
If you have issues with the xcode-select --install command; e.g. I kept getting a network problem timeout, then try downloading the dmg at developer.apple.com/downloads (Command line tools OS X 10.11) for Xcode 7.1
In macOS 10.14 this issue may also occur if you have two or more versions installed. If you like xCode GUI you can do it by going into preferences - CMD + ,, selecting Locations tab and choosing version of Command Line Tools. Please refer to the attached print screen.
I tried the solution xcode-select --install but it don't help me, I update from Sierra to High and happened this, my solution:
sudo xcode-select --reset
Reassigning the path Xcode is configured with worked for me.
sudo xcode-select -switch /Applications/Xcode.app
You'll then likely be prompted (after trying a command) to agree to the license agreement.
I had the same issue after upgrading to macOS Catalina.
This didn't work for me:
xcode-select --install
Downloading and installing Command Line Tools for Xcode 12 did it!
For me, after I've removed Xcode, I have to switch active developer path as follows:
sudo xcode-select -s /
I just updated to High Sierra and I couldn't just run xcode-select --install. First, I had to actually install xcode from the app store. Then I ran xcode-select --install. Then I had to run sudo xcodebuild -license, agree to the terms, then I could finally run git commands again.
Updated to High Sierra 10.13.2
xcode-select --install ALONE did not work for me.
Download X-code from app store
$xcode-select --install
a. May need to update after install using softwareupdate in command line. $sudo softwareupdate -i "Command Line Tools (macOS High Sierra version 10.13) for Xcode-9.1"
$sudo xcodebuild -license
For Mojave
Uninstall Any old version of Command Line Tools:
sudo rm -rf /Library/Developer/CommandLineTools
Download and Install Command Line Tools 10.14 Mojave.
For those also having issues with heroku command line tools after upgrading, I also had to do the following in my terminal:
xcode-select --install
brew install heroku/brew/heroku
brew link --overwrite heroku
It seems the upgrade to High Sierra messed with my symlinks in addition to forcing me to reinstall xcode tools. I kept getting 'not a directory' errors:
▸ stat /Users/mattymc/.local/share/heroku/client/bin/heroku: not a directory
▸ fork/exec /Users/mattmcinnis/.local/share/heroku/client/bin/heroku: not a directory
Hope that saves someone an hour :)
After update to macOS 10.13.3
After updating do macOS 10.13, I had to install
"Command Line Tools (macOS 10.13) for Xcode 9.3"
downloaded from https://developer.apple.com/download/more/
I upgraded mac os to macOS High Sierra - 10.13.3 and faced a similar issue while trying to install watchman (with command - brew install watchman).
ran the command: xcode-select --install, then ran "brew install watchman" - Everything works fine!
For the most recent version Mojave version 10.14.1, I use
solved by downloaded from https://developer.apple.com/download/more/ " login by apple id, and download
Command line tool newest stable version.dmg
That makes everything work
the old answer
xcode-select --install
doesn't work for me.
sudo xcode-select -s /Applications/Xcode-beta.app/Contents/Developer
Work for me.
Even if you do xcode-select --install it was not fixing that for me as it showed some network error. The problem was that it could not connect to the app store. I did the following to fix it.
Open keystore
Go to system root and select certificates.
Open digicert high assurance EV.
Expand the trust section, mark it as never trust.
Restart system now repeat step 1, 2, 3. and mark the trust policy as
back to use system defaults.
Your app store should work now and you should be able to run xcode-select --install

Installing Realm via CocoaPods in Swift

I keep getting return code 56 from cURL, which is caused by SSLRead returning errors -36 or -9806 in terminal "pod install":
Example 1:
[!] /bin/bash -c
set -e
sh build.sh cocoapods-setup
core is not a symlink. Deleting...
Downloading dependency: core 0.97.0
Downloading core failed:
curl: (56) SSLRead() return error -36
Example 2:
[!] /bin/bash -c
set -e
sh build.sh cocoapods-setup
core is not a symlink. Deleting...
Downloading dependency: core 0.97.0
Downloading core failed:
curl: (56) SSLRead() return error -9806
Has anyone faced this problem installing Realm?
Check which version of xcode-select (Xcode command line tools) you are using. I have to switch between an older version and a newer version for building AOSP from source.
Check using:
gcc --version
The latest is Apple LLVM version 7.3.0 (clang-703.0.31).
You can also check in Xcode by navigating to Xcode > Preferences, selecting the Locations tab and make sure Command Line Tools matches the version of Xcode you are using (mine says Xcode 7.3.1).
You should download core via url first:
curl https://static.realm.io/downloads/core/realm-core-1.3.1.tar.bz2 -O
mkdir $TMPDIR/core_bin
mv realm-core-1.3.1.tar.bz2 $TMPDIR/core_bin
more detail in github:
Be sure that you can access https://static.realm.io/downloads/core/realm-core-0.97.0.tar.bz2 by browser. If not, then it is the problem of your network.
Someone asks for solutions. So following is how I solved this.
download https://static.realm.io/downloads/core/realm-core-0.97.0.tar.bz2 using browser(as for me, I am using shadowsocks, so I can download it).
mkdir $TMPDIR/core_bin
mv realm-core-0.97.0.tar.bz2 core-0.97.0.tar.bz2
mv realm-core-0.97.0.tar.bz2 $TMPDIR/core_bin
the third renaming operation depends on the real needed name used by realm. You should check out $TMPDIR/core_bin when realm starts to download.

How to use gcc 4.2 with Xcode 4.2

I need to use gcc 4.2 with Xcode 4.2 for some older code. How do i get it to show
up. Xcode4.2 seems to have dropped support for it.
Thanks
Here is a way to enable compiling with gcc 4.2 in xcode 4.2. This is mostly done via command line so when you see lines starting with: [ 15:30 jon#MacBookPro / ]$, you need to open up Terminal.app and run the command that starts after the $.
No files or directories are removed or deleted in this process, so it is easy to undo if you need to compile with LLVM in the future.
Download - but do not install yet - xcode_4.1_for_lion.dmg or xcode_4.1_for_snow_leopard.dmg
Now, follow these steps to install Xcode 4.1 into /Developer-4.1:
Backup the working /Developer directory (where Xcode 4.2 is installed)
[ 15:30 jon#MacBookPro / ]$ sudo mv -v /Developer /Developer-4.2
Run the Xcode 4.1 installer using the default install location (/Developer)
Move the new Xcode 4.1 installation to /Developer-4.1:
[ 15:30 jon#MacBookPro / ]$ sudo mv -v /Developer /Developer-4.1
Move the Xcode 4.2 developer directory back to /Developer:
[ 15:30 jon#MacBookPro / ]$ sudo mv -v /Developer-4.2 /Developer
Edit the Xcode 4.2 GCC 4.2.xcspec file to get gcc 4.2 to show in the list of compiler options [1]:
[ 15:30 jon#MacBookPro / ]$ sudo vi "/Developer/Library/Xcode/PrivatePlugIns/Xcode3Core.ideplugin/Contents/SharedSupport/Developer/Library/Xcode/Plug-ins/GCC 4.2 (Plausible Blocks).xcplugin/Contents/Resources/GCC 4.2.xcspec"
Change lines 41 and 42 from this:
ShowInCompilerSelectionPopup = NO;
IsNoLongerSupported = YES;
To This:
ShowInCompilerSelectionPopup = YES;
IsNoLongerSupported = NO;
Backup the Xcode 4.2 iOS/Simulator Framework usr directories:
[ 15:30 jon#MacBookPro / ]$ sudo mv -v /Developer/Platforms/iPhoneOS.platform/Developer/usr /Developer/Platforms/iPhoneOS.platform/Developer/usr.backup
[ 15:30 jon#MacBookPro / ]$ sudo mv -v /Developer/Platforms/iPhoneSimulator.platform/Developer/usr /Developer/Platforms/iPhoneSimulator.platform/Developer/usr.backup
Copy Xcode 4.1 iOS/Simulator Framework usr directories to Xcode 4.2:
[ 15:30 jon#MacBookPro / ]$ sudo cp -rv /Developer-4.1/Platforms/iPhoneOS.platform/Developer/usr /Developer/Platforms/iPhoneOS.platform/Developer/usr
[ 15:30 jon#MacBookPro / ]$ sudo cp -rv /Developer-4.1/usr /Developer/Platforms/iPhoneSimulator.platform/Developer/usr
Copy the gcc and info iOS SDK library directories from Xcode 4.1 to Xcode 4.2 [2]:
[ 15:30 jon#MacBookPro / ]$ sudo cp -rv /Developer-4.1/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS4.3.sdk/usr/lib/gcc /Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS5.0.sdk/usr/lib/gcc
[ 15:30 jon#MacBookPro / ]$ sudo cp -rv /Developer-4.1/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS4.3.sdk/usr/lib/info /Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS5.0.sdk/usr/lib/info
Compile using gcc-4.2!
This is a blog post I've written with a little more info about this process. Feel free to leave a comment on the blog if you run into any issues or have any questions.
[1] If opening from a command line (using something like vi, emacs, nano, etc) make sure to either enclose the path in quotes "/long path/with spaces/in it/file.xcspec" or escape the spaces /some/long\ path/with\ spaces/in\ it/file.xcspec
[2] This is necessary because the iPhoneOS.platform SDK has its own seperate /usr/lib directories but the iPhoneSimulator.platform SDK does not
So the full process for getting gcc 4.2 to work with a fresh install of Xcode 4.2 (non-iOS) is:
Install gcc 4.2
sudo port install apple-gcc42
Tweak Xcode so that gcc 4.2 appears as a compiler option, by editing the Xcode 4.2 GCC 4.2.xcspec file to get gcc 4.2 to show in the list of compiler options:
Open the xcspec file for editing:
sudo vi "/Developer/Library/Xcode/PrivatePlugIns/Xcode3Core.ideplugin/Contents/SharedSupport/Developer/Library/Xcode/Plug-ins/GCC 4.2.xcplugin/Contents/Resources/GCC 4.2.xcspec"
Change lines 41 and 42 from this:
ShowInCompilerSelectionPopup = NO;
IsNoLongerSupported = YES;
To This:
ShowInCompilerSelectionPopup = YES;
IsNoLongerSupported = NO;
Link the gcc 4.2 binary to the location that Xcode expects:
sudo ln -s /opt/local/bin/gcc-apple-4.2 /Developer/usr/bin/gcc-4.2
sudo ln -s /opt/local/bin/g++-apple-4.2 /Developer/usr/bin/g++-4.2
I explained the problem and workaround in this blog post, which condenses the information I found. Feel free to comment.
Thanks chown for sharing this! I struggled around half a day, but at the end it turned out, that I only needed a few steps to achieve my goal:
For everyone that just needs GCC-4.2 to compile apps (no iOS stuff) it's pretty easy:
You don't need to install anything just follow these few steps:
EDIT: If you don't have GCC 4.2 installed already (from an earlier version of Xcode, or manual install), follow the instruciotns from Sean DeNigris in the comments!
Follow step 3 from the original description:
Edit the Xcode 4.2 GCC 4.2.xcspec file to get gcc 4.2 to show in the list of compiler options.
Make Xcode find the compiler again:
ln -s /usr/bin/gcc-4.2 /Developer/usr/bin/gcc-4.2
Also make the linker available:
ln -s /usr/bin/g++-4.2 /Developer/usr/bin/g++-4.2
This works perfectly for me! But as I said it's just for non iOS products!
Simple and userful solution https://github.com/kennethreitz/osx-gcc-installer/
It automates the lists of the declaration on the stackoverflow

XCode can't find GCC

After i updated iPhone SDK to 4.1 I can no longer compile neither for Simulator or Device. I get the following message:
error: can't exec '/Developer/Platforms/iPhoneSimulator.platform/Developer/usr/bin/gcc-4.2' (No such file or directory)
Solution for this?
Check to see if it is there and accessible, sudo ls -l /Developer/Platforms/iPhoneSimulator.platform/Developer/usr/bin/gcc-4.2. Mine has these permissions: -rwxr-xr-x 1 root wheel 166128 Jul 26 15:05 /Developer/Platforms/iPhoneSimulator.platform/Developer/usr/bin/gcc-4.2
Have you tried reinstalling yet?
I solved this by doing:
sudo cp /usr/bin/gcc-4.2 /Developer/Platforms/iPhoneSimulator.platform/Developer/usr/bin/gcc-4.2
I had this happen to me. So for xcode 3.2.5:
gcc-4.2 is definitely installed by
the installer. ie:
ls /Developer/Platforms/iPhoneSimulator.platform/Developer/usr/bin/g* =>
/Developer/Platforms/iPhoneSimulator.platform/Developer/usr/bin/g++
/Developer/Platforms/iPhoneSimulator.platform/Developer/usr/bin/g++-4.0
/Developer/Platforms/iPhoneSimulator.platform/Developer/usr/bin/g++-4.2
Randomly linking in the gcc-4.2 from
the /usr/bin directory is just asking for trouble. That's not the gcc that is part of the xcode package - who knows if it is really the same version.
Reinstalling fixed it for me,
although I was finding that
particular install flakey.