Why this happens
When you run Product > Archive to distribute an app to TestFlight or the App Store, Xcode packages the compiled binary, Info.plist, and debug symbol (dSYM) files into an .xcarchive bundle. Developers often go looking for these bundles weeks later to symbolicate crash logs, only to come up empty in Finder and Spotlight.
Two things hide .xcarchive files from normal searches. First, Xcode stores archives inside your user ~/Library folder, which macOS hides in Finder and excludes from default Spotlight results. Second, it is easy to mistype the file extension as .xarchive instead of .xcarchive, causing even targeted searches to return zero matches.
If you open the default ~/Library/Developer/Xcode/Archives directory and find it empty despite shipping past versions, your builds were not deleted by Xcode’s Product > Clean Build Folder command. Instead, Xcode is either configured to save archives to a custom path, your build was generated from the command line with a custom -archivePath, or a macOS storage cleanup tool purged your developer cache.
How to fix it
1. Reveal the archive from Xcode Organizer
The fastest way to find any existing archive on your Mac—regardless of where it is stored on disk—is through Xcode’s built-in Organizer window.
- Open Xcode and choose
Window > Organizerfrom the menu bar. - Select Archives in the left sidebar (or at the top of the window in older Xcode releases).
- Use the app selector menu to choose the project you want to inspect.
- Right-click (or Control-click) the specific version and build date in the list.
- Click Show in Finder.
Finder will open the exact date-stamped folder containing your .xcarchive bundle. Because an .xcarchive is a macOS package directory rather than a flat file, right-click the .xcarchive in Finder and choose Show Package Contents to access its internal dSYMs, Products, and BCSymbolMaps folders for crash log symbolication.
2. Open the hidden Archives directory directly
If you do not want to launch Xcode, you can jump straight to the default archive directory in Finder or Terminal. Xcode groups archives inside subdirectories named after the build date (YYYY-MM-DD).
In Finder:
- Press
Shift + Command + Gto open the Go to Folder prompt. - Paste the following path and press
Return:
~/Library/Developer/Xcode/Archives
- Open the date folder matching when you submitted your app to find
<App Name> <Date, Time>.xcarchive.
In Terminal, you can list all stored archives sorted by modification time:
ls -lt ~/Library/Developer/Xcode/Archives/*/*.xcarchive
3. Check Xcode Settings for a custom Archives location
If ~/Library/Developer/Xcode/Archives is empty or missing recent builds, check whether Xcode is writing archives to an alternate disk or folder.
- In the menu bar, open
Xcode > Settings...(orXcode > Preferences...on older macOS versions). - Select the Locations tab.
- Check the path listed next to Archives.
- Click the small arrow icon next to the path to reveal that folder directly in Finder.
Also click the Advanced… button in the same Locations tab if your team uses custom build locations relative to the workspace or build directory.
4. Search your entire Mac using Terminal instead of Spotlight
Standard Spotlight queries skip system and library folders, so typing .xcarchive into Spotlight usually returns nothing. If you built an archive using xcodebuild archive -archivePath, moved folders between drives, or built under another user profile, search the filesystem directly from Terminal.
Run find across your home directory (and double-check that you spell .xcarchive with two cs):
find ~ -type d -name "*.xcarchive" 2>/dev/null
If you store projects or build artifacts on external volumes or shared directories outside your home folder, broaden the search to /Volumes or /:
find /Volumes -type d -name "*.xcarchive" 2>/dev/null
The -type d flag speeds up the scan because .xcarchive bundles are directories, and 2>/dev/null hides permission warnings for protected system folders.
5. Fix new archives not appearing after a build
If running Product > Archive finishes with Build Succeeded yet nothing appears in the Organizer or the Archives folder, check two project settings:
Verify the Scheme’s Archive settings:
- Go to
Product > Scheme > Edit Scheme.... - Select Archive in the left column.
- Make sure Reveal Archive in Organizer is checked.
Verify the Skip Install build setting:
If your main app target accidentally has Skip Install set to Yes, Xcode generates an empty archive without an installable product, which prevents it from showing up under your app’s section in Organizer.
- Select your project in the Project Navigator.
- Select your main App Target and open Build Settings.
- Search for
Skip Install(SKIP_INSTALL) and set it to No. - Select any static library or embedded framework targets in your project and verify their
Skip Installsetting is Yes (otherwise Xcode bundles multiple top-level products and classifies the output as a “Generic Xcode Archive” that cannot be uploaded normally).
How to prevent it
- Archive your release
.xcarchivebundles externally: Copy the.xcarchivebundle (or at least itsdSYMsfolder) to secure cloud or team storage after every App Store release so machine migrations never leave you without debug symbols. - Watch out for macOS Storage cleanup: Opening
System Settings > General > Storage > Developerlets you delete “Xcode Archives” alongside project caches. Uncheck Xcode Archives when freeing up disk space, and exclude~/Library/Developer/Xcode/Archivesfrom third-party Mac cleaner apps. - Standardize CI archive paths: When archiving via Fastlane or
xcodebuildon a build server, explicitly pass-archivePathand upload the resulting.xcarchiveor.dSYM.zipas a build artifact. - Verify scheme settings in source control: Keep shared schemes checked into Git with Reveal Archive in Organizer enabled so local release builds always register in Xcode.
FAQ
Does Product > Clean Build Folder delete my Xcode archives?
No. Running Product > Clean Build Folder (Shift + Command + K) only clears intermediate build artifacts inside your project’s DerivedData directory. It never touches ~/Library/Developer/Xcode/Archives.
Where are the dSYM files located inside an .xcarchive?
Right-click the .xcarchive bundle in Finder and choose Show Package Contents. Open the dSYMs folder inside to find <YourApp>.app.dSYM along with symbol bundles for any dynamically linked frameworks.
How can I symbolicate crash logs if my .xcarchive was permanently deleted?
If you uploaded your app to App Store Connect or TestFlight with symbols included, Xcode and App Store Connect can still symbolicate crashes reported through Apple’s crash reporting system. You can also check App Store Connect under your build’s Build Metadata page to see if downloadable dSYM files are available for that build.
Parts of this guide are adapted from content licensed under CC BY-SA 4.0; this article is shared under the same license.
