Xcode won't create dSYM files for FirebaseAnalytics

Question

I’m getting dSYM warnings for FirebaseAnalytics when validating my app in Xcode:

Upload Symbols Failed


The archive did not include a dSYM for the FirebaseAnalytics.framework with the UUIDs > [D080D817-CA37-3B97-8A51-421A372C12DB]. Ensure that the archive's dSYM folder includes > a DWARF file for FirebaseAnalytics.framework with the expected UUIDs.



I've looked at the package contents of my app archive and there are no dSYM files related to Firebase in the dSYMs folder. I do have one for my app though.

Current situation:

1. I’m using Firebase v10.29.0 (installed via Swift Package Manager)
2. Analytics is enabled for my app in the Firebase Console
3. Events and Crashlytics log messages are being logged are visible in the Firebase Console
4. My local GoogleService-Info.plist has IS_ANALYTICS_ENABLED set to ‘No’ (but I’ve tried changing it to ‘Yes’ which doesn’t fix the problem)
5. I’ve ensured "Debug Information Format" is set to "DWARF with dSYM File" for both Debug and Release configurations
6. The Run Script build phase is running this: "${BUILD_DIR%/Build/*}/SourcePackages/checkouts/firebase-ios-sdk/Crashlytics/run"
7. I have all the correct Input Files paths in the script
8. I’ve cleaned the project and rebuilt multiple times

I’m out of ideas. What else can I try?

Thanks

Ravel

Possibly related to https://mcmap.net/q/1916028/-is-there-a-way-to-generate-dsyms-for-swift-packages-when-xcode-archiving/1271826. – Trews

I've got a dozen packages in my app, and since shifting to SPM (from Cocoapods), I have only three frameworks generating this error, and they are all Firebase/Google (FirebaseAnalytics, GoogleAppMeasurement, and GoogleAppMeasurementIdentitySupport). None of my other packages generate this error. I wonder if there is some issue in how they generated their binaryTargets? Maybe this is a question we have to direct to them? – Trews

FWIW, I’ve submitted a request there and I will let you know if I hear anything. – Trews

@Trews I'm facing the same issue, did you get any response yet ? – Sergias

No response, but it looks like they're working on it. – Trews

Answer 1

Might be a Xcode 16 issue caused by a change in how they process dSYMs. Discussion here: https://github.com/firebase/firebase-ios-sdk/issues/13543, including possible workarounds.

I was staring at the same issue. Swift app on Xcode 16, with Firebase 10.28, 10.29, etc using SPM. Also, followed textbook steps exactly as you have, all listed here: https://firebase.google.com/docs/crashlytics/get-started?platform=ios.

Was a bit puzzling to diagnose, until I tried uploading of a new build of a different app I had already published, and it popped up the same dSYM problems.

Resting