publish ios error: The SwiftSupport folder is missing

[Serge-SDL]

Hi!
I try to pusblish my app on AppStore and everything works well: build cmd and publish cmd but then I received an email from App store connect:

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

I saw some answers like this: https://stackoverflow.com/questions/38981628/invalid-swift-support-the-swiftsupport-folder-is-missing-with-xcode-7-3-1 but I don't know how to apply this on nativescript.

can anyone help on this ?
thanks!

[mbektchiev]

Are you using Xcode 11.4 to build your app?

[Serge-SDL]

yes, I use the last version.
I managed to comple my app since but without using cli...

[mbektchiev]

Can you try cleaning your platforms/ios folder and performing a publish build once more? After that please check whether the .ipa package contains a folder named SwiftSupport (You can change its extension to .zip and extract it). Also, you can search for files named libswiftFoundation.dylib and report if and where they are found in the platforms/ios directory and in the extracted .ipa.

[StefanNedelchev]

I also have the same issue and I use distribution provisioning profile. I also tried doing this with Always Embed Swift Standard Libraries option enabled from the xcode project.

[dyrkow]

@mbektchiev i have same issue. Yes, i have some swift library in my app file

[mbektchiev]

Rebuild your app using the current public (GM) version of Xcode and resubmit it.

Maybe you need to upgrade Xcode to the latest (12.3) version...

[dyrkow]

@mbektchiev Prodict ~> Archive works for me. I'm used just build.

[fpaaske]

I get the same issue when using NativeScript to build the release, but opening Xcode and archive from there works like a charm. It quite annoying because it prevents us from automating the build completely:

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

I'm using the latest Xcode at the moment; 15.2.

[shirakaba]

Heya @fpaaske we’re no longer (actively) maintaining JSC so I’m curious why you went with that over our stable V8 runtime?

[fpaaske]

Sorry, I'm not using this jsc version. I just found the same issue here and commented.