Asset validation failed (90085): Static Framework Embedded in Dynamic Framework

Question

Created 2w

Replies 1

Boosts 1

Participants 1

One of our apps got hit by the ITMS-91065: Missing Signature issue when we attempted to distribute it to externally via TestFlight. The email said FirebaseCore is missing the signature file within our own framework. After investigation, I realized our recent update to the version of Firebase that has the proper signatures and privacy manifest wasn't enough by itself.

Similar to Apple's own instructions on embedding static frameworks since Xcode 15, Firebase instructs us to select the Embed & Sign option. After making the appropriate changes though, we're getting the error in Transporter:

Asset validation failed (90085): No architectures in the binary

Our setup is as follows:

We have an analytics dynamic framework, which depends on Firebase's static framework. The Firebase related frameworks are embedded and signed in our analytics framework.

Our app depends on the analytics dynamic framework, which now includes Firebase frameworks within its framework. Since the Firebase frameworks are static, only the Info.plist and the resource bundle with privacy manifest and another Info.plist are included.

After searching online, some suggest it's because of the Info.plist included. For example, FirebaseCore.framework, which specifies CFBundleExecutable yet it's not included within the framework itself. I don't expect the executable to get included here though.

I opened an issue on Firebase's Github, which has more information. I am not sure how to proceed from here. Is there something I am missing? I would appreciate assistance. Thank you.

Boost

Answer 1

eb_lancefu OP

2w

After trying a few things, from using latest Xcode to switching dependency manager that imports Firebase from Carthage to Swift Package Manager, nothing seems to make a difference.

At this point, I think the issue is one of the following:

There's unknown issue with our project setup that removes the binary itself along with the codesign folder.
Including a static framework within a dynamic framework while the former needs to be signed simply isn't supported by Apple.

I then pivoted and started removing our Firebase integration and implementation in the library, and moved it to the app project itself. No issues were observed when uploading through Transporter. The build was processed, then I submitted it for review to distribute to external group on TestFlight. I will report back after it's reviewed.

0