To Whom It May Concern
I am developing an iOS iPhone application and am failing at the last hurdle. I am generating an IPA file without the SwiftFrameworksSimulator so am using an IPA packager to add the SwiftSupport folder to the IPA but unfortunately the version of the Swift Framework files are different in my app file and the SwiftSupport folder. I tried to rectify the issue by extracting the Frameworks folder from my app and tried to use these files for the Swift Support folder but got a signature error upon uploading the IPA file to Apple's App Store Connect site which is as follows: Invalid Swift Support - The file libswiftAVFoundation.dylib doesn’t have the correct code signature. I know PLIST files are the Swift configuration files so am wondering if there is a key that I can set to ensure the correct version of Swift compiler is called when building the original IPA file in Visual Studio (I'm using VS2017 on Windows) so that when packaging the IPA file with the IPA Packer shell script the correct Swift Support files are included? I am pairing VS2017 with a Macintosh running High Sierra and Xcode 10.1 with the 4.2.1 Swift compiler. All I need is a way to tell Visual Studio to tell XCode to use the correct ToolChain files to add to the original IPA file created by MSBuild in conjunction with XCode 10.1 so that when I use the IPA Packager the SwiftSupport folder is identical to the app\Frameworks folder removing the correct code signature and previous support files with different versions errors.
Any help is appreciated!
yours sincerely
Craig Hoy