dyld_shared_cache_extract_dylibs failed

Developer Tools & Services Xcode Xcode

Created Sep ’18

Replies 21

Boosts 1

Views 42k

Participants 19

I have installed the latest version of xcode on my imac (Version 10.0 (10A255)) and can compile and run my app in the simulator (iphone6, IOS12).

When I connect my iPhone (6, ios12) to the imac and try to run the app on my iPhone it compiles well but then I get the error:

dyld_shared_cache_extract_dylibs failed

With the previous verstion of xcode i did not had this problem and could run my apps on the iphone.

I cannot find the reason for this.. Who can help me?

Thanks,

Addy

Boost

rabia.dastgir@nxb.com.pk OP

Apr ’20

Thank you!! This solved my problem

kiyookasan OP

May ’20

Worked for me on: 10.15 Catalina, Xcode 10.3 (with 13.4 device support added to bundle) and iOS 13.4.1

puzzlekings OP

Jun ’20

Awesome - thanks so much for this.

Saved me having to update to Catalina and losing MSOffice 2011 support 🙂

BTW if it helps anyone: to create an empty file, navigate to the directory in terminal and type in the following

touch .processed_dyld_shared_cache_arm64e

imfaker OP

Jul ’20

My solution： paste another correct /Users/macbook/Library/Developer/Xcode/iOS DeviceSupport/{version} contents to version which error .
it is success.

caramelita OP

Jan ’24

fallout1998 's solution worked for me but some tips:

you can start by removing the "iOS DeviceSupport" folder; it will recreate that automatically recreate the folder with only the iOS version for the device you're working with, which helps to narrow the version now
had to mkdir the entire path starting from the Systems folder in my case, but it worked

xxt07d OP

M1 mac minit, macOs Sonoma 14.0, xcode 15.0

Currently there are different kind of folders inside of ~/Library/Developer/Xcode/iOS DeviceSupport/

they are like "iPad13,18 18.1 (22B83)"

You can find the corresponding folder in Window > Devices and Simulators. As you select your device, you can see the string from the parantheses.

For me deleting this specific folder solved the issue.

Thanks @fallout1988 and @caramelita for your answers.