Paul Raymond
Paul Raymond

Reputation: 1205

Error after uploading app to the app store

For the record I have not touched any of the files listed below, all I did was compile, attempt to pull my hair out by uploading and then I got this error message:

Invalid Swift Support - The files libswiftDarwin.dylib, libswiftMetal.dylib, libswiftCoreAudio.dylib, libswiftQuartzCore.dylib, libswiftos.dylib, libswiftObjectiveC.dylib, libswiftDispatch.dylib, libswiftCoreGraphics.dylib, libswiftCoreData.dylib, libswiftCoreFoundation.dylib, libswiftUIKit.dylib, libswiftCoreMedia.dylib, libswiftCore.dylib, libswiftFoundation.dylib, libswiftXCTest.dylib, libswiftCoreImage.dylib aren’t at the expected location /Payload/BeginerGuideDigFor.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.

Honestly I wouldn't even know where to beign

So to answer one of the question, according to the part apple told me to go through my libraries are fine here is a pic of me running the code for that enter image description here

here is what I ran and below that is the result enter image description here

UPDATE:

SOOOOO at this point I have now confounded the app support store, they cannot figure out why I am getting this error, they have asked me the same questions over and over, what version of Xcode, what version of Mac OS... still no resolution.

Upvotes: 1

Views: 1118

Answers (1)

clarus
clarus

Reputation: 2475

You mention a hair-pulling upload experience. But unless you have a build system/build scripts involved, normally the process is just Product>Archive and uploading from Window>Organizer (or using the Application Loader on an exported ipa from there). Are you doing anything different that may be corrupting the .ipa?

You might Export it for App Store, rename the .ipa file to .zip and unzip it. Right click on your app in the Payload directory, select Show Package Contents and look in your Frameworks directory for a clue. All of those files should be there. Do you have any Build Phase scripts that do anything with Frameworks?

UPDATE:

I just came across this Apple response to this type of issue in the Apple Developer Forums. That's a great resource for these types of things, by the way:

It's likely you have a plain dylib outside of a framework somewhere, which is only supported on macOS. Please review the Troubleshooting section of Tech Note 2435 for more context. If having a bare dylib is indeed the cause of the problem, please file a bug for an error message that clearly explains this.

Link: https://forums.developer.apple.com/message/218019#218019

Upvotes: 1

Related Questions