Open flexund opened 3 months ago
I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight.
Thanks for reporting this, @felixhedlund. I was able to reproduce the issue. I've raised this to our engineers and see what we can do here.
hello! Any news/updates? Thanks
@rizafran please make it to Dynamic library option.
it seems that dynamic library is deprecated on Firebase side...
Any update on this? I'm experiencing the exact same, and the same frameworks with FirebaseAnalytics, GoogleAppMeasurement and GoogleAppMeasurementIdentitySupport. Plus GoogleTagManager.
Was using CocoaPods, but moved over to SPM to see if that would help (allowing me to install it fresh, as this is a 3-4 year old project).
Hi, I'm also experiencing this issue. Standard SPM installation using Analytics, Auth, RemoteConfig, Storage.
App Store Connect flow, via Xcode, successfully uploads but says it has the following issues:
"The following issues occurred while distributing your application" ... "Upload symbols failed" "The archive did not include a dSYM for the
I've ensured that build Project > Build Settings > Debug Information Format is set to "DWARF with dSYM File" for both with Debug and Release
Just worth mentioning for anyone following here that there's a larger discussion about the issue here with some potential workarounds for the moment.
(I'm not a contributor btw, just happened to be following both Issues!)
Any ETA on fixing this ?
I can reproduce this issue with Swift Package Manager, but not with CocoaPods. I just want to be sure that this issue is not blocking App Review or App Store release, right?
According to the post on the Apple Developer Forums, this is an Apple issue, not an SDK issue.
According to the post on the Apple Developer Forums, this is an Apple issue, not an SDK issue.
It seems not an Apple issue, according to the lasted answer from Apple engineer: https://developer.apple.com/forums/thread/761589?answerId=806733022#806733022
See the latest at https://developer.apple.com/forums/thread/761589?page=2
A little confused on the resolution here, it seems that this is Apple updating their system to warn about symbols that are not included in crash reports, so Firebase needs to have some files included in the SPM builds that aren't right now. Is there any fix planned from Firebase? Or is this just a warning we'll have to ignore.
As far as we can tell it's an Apple issue and we're waiting for a response. For now, we believe the right approach is to ignore the warning.
Same issue Xcode 16.1 with firebase-ios-sdk v11.4.0
For now, we believe the right approach is to ignore the warning.
Alright! Let us know here once it resolved. @paulb777 Thank you!
Description
After archiving project with Firebase frameworks, the upload process completes with warnings about the archive's dSYM folder is missing DWARF file for these frameworks:
Reproducing the issue
Archive & Upload a build to App Store Connect using Xcode 16 Beta 6
Firebase SDK Version
11.1.0
Xcode Version
16 Beta 6
Installation Method
Swift Package Manager
Firebase Product(s)
Analytics
Targeted Platforms
iOS
Relevant Log Output
No response
If using Swift Package Manager, the project's Package.resolved
N/A
If using CocoaPods, the project's Podfile.lock
N/A