Xcode Cloud + dynamic library package

I'm trying to archive my app via Xcode Cloud and auto-deploy to TestFlight but it fails during "Prepare Build for App Store Connect" with the following error message:

ITMS-90334: Invalid Code Signature Identifier. The identifier "CoreImageExtensions-dynamic-555549444e09e22796a23eadb2704bf219d5c1fa" in your code signature for "CoreImageExtensions-dynamic" must match its Bundle Identifier "CoreImageExtensions-dynamic"

CoreImageExtensions-dynamic is a .dynamic library target of a package that we are using.

It seems that at some point a UUID is added to the library's identifier, which messes with code signing. When archiving and uploading the app in Xcode directly, everything works just fine.

Any idea why this is happening and how I could fix it?

Up vote post of FrankSchlegel Down vote post of FrankSchlegel
2.5k views
Posted by
FrankSchlegel
Reply

  • I have the same problem using a swift package with binary target.

    —
    Ken Chung
Add a Comment

Apple Recommended

Please see this other thread for further discussion of the issue, as well as some workaround possibilities.

Posted by
edford
Up vote reply of edford Down vote reply of edford
Post marked as Apple Recommended
Add a Comment

Replies

I have the same problem – and yes, the package is also a dynamic one.

Posted by
adam@micropixels
Post not yet marked as solved Up vote reply of adam@micropixels Down vote reply of adam@micropixels
Add a Comment

I had this with a third-party package I was trying to include and tried a few things to get around it but wasn't able to. I finally realized the package didn't need to be a dynamic library. Once I removed that from it's Package.swift file, it builds fine.

Posted by
joulupukki
Post not yet marked as solved Up vote reply of joulupukki Down vote reply of joulupukki
Add a Comment

Same issue for me. Hoping we get some traction by bumping it. Quite a few others have run into it and while moving to a .static library is a valid work around in some cases it's not going to necessarily work for everyone (including myself).

Some others who have encountered the issue:

I've also tested on the Xcode 13.3.1 and no dice.

Posted by
jjsidhu23
Post not yet marked as solved Up vote reply of jjsidhu23 Down vote reply of jjsidhu23
Add a Comment

Please see this other thread for further discussion of the issue, as well as some workaround possibilities.

Posted by
edford
Up vote reply of edford Down vote reply of edford
Post marked as Apple Recommended
Add a Comment