Clean DYLD caches (~/Library/Developer/CoreSimulator/Caches/dyld)

[lathiat]

I have noticed the following directory with data that also doesn't seem cleaned up. I used the visionOS simulator a couple times just for fun, last launch months ago. Even after removing the runtimes these DYLD caches are not removed by Xcode (no surprise) but DevCleaner also doesn't seem to detect them currently:
5.6G ~/Library/Developer/CoreSimulator/Caches
5.6G ~/Library/Developer/CoreSimulator/Caches/dyld
5.6G ~/Library/Developer/CoreSimulator/Caches/dyld/23F79
2.6G ~/Library/Developer/CoreSimulator/Caches/dyld/23F79/com.apple.CoreSimulator.SimRuntime.xrOS-1-0.21N5165g
2.6G ~/Library/Developer/CoreSimulator/Caches/dyld/23F79/com.apple.CoreSimulator.SimRuntime.xrOS-1-0.21N5165g/dyld_sim_shared_cache_arm64
628K ~/Library/Developer/CoreSimulator/Caches/dyld/23F79/com.apple.CoreSimulator.SimRuntime.xrOS-1-0.21N5165g/dyld_sim_shared_cache_arm64.map
4.0K ~/Library/Developer/CoreSimulator/Caches/dyld/23F79/com.apple.CoreSimulator.SimRuntime.xrOS-1-0.21N5165g/xprotect_scan_version.txt
3.0G ~/Library/Developer/CoreSimulator/Caches/dyld/23F79/com.apple.CoreSimulator.SimRuntime.xrOS-1-1.21O209
1.8G ~/Library/Developer/CoreSimulator/Caches/dyld/23F79/com.apple.CoreSimulator.SimRuntime.xrOS-1-1.21O209/dyld_sim_shared_cache_arm64
1.2G ~/Library/Developer/CoreSimulator/Caches/dyld/23F79/com.apple.CoreSimulator.SimRuntime.xrOS-1-1.21O209/dyld_sim_shared_cache_arm64.01.dylddata
668K ~/Library/Developer/CoreSimulator/Caches/dyld/23F79/com.apple.CoreSimulator.SimRuntime.xrOS-1-1.21O209/dyld_sim_shared_cache_arm64.map
4.0K ~/Library/Developer/CoreSimulator/Caches/dyld/23F79/com.apple.CoreSimulator.SimRuntime.xrOS-1-1.21O209/xprotect_scan_version.txt

[vashpan]

I considered that. But those caches will be recreated in the moment you boot simulator (or use Previews) again.

They're refreshed every time you boot simulator, and from what I can see - this cache is actually removed if you don't have specific runtime installed (unless I'm wrong - help from you guys here would be nice!)

The only case that would be worth clean - is when someone is NOT using simulator at any times - macOS developers, guys who are using only devices. Please consider though that any kind of "preview" in Xcode is using Simulator.

I'll keep it open for a while, I'm interested what you guys think?

[markst]

Seems I have CoreSimulator cache for simulator I no longer have installed:

[vashpan]

Hmm, are those "dyld" caches present in modern Xcodes? 🤔 It seems it's gone from my installation (I haven't deleted it myself) - could anyone confirm with Xcode 16 & 26? CoreSimulator/Caches/dyld folder. Also check their modification date if you use Xcode from a long time 😉

Maybe they moved somewhere else, but maybe they're no longer needed? Interesting...

[markst]

Isn’t the point of dev cleaner to help cleanup orphaned files or directories?

…

On Sun, 15 Jun 2025 at 7:05 pm, Konrad Kołakowski ***@***.***> wrote: *vashpan* left a comment (vashpan/xcode-dev-cleaner#48) <#48 (comment)> Hmm, are those "dyld" caches present in modern Xcodes? 🤔 It seems it's gone from my installation (I haven't deleted it myself) - could anyone confirm with Xcode 16 & 26? CoreSimulator/Caches/dyld folder. Also check their modification date if you use Xcode from a long time 😉 Maybe they moved somewhere else, but maybe they're no longer needed? Interesting... — Reply to this email directly, view it on GitHub <#48 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AACC7DVFZGYAOEW4EXANNND3DUZOJAVCNFSM6AAAAABIE6MZSWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDSNZTGYYDKNBSGI> . You are receiving this because you commented.Message ID: ***@***.***>

[vashpan]

Sure, my point was - investigate if that this cache have been cleared by Xcode itself at some point. My idea of DevCleaner is that it won't do redundant stuff for Xcode.

But of course sometimes it would be beneficial to have all that cleaning stuff in one place. For example in this year Xcode, we have this compilation cache - with a possibility to even set limit for it in Settings! Great stuff! I would love more from Xcode in this regard - so I'm thinking if DevCleaner should also have option to clear it separately? 🤔