5

I've been trying to upload a new build to iTunes Connect to update an app. I first used xCode 6 but got a email from Apple stating this:

Dear Developer,

We have discovered one or more issues with your recent delivery for "App". To process your delivery, the following issues must be corrected:

Invalid Swift Support - The files libswiftDarwin.dylib, libswiftDispatch.dylib, libswiftCoreGraphics.dylib, libswiftUIKit.dylib, libswiftContacts.dylib, libswiftCore.dylib, libswiftCoreAudio.dylib, libswiftFoundation.dylib, libswiftXCTest.dylib, libswiftCoreImage.dylib, libswiftObjectiveC.dylib aren’t at the expected location /Payload/App.app/Frameworks.

Move the file to the expected location, rebuild your app using the current public (GM) version of Xcode, and resubmit it.

Once these issues have been corrected, you can then redeliver the corrected binary.

I thought it was a simple fix, so I just updated to the latest GM (Xcode 7.2) & completed the Swift 2 migration, however I received the same email. Could someone explain how to solve this and what those files are? This isn't a "files don't match" problem as seen in other questions.

Zachary Espiritu
  • 937
  • 7
  • 23
John Polk
  • 51
  • 2
  • 1
    "Move the file to the expected location, rebuild your app using the current public (GM) version of Xcode, and resubmit it." Have you done what they told you to do? Have you moved those 11 files to the correct location? – Leo Dabus Jan 05 '16 at 01:42
  • I've rebuilt the app using the current GM, however I don't know what those files are (never heard of them before) so I have not done the second part. Please explain in simple terms for i am a newbie. Thanks – John Polk Jan 05 '16 at 12:00

3 Answers3

1

I stumbled upon this as I've encountered the same problem. It's the first time I've been tasked with handling the release of a Swift app to the App Store.

I found that this answer by TALAA works a treat: https://stackoverflow.com/a/26949219/1567836

There is an "Embedded Content Contains Swift Code" flag in the Build Settings that needs to be set to YES. After setting this, clean the project before building again.

After the clean, you'll have to recreate a build to upload to the App Store. You might find that the new upload will get rejected claiming that a binary already exists for that number. If you update the build number (has to be larger than the previous one) then the new upload will be accepted.

Community
  • 1
  • 1
Thomas Verbeek
  • 2,361
  • 28
  • 30
0

As per the @Thomas You need to enable that flag and after that for the "Invalid Swift Support", I had the issues with Application Loader since Xcode 6.4. So, I started uploading the app from the "Organizer" (Xcode > Window > Organizer > Upload to App Store).

This solves the problem.

Community
  • 1
  • 1
Sohil R. Memon
  • 9,404
  • 1
  • 31
  • 57
0

Inspect the payload and also the SwiftSupport folder in the .ipa file (by converting it to a .zip) and make sure the libraries in the email match across both those directories. Those need to match apparently.

You should probably not have libswiftXCTest.dylib in the Payload/App.app/Frameworks or SwiftSupport folders in something you're submitting to Apple. If you do, check the build section of the scheme for your App target and make sure you aren't including any test targets in your Archive step.

Matt Giger
  • 1