What Klyr’s Xcode view inspects
The dedicated scanner checks known locations under your Library rather than sweeping arbitrary project folders. Current categories include:
- DerivedData for build products, indexes and intermediate output.
- Archives containing archived builds and associated distribution assets.
- iOS DeviceSupport used when working with particular device and OS versions.
- CoreSimulator devices and caches created by installed simulator runtimes and test devices.
- Xcode caches stored under the user Library cache directory.
Rebuildable does not mean consequence-free
Close active Xcode builds and simulators before changing their data. Keep source repositories, signing assets, release archives and irreplaceable test state backed up.
A safer review workflow
- Inspect the category, path, size and modification date.
- Confirm whether an active project, release or connected device still needs it.
- Select only understood items.
- Move the selection to Trash through Klyr’s normal removal flow.
- Open Xcode and verify the affected workflow before emptying Trash.
Klyr applies its path, whitelist and sensitive-location checks again when an action occurs; scan-time classification is not the only guard.
Xcode storage questions
Is DerivedData safe to remove?
It is generally rebuildable, but removing it discards caches and forces builds and indexing to regenerate data.
Should I remove old Xcode Archives?
Only after confirming you no longer need the archived build, debug symbols, signing context or distribution record.
Does Klyr target source code?
The dedicated Xcode view targets known developer-data locations, not arbitrary project source folders. You still review every selected path.