System

Xcode watchOS Device Support

Xcode stores watchOS Device Support files for each connected Apple Watch and watchOS build so it can mount the proper developer disk image, read symbols, and collect logs during debugging. These folders accumulate device-specific support bundles, symbol files, and versioned developer resources that are only needed while working with that exact watchOS release. Kudu removes obsolete watchOS DeviceSupport directories without touching projects, source code, signing assets, simulators, accounts, or preferences.

Why it matters

Why clean Xcode watchOS Device Support?

  • Old watchOS support bundles pile up after testing multiple OS versions, and the first thing you notice is Xcode consuming tens of gigabytes in Library storage for devices you no longer own or target
  • A stale Device Support folder for a previous watchOS build can stop Xcode from matching the connected Apple Watch correctly, showing repeated preparing debugger messages or failed symbol loading in the debug console
  • After upgrading Xcode, leftover support files from an older toolchain can conflict with the newer developer disk image workflow, leading to attach failures or missing device logs until Xcode rebuilds what it needs
  • Corrupted symbol content inside an old Device Support directory can produce incomplete backtraces and hex-only crash logs, making watchOS debugging noticeably less useful
  • Keeping support files for every beta and point release slows manual cleanup and makes it harder to tell which watchOS versions are still relevant when the Devices window shows repeated processing for old builds
  • Unused device support data remains on disk even after the watch is unpaired or replaced, so you keep losing free space with no change to projects, app archives, or personal data
What gets cleaned

Cache paths Kudu targets

macOS

~/Library/Developer/Xcode/watchOS DeviceSupport
Frequently asked

Common questions about Xcode watchOS 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.