[Crashlytics] Xcode16 beta build with debug mode missing dSYM

[flexund]

Description

When building application with Debug mode on Xcode16, dSYM fails to upload to Crashlytics.

This is related to #13202

Workaround is to disable Debug Dylib Support in target Build settings. But this causes SwiftUI previews to not work.

Reproducing the issue

• Set ENABLE_DEBUG_DYLIB=YES for build options
• Build application for debug mode in Xcode 16

Firebase SDK Version

11.1.0

Xcode Version

16.0 Beta 6

Installation Method

Swift Package Manager

Firebase Product(s)

Crashlytics

Targeted Platforms

iOS

Relevant Log Output

No response

If using Swift Package Manager, the project's Package.resolved

Expand Package.resolved snippet

Replace this line with the contents of your Package.resolved.

If using CocoaPods, the project's Podfile.lock

Expand Podfile.lock snippet

Replace this line with the contents of your Podfile.lock!

[google-oss-bot]

I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight.

[Osein]

I solved this by setting ENABLE_DEBUG_DYLIB to false. Crashlytics upload dsym successfully but it makes preview go kaput

[themiswang]

Seems like Apple changed their dSYM content a bit again, will work on a fix. Meanwhile another work around is uploading the dSYM through web uploader.

[4eleven7]

Is there any update on this?

[jerald-dexcom]

I would like to know if there is any update to this as well. ENABLE_DEBUG_DYLIB to false is the only solution for me for Crashlytics to work.

[benfrearson]

As above, ENABLE_DEBUG_DYLIB is the only solution for me too. Manually uploading dsyms is not particularly feasible when rapid prototyping and using CI/CD.

Would be good to know if there's a fix on the way!

[4eleven7]

EDIT: Nope, still getting missing dSYM emails endlessly

I've moved from using the SPM recommended script
# "${BUILD_DIR%/Build/*}/SourcePackages/checkouts/firebase-ios-sdk/Crashlytics/run"

To using this custom script, which seems to be uploading dSYMs correctly, however I'm no script or Firebase expert, just a big dummy that has deadlines, so this might not solve all issues. All I know is my team and I no longer receive 30 emails a day about missing dSYM files.
You'll have to update paths and cater it to your project + use case etc.

UPLOAD_SYMBOLS_PATH="${BUILD_DIR%/Build/*}/SourcePackages/checkouts/firebase-ios-sdk/Crashlytics/upload-symbols"

if [ "${TARGET_NAME}" == "Staging" ]; then
    GOOGLE_SERVICE_INFO_PLIST="${SOURCE_ROOT}/${PROJECT}/Staging/GoogleService-Info.plist"
else
    GOOGLE_SERVICE_INFO_PLIST="${SOURCE_ROOT}/${PROJECT}/GoogleService-Info.plist"
fi

# Verify we found it
if [ ! -f "${GOOGLE_SERVICE_INFO_PLIST}" ]; then
    echo "Error: GoogleService-Info.plist not found at path ${GOOGLE_SERVICE_INFO_PLIST}"
    exit 1
fi

"${UPLOAD_SYMBOLS_PATH}" -gsp "${GOOGLE_SERVICE_INFO_PLIST}" -p ios "${DWARF_DSYM_FOLDER_PATH}/${DWARF_DSYM_FILE_NAME}"

echo "dSYM upload completed."

I've also set Previews to use legacy mode (Editor > Canvas > Enable legacy preview execution)

[themiswang]

Hey folks,

Thank you for reaching out, I am working on the fix now. This fix need a refactor work in script so we need to do a thoroughly regression test which might take more time. Tl;dr the fix need to make upload-symbols to support upload multiple DWARF contents within the same dSYM bundle which currently upload-symbols does not support. We likely gonna miss the code freeze for the upcoming release version. But as soon as we finished testing and I'll post the artifact in the issue as a workaround before we having official release.

[vhartikainen]

• Set ENABLE_DEBUG_DYLIB=YES for build options
• Build application for debug mode in Xcode 16

This seems to do the trick for me too.

• Xcode Version 16.0 (16A242d)

@themiswang Processing of new dSYMs seem to take rather long on Google's side - after upload complete, it takes 5-10minutes before the events start to appear. Is this normal?

This makes fast iteration and testing really hard and prone to make wrong conclusions what works and what not.

[jerald-dexcom]

Thank you @themiswang ,
Do you have any ETA for the release that will have this fix?