[11.3.0] Xcode 16.0 Validation Warnings ("The archive did not include a dSYM for")

[craiganthonyio]

Description

These validation warnings did not occur for me with Xcode 15.4 just a few days ago (was on Firebase 10.26.0 then). Since updating Xcode to 16.0 and Firebase to 11.3.0, my Xcode project successfully validates, but I get numerous warnings like this:

"Upload Symbols Failed The archive did not include a dSYM for the FirebaseAnalytics.framework with the UUIDs [...]. Ensure that the archive's dYSM folder includes a DWARF file for FirebaseAnalytics.framework with the expected UUIDs."

The frameworks I get the warnings for are: FirebaseAnalytics.framework FirebaseFirestoreInternal.framework GoogleAppMeasurement.framework GoogleAppMeasurementIdentitySupport.framework GoogleAppMeasurementOnDeviceConversion.framework absl.framework grpc.framework grpcpp.framework openssl_grpc.framework

Just a heads up...

Reproducing the issue

Archive an Xcode project using Xcode 16.0 and Firebase 11.3.0 and validate the archive.

Firebase SDK Version

11.3.0

Xcode Version

16.0

Installation Method

Swift Package Manager

Firebase Product(s)

Analytics, App Check, Authentication, Crashlytics, Database, Firestore, Functions, Installations, Messaging, Performance, Storage

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.

[paulb777]

May be a duplicate of #13551

[paulb777]

Based on the conversation in https://developer.apple.com/forums/thread/761589, this looks like an Apple issue

[biblehour]

Is there any work around for this? This issue seems to be breaking google analytics completely for iOS app. Every user who updated their app version to the new version (that had this missing dSYM issue) is now not showing in Analytics.

Is using Cocoapods instead a workaround? Or any other work around? This is a big issue for us as Analytics is now broken

[paulb777]

@rbmstudios You're the first report of Analytics not functioning with this warning. Would you open another issue with the template completed for your config?

[HugoMartins]

Same here with last Xcode 16.1 and Firebase 11.4.0

[hayata-0]

I'm facing the same problem myself.

[jerald-dexcom]

Coming from https://github.com/firebase/firebase-ios-sdk/issues/13543, and DSYMS uploads are not working for me even after updating to 11.4. Should we revert back to 11.2 and dsiable ENABLE_DEBUG_DYLIB = NO?

[Muhammadbarznji]

Any Update?

[fred-bowker]

Xcode 16.1 and Firebase 11.4.0, I am getting these warnings also. What is the actual effect of this does it mean that for crashlytics we won't get detailed crash reports as the DSYMS files aren't getting uploaded with the build?

[Harikarthyk]

+1

[IvanKalaica]

Is there any work around for this? This issue seems to be breaking google analytics completely for iOS app. Every user who updated their app version to the new version (that had this missing dSYM issue) is now not showing in Analytics.

Is using Cocoapods instead a workaround? Or any other work around? This is a big issue for us as Analytics is now broken

I’m experiencing an issue where Firebase Crashlytics (v11.5.0) non-fatal issues have stopped appearing for builds archived using Xcode 16.0. This was also accompanied by Validation Warnings during the archive build process. As a result, I now have a critical gap in my live environment, leaving me effectively blind and unable to troubleshoot issues.

[paulb777]

@IvanKalaica Is your issue the same as #14054?

[fred-bowker]

Hi @samedson

Relating to, Release Builds aren't uploading symbols when you archive and upload to the App Store

My understanding of this is that when upgrading to XCode 16, all users of Firebase crashlytics will start seeing the warning:

Upload Symbols Failed The archive did not include a dSYM for the FirebaseAnalytics.framework

The Apple developer link https://developer.apple.com/forums/thread/761589?answerId=808296022#808296022, states this is by design and that the warning is shown when a 3rd party library doesn't include a corresponding dsym file for the library.

Is it your understanding that this is why we have now started seeing this warning when users have moved to XCode 16 from XCode 15?

Thanks, Fred

[samedson]

Hey @fred-bowker, so the pattern we're seeing is that SDKs that Firebase distributes as binaries are being impacted by this, which includes:

• FirebaseAnalytics
• GoogleAppMeasurement
• FirebaseFirestore

Our hunch is there's something in our build process that's stripping out the symbols, or not producing them in a way that Xcode 16 wants. My hunch right now is that Apple expects an explicit dSYM for each framework, which we may not be producing in the binary frameworks (the binaries themselves should have symbols included though).

But to your question, I believe these warnings are happening with Xcode 16 only.

In the coming weeks we're going to spend some time to figure out how to update our build process to make these warnings go away. For now, as long as there's no impact to your workflow, it should be safe to ignore these warnings (my hunch is this impacts Apple's ability to display stacktraces in their crash reporting system for the impacted frameworks).

[karimjimo]

hi there.

Is there any ETA for this issue?

[lakshaya-heyaura]

Any solution for this yet?

[ncooke3]

Hi all, the validation warnings should be harmless. I left a response to the Apple forums thread above that provides more context as to what is going on: https://developer.apple.com/forums/thread/761589?page=3

I believe the fix needs to come from Apple as Xcode is complaining about missing dSYMs for a dylib that it (Xcode) created.

[IvanKalaica]

Is there any work around for this? This issue seems to be breaking google analytics completely for iOS app. Every user who updated their app version to the new version (that had this missing dSYM issue) is now not showing in Analytics. Is using Cocoapods instead a workaround? Or any other work around? This is a big issue for us as Analytics is now broken

I’m experiencing an issue where Firebase Crashlytics (v11.5.0) non-fatal issues have stopped appearing for builds archived using Xcode 16.0. This was also accompanied by Validation Warnings during the archive build process. As a result, I now have a critical gap in my live environment, leaving me effectively blind and unable to troubleshoot issues.

Issue fixed. It was an internal app bug preventing non-fatal crashes from reaching Firebase Crashlytics.

[karimjimo]

@IvanKalaica how did you fix it?

[IvanKalaica]

@IvanKalaica how did you fix it?

It was an internal app bug - not a Firebase Crashlytics issue.

[MoSabry00]

@IvanKalaica how did you fix it?

It was an internal app bug - not a Firebase Crashlytics issue.

How did you fix it or how did you know its internal ? which code file was causing the issue?

[GiumaSoft]

I've found this post very interesting, so I decided to take a look into Package.swift file included in firebase-ios-sdk, that doesn't provide any the type of library (I suppose assuming that Xcode give you the option to compile it statically or dynamically) but that's not the case with Swift Package Manager.

Hope that can help to make some light on this issue.

[artroman]

To fix this issue, I rolled back Firebase instance to Cocoapods install method, which is already contains version 12.4.0.