Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages
Flutter and app store releases

Xcode builds no dSYM for the app, so Crashlytics shows missing dSYMs

ErrorThe Crashlytics dashboard lists missing dSYMs for a build

Short answer

Crashlytics needs a dSYM from every build. Xcode only makes one when Debug Information Format is DWARF with dSYM File, and the Crashlytics Run Script must be the last build phase with every dSYM path listed as an Input File, or script sandboxing blocks it. Locate or upload dSYMs by hand when a build slipped through.

  • Applies to Xcode 26, Firebase iOS SDK (Crashlytics), Swift Package Manager
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Fix it fast

  1. 1Find out which cause you have

    List the dSYMs on this Mac with their UUIDs. If nothing comes back for your app, Xcode is not producing one.

    mdfind -name .dSYM | while read -r line; do dwarfdump -u "$line"; done
  2. 2Match what you see, then jump to its fix

    1. 1No MyApp.app.dSYM next to the built app, in Debug or ReleaseDebug Information Format is not DWARF with dSYM FileFix
    2. 2error: Info.plist Error Unable to process Info.plist, or the script cannot read a dSYM fileThe Run Script is blocked because its inputs are not listedFix
    3. 3The script runs, yet Crashlytics reports no symbols for the buildThe Crashlytics Run Script is not the last build phaseFix
    4. 4The Crashlytics dashboard asks you to upload dSYMs for a build already in the storeA released build has no dSYM uploadedFix

What does the error look like?

  • The Crashlytics dashboard lists missing dSYMs for a build
  • error: Info.plist Error Unable to process Info.plist

Cause 1 of 4

Debug Information Format is not DWARF with dSYM File

1Check

Debug builds keep symbols inside the binary by default, while release builds place them in a companion dSYM. Crashlytics asks for DWARF with dSYM File on all build types.

xcodebuild -showBuildSettings -project MyApp.xcodeproj -scheme MyApp | grep DEBUG_INFORMATION_FORMAT

2Fix

In the app target's Build Settings (All), search for debug information format and set DWARF with dSYM File for every configuration, then rebuild.

# Build Settings > Debug Information Format > DWARF with dSYM File (Debug and Release)

3Verify

The build now produces a .dSYM next to the .app.

mdfind -name MyApp.app.dSYM

Confirmed by firebase.google.com

Did this fix it?

Cause 2 of 4

The Run Script is blocked because its inputs are not listed

1Check

With User Script Sandboxing enabled, a script can only read files listed in Input Files, and Xcode 15 and later needs the complete paths. If ENABLE_USER_SCRIPT_SANDBOXING and ENABLE_DEBUG_DYLIB are both YES, the .debug.dylib path is needed too.

xcodebuild -showBuildSettings -project MyApp.xcodeproj -scheme MyApp | grep "ENABLE_USER_SCRIPT_SANDBOXING\|ENABLE_DEBUG_DYLIB"

2Fix

In Build Phases > Run Script, add these Input Files (add the last line only when both settings above are YES).

${DWARF_DSYM_FOLDER_PATH}/${DWARF_DSYM_FILE_NAME}
${DWARF_DSYM_FOLDER_PATH}/${DWARF_DSYM_FILE_NAME}/Contents/Resources/DWARF/${PRODUCT_NAME}
${DWARF_DSYM_FOLDER_PATH}/${DWARF_DSYM_FILE_NAME}/Contents/Info.plist
$(TARGET_BUILD_DIR)/$(UNLOCALIZED_RESOURCES_FOLDER_PATH)/GoogleService-Info.plist
$(TARGET_BUILD_DIR)/$(EXECUTABLE_PATH)
${DWARF_DSYM_FOLDER_PATH}/${DWARF_DSYM_FILE_NAME}/Contents/Resources/DWARF/${PRODUCT_NAME}.debug.dylib

3Verify

Archive again and check that the Run Script step finishes without the Info.plist error.

xcodebuild archive -project MyApp.xcodeproj -scheme MyApp -archivePath /tmp/MyApp.xcarchive

Confirmed by firebase.google.com

Did this fix it?

Cause 3 of 4

The Crashlytics Run Script is not the last build phase

1Check

The script must be the project's last build phase, otherwise Crashlytics cannot process the dSYMs properly. With Swift Package Manager the script path is the Crashlytics run file in the firebase-ios-sdk checkout.

grep -n "Crashlytics/run" MyApp.xcodeproj/project.pbxproj

2Fix

Drag the Run Script phase to the bottom of Build Phases. The script line for Swift Package Manager is shown below.

"${BUILD_DIR%/Build/*}/SourcePackages/checkouts/firebase-ios-sdk/Crashlytics/run"

3Verify

Archive and run again, and read the build log for the script step.

xcodebuild archive -project MyApp.xcodeproj -scheme MyApp -archivePath /tmp/MyApp.xcarchive

Confirmed by firebase.google.com

Did this fix it?

Cause 4 of 4

A released build has no dSYM uploaded

1Check

The dSYM must match the binary by UUID. Open the archive for that release in Xcode's Organizer, Control-click it, choose Show Package Contents and look in the dSYMs folder.

dwarfdump -u /tmp/MyApp.xcarchive/dSYMs/MyApp.app.dSYM

2Fix

Upload the dSYMs with the upload-symbols tool, or zip them and drop them into the dSYMs tab of the Crashlytics dashboard. Run upload-symbols --help for its options.

/PATH/TO/PODS/DIRECTORY/FirebaseCrashlytics/upload-symbols -gsp /PATH/TO/GoogleService-Info.plist -p ios /PATH/TO/dSYMs

3Verify

The dashboard no longer lists missing dSYMs for that build.

dwarfdump -u /PATH/TO/dSYMs/MyApp.app.dSYM

Confirmed by firebase.google.com

Did this fix it?

How do I stop it coming back?

  • Keep the Xcode archive of every release you ship; without it you may not be able to diagnose a crash.
  • Check Debug Information Format in both Debug and Release when you add a target or extension.
  • Keep the Crashlytics Run Script last whenever you add a new build phase.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.

Which stack is behind this page?

Projects of mine built on the same technologies:

Related fixes

Mobile apps

InstanceID token() no longer works in a Swift Firebase app

Instance ID calls fail to compile after upgrading Firebase to 8.0.0 or later

Firebase removed the Instance ID dependency from Messaging in 8.0.0, so InstanceID.instanceID() calls no longer belong in a current app.

3 causes, each with a fix

Next step

Want this handled for good?

I look after servers, apps and releases end to end. Tell me what keeps breaking.