Hello,
i know this topic is here since ever, also in other forums, however this topic i face for a month and cant get pass it, I tried all other suggestions which didnt bring me anywhere.
so, project using cmake in order for Qt creator (so c++ base project with enabled swift), however once i run a cmake which generates *.xcodeproj for Xcode, i open it via xcode and can properly build and deploy to device.
however when I try to archive and sent to Testflight/AppStore, I get:
ITMS-90426: Invalid Swift Support
and when I try to followup guides to create it manualy, copying libs from:
$(TOOLCHAIN_DIR)/usr/lib/swift-5.0/$(PLATFORM_NAME)
- plese here note, that ALL guides indicate to use folder "swift", however there are no *.dylib files... they are only in "swift-5.0" folder
then I receive an error type:
ITMS-90429: Invalid Swift Support - The files libswiftMetal.dylib, libswiftHomeKit.dylib, libswiftsimd.dylib, libswiftCallKit.dylib, libswiftos.dylib, libswiftNetwork.dylib, libswiftMapKit.dylib, libswiftCoreLocation.dylib, libswiftAccelerate.dylib, libswiftCoreGraphics.dylib, libswiftSceneKit.dylib, libswiftCoreData.dylib, libswiftGameplayKit.dylib, libswiftUIKit.dylib, libswiftMetalKit.dylib, libswiftCore.dylib, libswiftFoundation.dylib, libswiftPhotos.dylib, libswiftModelIO.dylib, libswiftWatchKit.dylib, libswiftDarwin.dylib, libswiftARKit.dylib, libswiftAssetsLibrary.dylib, libswiftSpriteKit.dylib, libswiftNaturalLanguage.dylib, libswiftCoreAudio.dylib, libswiftIntents.dylib, libswiftQuartzCore.dylib, libswiftObjectiveC.dylib, libswiftDispatch.dylib, libswiftCoreFoundation.dylib, libswiftCoreMedia.dylib, libswiftVision.dylib, libswiftAVFoundation.dylib, libswiftContacts.dylib, libswiftGLKit.dylib, libswiftSwiftOnoneSupport.dylib, libswiftXCTest.dylib, libswiftMediaPlayer.dylib, libswiftCloudKit.dylib, libswiftCoreImage.dylib aren’t at the expected location /Payload/Filmtoro.app/Frameworks. Move the file to the expected location, rebuild your app using the current public (GM) version of Xcode, and resubmit it.
- here please also note that actually *.xcarchive does not contain any "Payload" folder, the package contains only two folders "dSYMs" and "Production/Applications/myapp.app" (inside it I can find "Frameworks" folder...
this link was also very interested: https://indiestack.com/2017/03/implicit-swift-dependencies/
- tho id didnt help a bit :)
so what I would like to know, is what actually forces xcode to generate the SwiftSupport folder to the archive... the must be some direct setting inside *.xcodeproj/pbxproj which forces it... or dirrect setting in xcode/Build Settings which if not work I can submit an ticket to investigate.
I am sure after a month of trying everything, whatever tip you can point out I already tried, however Please lets try everything again to get bottom of this.
Many thanks for any tip
It’s hard for Apple folks to help you when you’re this deep into third-party tools.
IMPORTANT The Xcode project format isn’t considered API and so DTS doesn’t support tools that generate Xcode projects.
Still, I have two bits of general advice on this topic:
-
Contact your tools vendor to see if they have specific advice for you.
-
If not, you can try the debugging approach suggested below.
My general advice for problems like this is to do what Xcode does. So, in this case that means something like the following:
-
Create a new project from one of Xcode’s built-in templates, using the same bundle ID as your main app.
-
Add some code to make sure that it exercises all the cases you care about. For example, if you’re using Swift / C++ interoperability, add some C++ code and call it from Swift, just to make sure you have the basics working.
-
Build that and test it locally.
-
Then submit that to App Store Connect.
If you have any problems getting that to work, I’d be happy to help with those. However, I suspect that you won’t.
Once you’re done, you have a working project created by Xcode and a non-working one created by your third-party tools, and you can compare the two to see what’s different. And once you know what’s different, you can do two things:
-
Fix the Xcode project to see if that fixes your submission issue.
-
Work backwards to work out how to fix it in your third-party tools.
Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"