When plugging my iPhone in and starting the Xcode organizer, a yellow circle next to the device show me that "This device is busy or otherwise unusable by Xcode." The Organizer is then processing two files (the second one takes quite a while to finish) and afterwards I get the error message as shown in the screenshot.
I tried to google for that error message ("dyld_shared_cache_extract_dylibs failed") but could not find anything useful. I tried a couple things: repair permissions of my harddrive and run "sudo update_dyld_shared_cache -force". Still getting the error message.
I am running iOS 4.2.1 and Xcode 3.2.5. I have not updated Xcode after updating from 4.2 to 4.2.1 (I think).
The Xcode console is empty but the regular OS X console shows this:
1/22/11 10:56:19 PM Xcode[4187] Started symbol copying process
1/22/11 10:56:19 PM Xcode[4187] Skipped copying file 1 of 2 ("processed" sentinal found)
1/22/11 10:56:19 PM Xcode[4187] Skipped processing file 1 of 2 ("processed" sentinal found)
1/22/11 10:56:19 PM Xcode[4187] Skipped copying file 2 of 2 ("copied" sentinal found)
1/22/11 10:56:19 PM Xcode[4187] Started processing file 2 of 2
1/22/11 10:56:20 PM [0x0-0x4d04d].com.apple.Xcode[4187] arch already exists in fat dylib
1/22/11 10:56:20 PM [0x0-0x4d04d].com.apple.Xcode[4187] arch already exists in fat dylib
1/22/11 10:56:20 PM [0x0-0x4d04d].com.apple.Xcode[4187] arch already exists in fat dylib
1/22/11 10:56:21 PM [0x0-0x4d04d].com.apple.Xcode[4187] arch already exists in fat dylib
1/22/11 10:56:21 PM [0x0-0x4d04d].com.apple.Xcode[4187] arch already exists in fat dylib
1/22/11 10:56:22 PM [0x0-0x4d04d].com.apple.Xcode[4187] arch already exists in fat dylib
1/22/11 10:56:22 PM [0x0-0x4d04d].com.apple.Xcode[4187] arch already exists in fat dylib
1/22/11 10:56:22 PM [0x0-0x4d04d].com.apple.Xcode[4187] arch already exists in fat dylib
1/22/11 10:56:23 PM [0x0-0x4d04d].com.apple.Xcode[4187] arch already exists in fat dylib
1/22/11 10:56:23 PM [0x0-0x4d04d].com.apple.Xcode[4187] arch already exists in fat dylib
1/22/11 10:56:23 PM [0x0-0x4d04d].com.apple.Xcode[4187] arch already exists in fat dylib
This error message is then repeated constantly.
Target path to directory has been changed since Xcode 3.
If you have same issue in Xcode 8 then follow next steps:
~/Library/Developer/Xcode/iOS DeviceSupport/
Source: Apple Developer Forum
After all this time I wanna contribute with one more possible solution for this problem...
Unpair Device
One more thing: I changed the version inside /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/DeviceSupport from 10.3 to 10.3.3 - that is "exactly" version on my device, so, observe this too.
Believe in me guys... I bought 2 cables, investigate all links in google, bing, yahoo, books, forums... everything and nothing solves... until this.
For me the approach that worked was the one mentioned here which is:
~/Library/Developer/Xcode/iOS DeviceSupport/
For Xcode 10.1, iOS 13.3 Below helped me.
Copied from https://forums.developer.apple.com/thread/108917
go to ~/Library/Developer/Xcode/iOS DeviceSupport/13.2/Symbols/System/Library/Caches/com.apple.dyld
create empty file if it is not there - .processed_dyld_shared_cache_arm64e
restart xcode and enjoy!
With the help of somebody at the Apple Developer Forums I was able to fix the problem by removing the "/Developer/Platforms/iPhoneOS.platform/DeviceSupport/4.2.1 (8C148)" folder. Xcode then re-added the symbols automatically and the error disappeared. For more information see this thread.
For what it's worth: I encountered this problem when I was out of disk space. It seems that XCode was the first application to 'notice' by throwing this error. After freeing up some disk space everything worked fine again.
This happened to me when disk space was very low on the mac
for xCode 10.1 on High Sierra, you need to create an empty file named :
.processed_dyld_shared_cache_arm64e
and paste it to:
/Users/{you}/Library/Developer/Xcode/iOS DeviceSupport/{your device version} arm64e/Symbols/System/Library/Caches/com.apple.dyld
make sure that the folder is empty. for me it took couple of time trying and waiting and removing device to get it to work.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With