ITMS-90426: Invalid Swift Support - The SwiftSupport folder is missing. Rebuild your app using the current public (GM) version of Xcode and resubmit it

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 should be located at the root level alongside your file. Normally, Xcode handles this automatically.

I am not interested in how you build your Objective-C and Swift together and set up the bridge header. Did you let Xcode do it for you?

I do not believe this is a bug and I believe you have submitted one today? I think this is a configuration issue on your project that is preventing the SwiftSupport build from being created.

My personal recommendation at this point is to create a new project in Xcode and add some Objective-C code and let the bridge header be created. Then when submitting, you will not receive this error and you can compare the differences between both projects instead of trying to find out the issue looking at how the project was setup.

But I never seen this issue but we have people that has and some post about it, hope someone here have seen it previously and realize what setting is causing the SwiftSupport folder to be excluded normally is a library and external framework from the post below:

We have a post from an Apple Engineer about this here that will provide most of the information https://developer.apple.com/forums/thread/765288?answerId=807098022#807098022

Albert Pascual
  Worldwide Developer Relations.

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 this error by generating an Archive using Development environment and then extract an IPA using Distribution method. The resulting IPA contained the SwiftSupport folder that App Store Connect expected. <key>method</key> <string>app-store-connect</string>

FYI, this occurs when we generate an Archive using the Development environment and then extract an IPA using the development method. The resulting IPA did not have the SwiftSupport folder. <key>method</key> <string>development</string>

The new observation is that uploading the application to TestFlight was successful. But the minute we add testers and submit for review, the application binary state shows "invalid binary" as seen in the attached screenshot.

What causes the application binary state to become "invalid binary"? Could you please help here on this.

Regards, Chethan