Code Signing failed for third-party Swift package

Question

Created Mar ’24

Replies 5

Boosts 3

Views 1.5k

Participants 6

I am having trouble submitting the next build of my macOS app to the App Store Connect. I keep getting a variation of this error:

ITMS-90238: Invalid Signature - The main app bundle MyApp at path MyApp.app has following signing error(s): code has no resources but signature indicates they must be present In subcomponent: MyApp.app/Contents/Frameworks/GoogleAppMeasurement.framework . Refer to the Code Signing and Application Sandboxing Guide at http://developer.apple.com/library/mac/#documentation/Security/Conceptual/CodeSigningGuide/AboutCS/AboutCS.html and Technical Note 2206 at https://developer.apple.com/library/mac/technotes/tn2206/_index.html for more information.

ITMS-90238: Invalid Signature - The main app bundle MyApp at path MyApp.app has following signing error(s): code has no resources but signature indicates they must be present In subcomponent: MyApp.app/Contents/Frameworks/GoogleAppMeasurementIdentitySupport.framework . Refer to the Code Signing and Application Sandboxing Guide at http://developer.apple.com/library/mac/#documentation/Security/Conceptual/CodeSigningGuide/AboutCS/AboutCS.html and Technical Note 2206 at https://developer.apple.com/library/mac/technotes/tn2206/_index.html for more information.

ITMS-90238: Invalid Signature - The main app bundle MyApp at path MyAppt.app has following signing error(s): code has no resources but signature indicates they must be present In subcomponent: MyApp.app/Contents/Frameworks/FirebaseAnalytics.framework . Refer to the Code Signing and Application Sandboxing Guide at http://developer.apple.com/library/mac/#documentation/Security/Conceptual/CodeSigningGuide/AboutCS/AboutCS.html and Technical Note 2206 at https://developer.apple.com/library/mac/technotes/tn2206/_index.html for more information.

I am using Firebase framework as a Swift package. I tried updating Swift package to the latest version and that didn't help. I also tried to revert to the last version that was successfully used on the App Store/TestFlight and that didn't help.

I have no control over this framework other than not use it or choose a specific version.

I also tried to export the app and use the Transporter app and that didn't help.

Any suggestions?

Boost

Answer 1

JesusMG OP

Mar ’24

any information about it @eskimo ?

0

Answer 2

nickcooke OP

Mar ’24

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.

3

Answer 3

Rakel Lion OP

Mar ’24

App Store Connect

Hello,

We noticed one or more issues with a recent delivery for the following app:

Version 24.3.4 Build 2.1.0 Please correct the following issues and upload a new binary to App Store Connect.

ITMS-90291: Malformed Framework - The framework bundle FirebaseFirestoreInternal (------.app/Contents/Frameworks/FirebaseFirestoreInternal.framework) must contain a symbolic link 'FirebaseFirestoreInternal' -> 'Versions/Current/FirebaseFirestoreInternal'. Refer to the Anatomy of Framework Bundles for more information.

1

Answer 4

anosidium OP

Mar ’24

I had these problem when I was using Xcode Version 15.3 (15E204a). It turns out that they have fixed it but then Apple has apparently changed something in their backend. There's an opened issue about the new problems, Malformed Framework response from App Store Connect. The suggestion for the meantime is to use Xcode Version 15.2 (15C500b).

0

Answer 5

IoStream OP

Mar ’24

Xcode Archive
Open archives window
Show in finder
Show package contents
Go to /Products/Applications/%YOUR_APP%.app/Contents/Frameworks/
Backup deleted files, delete google "frameworks" that cause error ITMS-90238, GoogleAppMeasurementIdentitySupport.framework, FirebaseAnalytics.framework etc
Upload modified archive again from Xcode Archives window

Look to the size of frameworks, this is something wrong with it.

After all build processing completed and I check work in TestFlight and all ok

0