System
Xcode iOS Device Support
Xcode stores per-iOS-version DeviceSupport bundles under iOS DeviceSupport so it can symbolicate crash logs, mount the correct developer disk image on attached iPhones and iPads, and prepare devices for debugging. These folders contain platform symbols, dyld shared cache support files, DeveloperDiskImage files, and related metadata that accumulate as you connect devices running different iOS builds. Kudu removes outdated DeviceSupport bundles to recover disk space without touching your projects, signing identities, simulator data, accounts, or device backups.
Why clean Xcode iOS Device Support?
- Old DeviceSupport folders for iOS builds you no longer test can consume many gigabytes, and you notice Xcode taking an unexpectedly large share of System Data or developer storage
- Stale support files from older iOS point releases can make Xcode pause at Preparing debugger support or Processing symbol files when you reconnect a device
- After upgrading Xcode, cached DeviceSupport content for unsupported builds may remain on disk even though the current Xcode cannot use it, leaving wasted space with no benefit
- If symbol files for many past devices accumulate, crash log symbolication lookups become harder to manage and you may see duplicate or obsolete iOS build folders in Developer storage
- Removing unused DeveloperDiskImage and symbol bundles can clear out support data for devices you no longer own, reducing clutter when Xcode scans available device support versions
- Corrupted DeviceSupport contents can lead to repeated prompts to prepare a device for development, slow attachment, or failure to start a debug session until Xcode downloads or rebuilds fresh support files
What gets cleaned
Cache paths Kudu targets
macOS
~/Library/Developer/Xcode/iOS DeviceSupport |
Frequently asked
Common questions about Xcode iOS Device Support
Free & open source
Download Kudu and reclaim your disk space.
Available on Windows, macOS, and Linux. No account required, no feature gates, no telemetry without consent. All cleaning targets are open source and community-auditable.