You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I integrate Google Firebase using Swift Package Manager and can receive events in the Analytics's real-time dashboard. Everything will go fine until it is submitted to App Store Connect.
When I submitted my app to App Store Connect for testing, I got an email that there was an error in my app:
Hi eveeyone, I'm closing this as it is a dupe of #12505. The issue came down to a faulty plist for macOS slices and a subtle change in framework validation in Xcode 15.3. The fix for this should be released this week (#12505 (comment)).
Description
I integrate Google Firebase using Swift Package Manager and can receive events in the Analytics's real-time dashboard. Everything will go fine until it is submitted to App Store Connect.
When I submitted my app to App Store Connect for testing, I got an email that there was an error in my app:
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.
Reproducing the issue
No response
Firebase SDK Version
10.22.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
snippetIf using CocoaPods, the project's Podfile.lock
Expand
Podfile.lock
snippetReplace this line with the contents of your Podfile.lock!
The text was updated successfully, but these errors were encountered: