Geek Answers Handbook

"Invalid Swift Support - Missing SwiftSupport Folder" with Xcode 7.3.1

After sending the application update using Application Loader, I received this email from Apple:

We have encountered one or more problems with your recent delivery for "[Application Name]". To process your delivery, the following problems should be fixed:

Invalid Swift support - missing SwiftSupport folder. rebuild your application using the current publicly available (GM) version of Xcode and resubmit it.

Once these problems are fixed, you can re-add the fixed binary.

I confirmed that this binary was built with the latest GM Xcode (7.3.1), so this is not a problem. I saw many possible fixes for this problem on the Internet, but I hoped that by giving more detailed information someone could help me figure out a specific solution.

  • Presented IPA file using Application Loader 3.5 without problems.
  • The previous version of the application does not use Swift, but this update is in progress.
  • Setting up an assembly with embedded content contains a quick code: NO . My understanding is that this should only be YES if we have a pure Objective-C target that depends on Swift or a mixed target.
  • The project uses CocoaPods, but nothing has changed in our packages for this update.
  • In the previous version of the application, the application and the WatchKit extension were added, but this update does not work.
  • Inside xcarchive generated with the same assembly, there is a SwiftSupport folder. It contains a subfolder called iphoneos that contains several Apple Swift libraries, such as libswiftFoundation.dylib .
  • If I rename the .ipa file to .zip and unzip it, its application package does not contain the SwiftSupport folder, but contains the Frameworks folder with the same types of Swift styles.
+6
source share
3 answers

The solution here was in this answer . We needed to use the new -exportOptionsPlist flag with xcodebuild instead of the old -exportFormat and -exportWithOriginalSigningIdentity flags. Plist just needs to have the method key installed on the app-store .

+7
source

In my case, I just added a redundant fast file to the project, and it solved the problem.

0
source

You should select "Save for deployment of the iOS app store" instead of the option "Save for custom deployment" when creating the ipa file. enter image description here

0
source

More articles:


All Articles