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

Question

Created 7h

Replies 1

Boosts 0

Participants 2

We are getting the above mentioned error while uploading to TestFlight.

We have used a Swift Class to request for the Age Range via DeclaredAgeRange Framework. We have exposed Swift class and a helper function to be available in Objective-C layer. We have enabled the following build settings

SWIFT_OBJC_INTERFACE_HEADER_NAME = "Common-Swift.h";

SWIFT_OBJC_BRIDGING_HEADER = "Common-Bridging-Header.h ";

ALWAYS_EMBED_SWIFT_STANDARD_LIBRARIES = YES

Also we are compiling the application using latest available Xcode release 17C52

Is there anything else we need to do to resolve the error?

Boost

Answer 1

DTS Engineer OP

Apple

5h

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.

0