ITMS-90334 error when executing a Xcode Cloud TestFlight build

When I try to create a TestFlight build of my app using Xcode Cloud, I get a couple of ITMS-90334 errors and the build fails. The error messages look like:

ITMS-90334: Invalid Code Signature Identifier - The identifier 'MySwiftPackage-55554944e95A2da4fe9e3357b44de57c3ba890e8' in your code signature for 'MySwiftPackage_-658550CFFF128C8B_PackageProduct' must match its Bundle Identifier 'MySwiftPackage'

Where MySwiftPackage is a Swift Package which is used by a framework as well as the application. The dependencies look like this:

MyApp
+ MyFramework
  + MySwiftPackage
+ MySwiftPackage
  • MyApp is a macOS app
  • MyFramework is a mixed Swift and Objective-C framework
  • MyApp is also mixed Swift and Objective-C
  • When I run an archive build on my local Mac and upload the build to App Store Connect to be used as a TestFlight build, everything seams to be fine and the build is accepted
  • I found some discussions on ITMS-90334 but not related to using Swift Packages and Frameworks

Any ideas what might be going on or where I can look to get more info on the nature of ITMS-90334?

Accepted Reply

Same issue for us. Works fine manually via Xcode.

Trigger Xcode Cloud build. 2 of our packages result in the same error.

The packages are pure Swift. Our codebase is pure swift. It is an iOS app.

  • This is interesting. I assumed it has something to do with my Swift Packages used and embedded by the Objective-C frameworks. But this seams not to be the case.

    By the way, flagging your reply as "accepted solutions" was an "accident" on my part. But there seams to be now way to un-flag a reply once it has been set. So from my point of view, I'm still looking for an answer!

Add a Comment

Replies

Same issue for us. Works fine manually via Xcode.

Trigger Xcode Cloud build. 2 of our packages result in the same error.

The packages are pure Swift. Our codebase is pure swift. It is an iOS app.

  • This is interesting. I assumed it has something to do with my Swift Packages used and embedded by the Objective-C frameworks. But this seams not to be the case.

    By the way, flagging your reply as "accepted solutions" was an "accident" on my part. But there seams to be now way to un-flag a reply once it has been set. So from my point of view, I'm still looking for an answer!

Add a Comment