There is an issue tracking this in the firebase-ios-sdk repo. I'm trying to figure out it if this is only caused by Firebase. Is anyone using Firebase? Is anyone not using Firebase, but seeing this issue? If you are using Firebase and seeing this issue, please feel free to contribute to the discussion in the above linked issue. Additionally, reverting to Firebase 10.7.0 should unblock your development until a solution is found. Thanks!

These frameworks come from Firebase and the corresponding fixes will be released this week (week of March 18, 2024). Refer to this issue in the Firebase repo for more details.

Hi @DTS Engineer – Static frameworks containing privacy manifests need to be embedded, so that the privacy manifest resource is copied into the app bundle. When embedding a static framework, Xcode 15 is smart enough to strip out the static archive, replace it with an empty dylib, and copy in the resources. This explains why Paul was able to download the SDK as a static framework, but you saw the same SDK as a dylib within the app bundle. When Xcode 16 sees this Xcode-generated empty dylib, it looks for the corresponding dSYM file, but it's not there and emits the warning. I believe the fix is within Xcode– when Xcode detects a static framework is being embedded and generates the empty dylib, it also needs to generate an empty dSYM to go along with it.