My application get crash in apple's testing phase. I have crash log. When I am execute symbolicatecrash command, I get an error
Can't exec "/usr/bin/xcode-select": No such file or directory at /usr/bin/symbolicatecrash
or some how command get executed then it shows same crash file.
My .app & .dSYM files are in same directory.
I don't know what is problem. kindly help me in solving above issue.
Thanks.
xcode-select is missing from /usr/bin. Try installing XCode again, and making sure you choose to install the optional Unix support and the Developer Tools System.
xcode-select is a program which should be in usr/bin that manages the path to XCode if you have multiple XCode versions installed. Versions of tools such as xcodebuild in /usr/bin are just shims that redirect to which ever version of XCode you are choosing to use.
See this Apple link and this man page. In particular, note this: "When writing software that uses the Xcode UNIX tools, Apple recommends using the copy of those tools installed in Xcode/usr instead of /usr, because your users may not have tools in /usr if they have disabled the optional UNIX Development Support choice in the Xcode installer. Your software can find the path to the directory with the xcode-select command (see previous section)."
Related
Struggling to notarize DMG created with install4j v8.0.8. This is what I do:
the install4j runs on Windows machine
we use "MacOS folder archive" media packaged into DMG
everything is signed as required with valid "Developer ID Application" certificate
the DMG then taken to MacOS machine (Big Sur) where we do notarization with our own scripts
notarization fails with an error "The signature of the binary is invalid" pointing to one specific file
When I check the signature of that binary with Mac tools it looks perfectly fine. When I check the signature of the DMG, it looks fine too:
$ codesign -vd --verbose=4 path-to-failed-binary
$ codesign -vvv --deep --display path-to.dmg
When I remove this particular binary from the package, the app gets notarized fine (there are many other binaries inside the package, like JRE). Looking around I see similar problems related to the way the package is zipped.
Which makes me wander if it even possible to create DMG on Windows machines with install4j and then doing the manual notarization on Mac? Or, there is something wrong in install4j creating the DMG package?
This is called though cocoa.h and foundation.h, then NSURLError.h. Not sure why this compiler error just came up when I added portaudio and some other needed frameworks. The error first comes from some existing code. Indeed, there is no CoreServices/CoreServices.h anywhere on the whole system. Do I need to update Xcode?
I found an Apple help answer that said "Those are not makefile directives. How are you trying to build it? Most projects like this come with "configure" scripts that you just need to run from the command line. The only thing you need from Xcode are the Command Line Tools." I don't know what this means or how to do this.
I did run the port audio/configure terminal script, but saw nothing about CoreServices.h being generated. Where does this need to come from?
Thanks.
I further note that in the CoreServices frameworks directory associated with the Xcode project, there is a terminal file called "CoreServices" that when run, generates the error "CoreServices.framework/Versions/A/CoreServices: cannot execute binary file" . What could it be missing?
It's hard to answer your question in this specific case but:
I believe that CoreServices.h can be found at /System/Library/Frameworks/CoreServices.framework/Versions/A/Headers/CoreServices.h, is it not the case on your machine? If not, you might have to re-install Xcode
To install PortAudio, you can also use brew with the command brew install portaudio and then link your project with its headers and libs (/usr/local/Cellar/portaudio/19.6.0/include and /usr/local/Cellar/portaudio/19.6.0/lib) in your Xcode project (under the tab Build Phases > Link Binary with Libraries). That might be the easiest option.
I'm trying to build emacs-25.1 from source on OSx. Everything goes fine until make install. When Emacs is trying to compile xml.c I get:
xml.c:23:10: fatal error: 'libxml/tree.h' file not found
#include <libxml/tree.h>
What is happening?
I'm not sure what your exact error is. However, there is an easier way to build emacs25 on OSX and macOS. Install homebrew is easy and once you have it, all you need to do is run
brew install emacs --with-cocoa --with-rsvg --with-ns
and then
brew linkapps emacs
and your done. Even if you want to do it by hand, you can get the recipe homebrew users to see how it does the build and install, which might help track down your error.
NOTE Check what the actual args are you can pass to the build environment. the ones I've listed are from memory and there are some others you may want to include.
A colleague was having the same problem and posted in the GNU emacs devel list right here. Daniel Suton provided the answer. Xcode is missing:
xcode-select --install
MacOS provides a libxml implementation (and headers) by default when you install xcode. Note that I had installed xcode already. But I've also upgraded from EL Captain to Sierra so my xcode installation must have been erased in the process.
Anyway, after installing xcode like described above and then after git clean -fxd I was able to rebuild emacs again.
Note: getting this on Xcode 4.3.2? Check out the answer to this question.
Note: creating a symbolic link to use the 4.2 lib seems to work fine
cd /Developer/Platforms/iPhoneOS.platform/DeviceSupport/4.2.1\ \(8C148\)/Symbols/
sudo ln -s ../../4.2\ \(8C134\)/Symbols/Developer
After upgrading from 4.2.0 (beta, I believe) to 4.2.1, the libXcodeDebuggerSupport.dylib file is missing, which results in:
warning: Unable to read symbols for /Developer/Platforms/iPhoneOS.platform/DeviceSupport/4.2.1 (8C148)/Symbols/Developer/usr/lib/libXcodeDebuggerSupport.dylib (file not found).
which I guess isn't good. Looking at the directory in question I note:
.../DeviceSupport/4.2 (8C134)/Symbols/Developer/usr/lib/libXcodeDebuggerSupport.dylib
but
.../DeviceSupport/4.2.1 (8C148)/Symbols/System/
.../DeviceSupport/4.2.1 (8C148)/Symbols/usr/
the above two dirs make up all the content in the 4.2.1 folder. No "Developer" folder. Checking the /usr/ dir there, I find no libXcodeDebuggerSupport.dylib file in the lib dir either, so ln -s'ing isn't an option.
Worth mentioning: after the upgrade, I plugged the iPad in and had to click "Use for development" in Xcode organizer. Doing so, I got a message about symbols missing for that version, and Xcode proceeded to generate such, then failed. I restored the iPad and did "Use for development" again, and nothing about missing symbols appeared...
Update: deletion of /Developer and reinstallation of Xcode from scratch does not fix this issue.
Update 2: I just realized that after the reinstall of Xcode,
.../DeviceSupport/4.2 (8C134)/Symbols
is now a symbolic link,
lrwxr-xr-x 1 root admin 36 Dec 3 17:17 Symbols -> ../../Developer/SDKs/iPhoneOS4.2.sdk
And the directory in question has the appropriate files. Maybe this is simply a matter of linking the 4.2.1 dir in the same fashion? I'll try that and see if Xcode freaks out. If someone who has this file could provide a md5 sum that would be splendid. This is what it says for me:
$ md5 /Developer/Platforms/iPhoneOS.platform/DeviceSupport/4.2\ \(8C134\)/Symbols/Developer/usr/lib/libXcodeDebuggerSupport.dylib
MD5 (/Developer/Platforms/iPhoneOS.platform/DeviceSupport/4.2 (8C134)/Symbols/Developer/usr/lib/libXcodeDebuggerSupport.dylib)
= 08f93a0a2e3b03feaae732691f112688
If the MD5 sum is identical to the output of
$ md5 /Developer/Platforms/iPhoneOS.platform/DeviceSupport/4.2.1\ \(8C148\)/Symbols/Developer/usr/lib/libXcodeDebuggerSupport.dylib
then we're all set.
What I just did to solve this problem was:
cd /Developer/Platforms/iPhoneOS.platform/DeviceSupport/4.2.1 (8C148)/Symbols
and created the symlink was missing:
ln -s ../../4.2\ \(8C134\)/Symbols/Developer/ Developer
It solves my problem.
If you do not have anything to lose, just dump the whole Developer folder (or Developer4.2 or however you call it). Reinstall from scratch with the official release of iOS 4.2 SDK - "Xcode 3.2.5 and iOS SDK 4.2".
I did that and found everything gets installed under 4.2 (8C134) only, and does not use 4.2.1 at all.
I do not have enough points to comment to the accepted answer.
Trinca's solution works for me.
Only one addition though:
I got a permission denied in Xterm when I tried to execute the ln command.
just had to enter
sudo xterm
and enter my admin password for the system
and repeat the process in the new terminal.
I am wondering how many people out there are re-installing Xcode because of this issue.
It is definitely a huge waste of time, if people went ahead with re-installation without checking for a better solution. Apple has to keep enough reviewers for sdk runtime checks, and not just for our apps :).
Trashing the folder does not properly uninstall Xcode.
Here are the steps to uninstall Xcode from the PDF readme distributed with the installer:
Uninstalling Xcode Developer Tools
To uninstall Xcode developer tools on the
boot volume along with the
directory, from a Terminal window
type:
$ sudo <Xcode>/Library/uninstall-devtools -mode=all
To remove the underlying developer content on the boot volume,
but leave the directory and
supporting files untouched, from a
Terminal window type:
$ sudo <Xcode>/Library/uninstall-devtools --mode=systemsupport
To just remove the UNIX development support on the
boot volume, but leave the
directory and supporting files
untouched, from a Terminal window
type:
$ sudo <Xcode>/Library/uninstall-devtools --mode=unixdev
Finally, to just uninstall the directory you
can simply drag it to the trash, or
from a Terminal window type:
$ sudo <Xcode>/Library/uninstall-devtools --mode=xcodedir
NOTE: The uninstaller that ships with previous versions of
the Xcode developer tools will not
clean everything off of your system
properly. You should use the one
installed with these Xcode developer
tools.
My gut feeling tells me that this process will properly nuke/replace dylibs like the one that is causing you trouble. At the very least, all trying this will cost you is time.
Do you have the image in ~/Library/iTunes/iPhone Software Updates you could add that to the xcode organizer and get the symbols from there maybe.
I had this issue as well and this did not work for me:
Quit XCode
Delete the folder /Developer/Platforms/iPhoneOS.platform/DeviceSupport/4.2.1\ (8C148)
Plug in your iPhone
Bring up the organizer. It should ask you to collect the symbols from your phone.
Wait while it collects and processes the symbols off your phone.
To resolve this issue, I simply copied the the following directories to the /Developer/Platforms/iPhoneOS.platform/DeviceSupport/4.2.1 (8C148)/Symbols directory:
/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS4.2.sdk/usr/lib/info/
/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS4.2.sdk/Developer/
Once copied over, debugging on the device works normally and no more error messages in the console are received.
Hopefully this helps others that are struggling with debugging on 4.2.1 devices.
Happy Holidays!
What I did was just navigate over to /Developer/Platforms/iPhoneOS.platform/DeviceSupport/Latest/Symbols/ and just drop the whole Developer folder into /Developer/Platforms/iPhoneOS.platform/DeviceSupport/4.2.1 (8C148)/Symbols/
Worked! :)
I have downloaded iPhone SDK 4.0.2, I wanted to install it, but it looks that I don't have enough space. This made me think that maybe I could unistall the previous versions of iPhone SDK and install only the newest one.
Does anyone know how to do this?
Should I keep the old versions? Is there any situation they could be useful?
Thanks for sharing your thoughts!
Should you remove old versions? Up to you. You'll certainly have a "clean" installation. Do whatever you think is best for you. (You might want to reboot your system after uninstalling.)
Paul Peelen linked the command line step to do the removal, but I'm going to quote ad verbatim from Apple's "About Xcode.pdf" since the link could disappear:
Uninstalling Xcode Developer Tools
To uninstall Xcode developer tools on the
boot volume along with the
directory, from a Terminal window
type:
$ sudo <Xcode>/Library/uninstall-devtools -mode=all
To remove the underlying developer content on the boot volume,
but leave the directory and
supporting files untouched, from a
Terminal window type:
$ sudo <Xcode>/Library/uninstall-devtools --mode=systemsupport
To just remove the UNIX development support on the
boot volume, but leave the
directory and supporting files
untouched, from a Terminal window
type:
$ sudo <Xcode>/Library/uninstall-devtools --mode=unixdev
Finally, to just uninstall the directory you
can simply drag it to the trash, or
from a Terminal window type:
$ sudo <Xcode>/Library/uninstall-devtools --mode=xcodedir
NOTE: The uninstaller that ships with previous versions of
the Xcode developer tools will not
clean everything off of your system
properly. You should use the one
installed with these Xcode developer
tools.
(Those are current at least as of "Xcode 3.2.3 for Mac OS X 10.6 and iPhone OS 4.0")
You can use appzapper, or just remove the stuff in /Developer/Applications (I believe).
Edit:
Asked my friend google, and this is what it came up with: http://macdevelopertips.com/xcode/how-to-uninstall-xcode.html
The new iOS SDK overwrites most of the old one (unless you change the installation directory), so it doesn't really double the disk space usage.