ITMS-90426: Invalid Swift Support

Question

joebob2003 OP

Created Feb ’20

Replies 7

Boosts 0

Views 13k

Participants 10

Hi,

Having issues uploading our build to App Store Connect for use in TestFlight. We get a success when building through Xcode, but we get an email after it uploads via archive manager stating "ITMS-90426: Invalid Swift Support - The SwiftSupport folder is missing. Rebuild your app using the current public (GM) version of Xcode and resubmit it.".

We have confirmed that we don't have any Swift dependencies and that we are running the latest Xcode (v11.3.1). We've also tried to build/deploy this on multiple computers with the same error. Our app was built using Unity, then brought into Xcode to build/deploy from there. We have never had any Swift dependencies in our project.

We are able to deploy directly to our devices, but it seems that the only time we run into issues is trying to. Any help is appreciated.

Boost

Answer 1

sudutta OP

Apr ’20

We face the same issue, were you able to solve it?

0

Answer 2

sfsfsdf OP

Jun ’20

did you Solve the issue i am also facing the same issue

0

Answer 3

ajzarn OP

Jun ’20

You may need to manually include the SwiftSupport folder. This post may be helpful: https://stackoverflow.com/questions/57214466/ios-resigning-enterprise-ipa-with-app-store-certificate/62457388#62457388

0

Answer 4

a_weissbr OP

May ’21

Getting same Issue by uploading build with azure pipeline. Xcode 12.4 is currently used, don't have possability at the moment to update to newer (12.5) Xcode version (VM Agent).

.xcarchive don't contains SwiftSupport folder when builing with azure pipeline. Manuelly adding of SwiftSupport with this workaround not working -> same issue ITMS-90426: Invalid Swift Support with list of libs.

Has anyone Solutions to fix this?

0

Answer 5

rruipinheiro OP

Jan ’23

Did you found a solution for this? I have the same problem.

0

Answer 6

gregorx1 OP

Apr ’23

Please verify if you are not uploading adhoc ipa which is by default stripped of Swift files. In my case - that kind of checking in fastlane script and explicitly specifying the correct ipa file helped.

4

Answer 7

bastisenengo OP

Aug ’23

Uploading the Ad Hoc build to the App Store was my problem. Thanks @gregorx1! for the hint!

1