Codesigning failure on MacOS

[girishw]

Description

I have an app with the Firebase SDKs that compiles and works fine for an iOS destination. However, I now have a new MacOS destination and the build fails for it with the following error message:

....../...app: code object is not signed at all In subcomponent: ....../Build/Products/Beta/..../Contents/Frameworks/GoogleAppMeasurement.framework Command CodeSign failed with a nonzero exit code

When I filter the MacOS build log for signing, I see the attached

: the frameworks are not getting signed. When I similarly filter for the iOS build, I see that they are getting signed.

Reproducing the issue

No response

Firebase SDK Version

10.23.1

Xcode Version

15.3

Installation Method

Swift Package Manager

Firebase Product(s)

Analytics

Targeted Platforms

macOS

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.

[ncooke3]

Thanks for the report. Is this issue occurring on 10.23**.0** as well?

[girishw]

Thanks for the report. Is this issue occurring on 10.23**.0** as well?

No, this does not occur on 10.23.0. Please note that I am using the new Xcode multiplatform target feature.

[kevinanderson7]

We are seeing a similar issue with Mac Catalyst after updating to version 10.23.1 from 10.22.0. An iOS destination seems to work fine. I can also confirm that the issue doesn't seem to happen with version 10.23.0.

[SwiftNativeDeveloper]

This is also happening to my team for 10.23.1.

My project setup is a single universal app (iOS + iPadOS), targeting iOS 17.0 SDK, Xcode 15.3, nothing special.

Noteworthy, it can also happen for another third party dependency that we use that is also a swift package .binaryTarget.

[ncooke3]

Thanks, everyone. I suspect this issue will be fixed by the 10.24.0 release next week. The next release will contain signed SDKs and SDKs with a fixed structure for macOS/macCatalyst. I will keep this issue open until then.

[ncooke3]

10.24.0 is now released and all XCFrameworks have code signatures. I'm marking this as closed, but do let me know below if the issue persists after updating.