ITMS-90158

@vicatcu Awesome you found out the issue and thanks for posting that so other developers can be aware of if they get the ITMS-91061 that's what they need to do as well as posting the name of the plugin and the replacement to use. This a complete answer for developers. Thanks! Albert Pascual
  Worldwide Developer Relations.

I discovered the root cause was that a new requirement (ITMS-91061: Missing privacy manifest) started being enforced in December that affected the use of the @codetrix-studio/capacitor-google-auth. It seems like that plugin is not being maintained anymore, and I'll be looking into migrating to using @capgo/capacitor-social-login instead.

Hi Albert I went through Ed's post; basically, he is talking about how to embed the frameworks. In our case, this isn't about embedding the frameworks we have developed or even third party frameworks. It's likely about the Swift system libraries provided by Xcode, probably to support older iOS versions. As pointed out in Ed's post - iOS, watchOS, and tvOS support third-party frameworks but don’t support third-party standalone dynamic libraries—those outside a framework bundle, typically with the .dylib filename extension. The only exception to this rule is the Swift system libraries provided by Xcode. Our application deployment target is set to 13.0. We have started using Declared AgeRange Framework (Swift ONLY API) to comply with the upcoming state law. Declared AgeRange is an asynchronous API and our application uses await/Async. Initially we encountered a TestFlight error regarding the missing SwiftSupport folder. ITMS-90426: Invalid Swift Support - The SwiftSupport folder is missing We resolved t

Thanks for the post and the details, the error is not about having the latest version of Xcode, looks like you do have it as Xcode Version 26.2 (17C52). The error message you're encountering, ITMS-90426: Invalid Swift Support - The SwiftSupport folder is missing., indicates that your app submission to App Store Connect is missing a required folder named SwiftSupport. So this is extremely interesting to me for sure. When archiving your app, ensure there are no build warnings about folders. Go to > , and then check the Organizer to ensure everything is correctly packaged. If your app uses Swift Package Manager, ensure that all packages are updated and correctly integrated. Sometimes issues arise from improperly configured packages? I believe this issue is always about packages you are using. Can you check that? read until the end where a post from an Apple engineer will give you more information. If you're manually managing your app bundle, ensure the folder is present in the archive's structure. It

Thanks for the post. Are you using any other software besides Xcode? I have a few suggestions that I would like to share with you. Additionally, I would appreciate it if you could provide as much information as possible regarding the project that is generating this issue. Regrettably, the error message does not provide a substantial amount of information. “ITMS-90714: ” Invalid binary. The application contains one or more corrupted binaries. Please rebuild the application and resubmit it. Could I kindly request a few questions to assist us in further narrowing down the issue? Are you using Objective-C with empty names in the metadata? To identify the binaries with those conditions, you can run the following Terminal command on each binary inside the app: % xcrun dyld_info -objc Payload/YourApp.app/YourApp | grep (null)” Can you check the build log in Xcode and provide me with those messages including the warnings are really important and may give us a clue. Can you share those warnings? Additionally,

Ha. got an iOS version of the app together. Validated OK. Took a long time to upload but completed OK. Remember this includes the modified model in the app bundle. Got an email from App Store Connect. Please correct the following issues and upload a new binary to App Store Connect. ITMS-90558: Thinned app size is too large - The “/Payload/PK-LLM.app” app bundle in the universal variant is 4 GB, which exceeds the maximum allowable size. Looks like I'm going to upload the specialized model to HuggingFace. Also, the current macOS version give an error after compiling (but not always). Could not launch “PK-LLM” Runningboard has returned error 5. Please check the system logs for the underlying cause of the error. The logs are full of a lot of stuff I don't understand. Maybe uploading to HuggingFace is the way to go.

Thank you for your answer. I tried with both AsheKube.app.a-Shell.localWebServer and com.example.example-extension. The only difference I could see is that sometimes it would fail when uploading (I would get the error message inside Xcode) and other time it would fail after uploading: I would get a kind e-mail from AppStore Connect, stating: Hello, We noticed one or more issues with a recent delivery for the following app: a-Shell App Apple ID 1473805438 Version 1.17.0 Build 500 Please correct the following issues and upload a new binary to App Store Connect. ITMS-90349: Invalid Info.plist value - The value of the EXExtensionPointIdentifier key, AsheKube.app.a-Shell.localWebServer, in the Info.plist of “a-Shell.app/Extensions/localWebServer.appex” is invalid. Please refer to the App Extension Programming Guide at https://developer.apple.com/library/content/documentation/General/Conceptual/ExtensibilityPG/Action.html#/apple_ref/doc/uid/TP40014214-CH13-SW1. Apple Developer Relations Builds 496, 497 and