iOS dSYM upload to crash reporter failed: "dSYM not found" error after archive

TL;DR

Locate or regenerate the dSYM for the exact build, making sure the archive step actually produced one: check the archives dSYMs folder, confirm debug information format is set to DWARF with dSYM for the release configuration, and match the dSYM UUID to the app binary UUID the crash reporter expects. Upload scripts fail when they glob a stale path or when a framework dSYM is missing even though the app dSYM exists.

dSYM not found - iOS upload to crash reporter after archive

Use this when

• The crash symbolication upload step fails with dSYM not found after archiving.
• Release builds were switched to a configuration without dSYM generation.
• CI archives on one machine and uploads symbols from another.

Not for this skill when

• The crash reporter rejects the dSYM as mismatched. That is a UUID problem, a step beyond existence.
• You use App Store Connect crash reports only. Those need no manual dSYM upload for your own code.

Steps

1. Open the .xcarchive from the failed build and list its dSYMs folder contents. Verify: the present and missing dSYMs are listed by name
2. Compare the app binary UUID in the archive with the dSYM UUID using the dwarfdump uuid command on both. Verify: UUIDs match for the pairs that exist, confirming which are truly missing
3. Check the release build settings for debug information format and set it to DWARF with dSYM file for app and framework targets. Verify: the setting is correct on every target that ships code
4. Fix the upload script path to read from the actual archive location or the CI steps exported archive variable, not a hardcoded developer path. Verify: the script resolves the archive produced by this build
5. Re-archive and run the symbol upload step. Verify: the crash reporter accepts the dSYMs and lists them for this build version
6. Trigger or wait for a test crash and confirm it symbolicates in the reporter dashboard. Verify: the test crash shows file and function names instead of addresses
7. Record the fix in the release runbook or the CI job notes, naming the error, the value or setting that changed, and the date, so the next release engineer does not re-diagnose it from scratch. Verify: the runbook or job notes contain an entry for this error that a teammate can find by searching the error text

Why it happens

dSYMs are separate files generated at archive time, one per binary, keyed by UUID. They go missing when a configuration generates plain DWARF, when bitcode-era or distribution flows strip them, or when CI moves the archive before the upload step looks for it. Without the exact builds dSYM, crash reports for that build stay unsymbolicated forever; they cannot be recreated later.

In practice this failure is rarely a one-off. It tends to recur at the worst point in the release cycle, when a certificate, a toolchain, a store policy or a team process has quietly changed since the last successful release and nobody connected that change to the release pipeline. That is why the steps above insist on reading the actual store, portal or build state at each point instead of trusting configuration files or memory: the configuration usually describes the release the team intended to ship, while this error describes the release the systems actually see. Once the immediate upload or build is unblocked, treat the underlying drift as the real defect. Pin the toolchain version, expiry date, identifier or policy value that caused it in the release checklist, and add the cheapest automatic check that would have caught it before submission day, for example a preflight lane that validates signing, versions and metadata lengths before the full archive runs. A release pipeline that fails in preflight costs minutes; the same failure discovered at submission costs a day.

Variants and edge cases

dSYM not found crash reporter upload fix

Upload phrasing; check archive contents and UUIDs. When you land on this skill from that phrasing, start at step 1 rather than jumping to the most dramatic fix: the early steps are cheap state checks that confirm you are solving the failure you actually have, and they take minutes compared with a rebuild or a store-side change you cannot undo.

missing dSYM release configuration Xcode setting

Settings phrasing; enable DWARF with dSYM for release. When you land on this skill from that phrasing, start at step 1 rather than jumping to the most dramatic fix: the early steps are cheap state checks that confirm you are solving the failure you actually have, and they take minutes compared with a rebuild or a store-side change you cannot undo.

Edge case: framework dSYMs

Crash reporters need framework dSYMs too. A present app dSYM with missing framework dSYMs still fails strict upload scripts. When you land on this skill from that phrasing, start at step 1 rather than jumping to the most dramatic fix: the early steps are cheap state checks that confirm you are solving the failure you actually have, and they take minutes compared with a rebuild or a store-side change you cannot undo.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstxSzjAKPvUgPb-KhaU1Z7Q