I’m getting the following email back from Apple after a build is processed:

Invalid Swift Support - The files libswiftCoreAudio.dylib, 
libswiftCoreData.dylib, libswiftCoreLocation.dylib don’t match 
/Payload/splashpath.app/Frameworks/libswiftCoreAudio.dylib, 
/Payload/splashpath.app/Frameworks/libswiftCoreData.dylib, 
/Payload/splashpath.app/Frameworks/libswiftCoreLocation.dylib. Make sure the 
files are correct, rebuild your app, and resubmit it. Don’t apply 
post-processing to /Payload/splashpath.app/Frameworks/libswiftCoreAudio.dylib, 
/Payload/splashpath.app/Frameworks/libswiftCoreData.dylib, 
/Payload/splashpath.app/Frameworks/libswiftCoreLocation.dylib.

I’ve found a StackOverflow thread here which seems to suggest I need to move 
some libraries about in the archive:

http://stackoverflow.com/questions/32526526/invalid-swift-support-files-don-t-match
 
<http://stackoverflow.com/questions/32526526/invalid-swift-support-files-don-t-match>

What I’m wondering is if this is a bug in Xcode or we’re just not mean to be 
able to submit binaries with non-bitcode frameworks? I’m going to try the 
workaround and then submit a radar either way.
 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      ([email protected])
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/xcode-users/archive%40mail-archive.com

This email sent to [email protected]

Reply via email to