Xcode Device Logs
Connected iPhone, iPad, Apple Watch, and Apple TV hardware writes crash reports, jetsam logs, panic logs, and other diagnostic bundles into Xcode's iOS Device Logs folder so Xcode can symbolicate them and show them in the Devices and Simulators window. These files accumulate across every attached device and app build, often keeping old .crash, .ips, and related diagnostic artifacts long after they are useful. Kudu removes the stored device log archives and crash report copies from this Xcode cache location without touching projects, signing assets, app source, device backups, accounts, or settings.
Why clean Xcode Device Logs?
- Hundreds or thousands of retained .crash and .ips reports from repeated test runs make the iOS Device Logs folder grow into multiple gigabytes, and you notice Xcode consuming unexpected disk space on the system drive
- Old crash logs from previous app versions clutter the Devices and Simulators log list, making it harder to spot the current failure you are actually debugging
- Stale symbolicated copies tied to older dSYMs can leave crash details looking inconsistent with the latest build, so stack traces appear confusing or no longer match current source lines
- A very large device log archive slows browsing and searching in Xcode's device log viewer, which shows up as lag when opening logs or scrolling long diagnostic histories
- Retained logs from many physical devices keep obsolete device names, bundle IDs, and crash sessions around, so developers waste time triaging reports that are no longer relevant
- After a bug is fixed, keeping historical panic, jetsam, and watchdog reports in the same cache can make new incidents look like repeats, and the visible symptom is duplicate-looking crashes mixed across old and new builds
Cache paths Kudu targets
macOS
~/Library/Developer/Xcode/iOS Device Logs |
Common questions about Xcode Device Logs
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.