Darwin Build Environment Help Center
Windows 11
Builder v3.74
Swift 6.1.2
iOS SDK 18.5
Hi Pierre-Marie,
I've been getting this error for months now and updating the builder and SDK don't seem to help. The app compiles without problem it's only when I submit it to the appstore connect that I'm getting this error:
ITMS-90426: Invalid Swift Support - The SwiftSupport folder is missing. Rebuild your app using the current public (GM) version of Xcode and resubmit it.
I would really appreciate your help.
Thank you!!
Anthony
This error happens when your minimum build target is set too low, i.e. to a generation of devices that didn't have any Swift libraries in the base system. Raise your minimum build target (on the Unity side, iOS project settings) and it should fix the problem. Let me know if that was not the case.
Thanks for your fast reply!
Do you mean the "Target Minimum iOS Version" ? it's set to 17.0 at the moment. Which is fairly recent (released 2 years ago only) I just tried 18.0 and got the same error. Could it be something else?
17.0 is okay - no need to change it. The reason must be elsewhere. Does your project include precompiled binaries or frameworks ?
I just tried with 18.5, and did a full rebuild. Same error.
In term of binaries, I'm using one call libOVRLipSync.dylib for lip syncing and also my own .mm script to change some audio recording/playback settings
on the libOVRLipSync.dylib, the import settings are set like this:
Platform: iOS
"Add to embedded binaries" is checked
"Load on startup" is checked
There is also a libOVRLipSyncShim.a with these settings:
Platform: iOS
"Add to embedded binaries" is unchecked
"Load on startup" is unchecked
I tried another build where I unchecked, the settings:
"Add to embedded binaries" and "Load on startup"
Got the same error.
It is possible that this library libOVRLipSync.dylib was compiled from legacy Swift code for an old target. You can check if it’s the case by using "otool" on it to display its Mach-O load commands. If that’s the case, see if you can obtain an updated version.
libOVRLipSync is actually deprecated and there is no update for it. I removed it to replace it by something else later. The ipa got pushed without issue to Apple Connect so it's clearly related to that lib.
But, a colleague compiled the IPA with the lib again using XCode and sent it to the store via XCode too. The IPA passed!
So yes that lib is an issue while compiling with ios builder , but looks like XCode still does something different that makes it work.
Anyway I will still remove it and add a different lib to handle lipsync just so I can compile using IOS Builder as I don't have a Mac myself.
Interesting.
Well, technically, what would be sufficient would be to do just what the App Store says, and add the ~150 Mb of Swift runtime files to your app (and the very version your library was compiled with). The upload tool used to do that long ago, but I deprecated this feature because now all devices are able to run at least Swift 5, and libraries that use older versions have become rare.
Whatever, I believe getting rid of a deprecated library is a sensible choice here. You would have had to do it sometime anyway, sooner or later.
That makes sense. Thanks for your support PM! Appreciated
You're welcome.
Moderators: Pierre-Marie Baty