XcodesOrg / XcodesOrg/XcodesApp

Add Storage Management Tools for Xcode Junk

Open
#781 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Swift
Stars
8.6k
Forks
387
Avg merge
6d 7h
Merged PRs (30d)
3

Description

Tell us how we can improve Xcodes
Xcode installations accumulate a large amount of residual files over time—Derived Data, old iOS/watchOS/tvOS simulators, device support files, caches, and other build artifacts. These can easily grow to tens of gigabytes and are difficult to manage manually. Adding built-in storage management tools would make Xcodes a far more complete and helpful utility for developers.

Is your feature request related to a problem? Please describe.
Yes. Xcode’s leftover files take a huge portion of disk space, especially for developers who frequently install multiple Xcode versions or test across many simulators. Cleaning these folders manually or via scripts is inconvenient, error-prone, and not beginner-friendly. There is currently no unified place in Xcodes to view and manage storage usage across all installed components.

What would you like to see? How would you like it to work?
I would love Xcodes to include a Storage Management section that:
• Automatically detects large Xcode-related directories (Derived Data, Archives, Logs, Device Support, etc.)
• Lists installed simulators with their sizes and allows quick removal of unused ones
• Shows total storage usage per Xcode installation
• Offers one-click cleanup actions (e.g., “Clear Derived Data”, “Remove old Simulators”, “Clean Caches”)
• Optionally provides recommendations for safe cleanup based on last-used timestamps

This would make Xcodes not only a great installer manager but also the central tool for maintaining a clean and optimized Xcode environment.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by surveying the XcodesApp storage-related entry points and existing handling of Xcode installations, simulators, caches, archives, logs, and device support files. Done would require an agreed Storage Management section that reports usage and provides safe cleanup actions, including simulator removal and optional recommendations.

Written by the indexing model from the issue text.

Assessment

Tech stack
macos, swift
Domain
desktop, tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.