Is there a reason that Swift Package Manager generated libraries would have recently started triggering this error for target names that include underscores? See https://github.com/firebase/firebase-ios-sdk/issues/9912

if you're running into this issue with the leveldb CocoaPod (a dependency of FirebaseFirestore and FirebaseDatabase), we've published version 1.22.2 with updated minimum versions, compatible with Xcode 14. Run pod update to get 1.22.2.

Linking Firebase static frameworks via Swift Package Manager reliably reproduces the issue. See https://github.com/firebase/firebase-ios-sdk/issues/13551 and https://github.com/firebase/firebase-ios-sdk/issues/13764

@DTS Engineer Thanks for investigating. If I download the FirebaseAnalytics from the link in the Package.swift https://github.com/firebase/firebase-ios-sdk/blob/main/Package.swift#L306C13-L306C84 and run the file command it shows up as a static archive: $ file /Users/paul/Downloads/FirebaseAnalytics.xcframework/ios-arm64/FirebaseAnalytics.framework/FirebaseAnalytics /Users/paulbeusterien/Downloads/FirebaseAnalytics.xcframework/ios-arm64/FirebaseAnalytics.framework/FirebaseAnalytics: current ar archive My understanding is the Swift Package Manager or Xcode is wrapping the static framework with a dynamic wrapper when embed and sign is chosen. Since the Package.swift is pointing at a static framework, the resulting issue looks like a coordination issue between Apple tooling.