My build is successfully uploaded but Not shown on testflight due to below issue sent by apple.
App detail : I am having iPhone app in React Native and watchOS app in swift langauge.
Xcode version : 11.3
Issue reported by apple -
ITMS-XXXX: Invalid Swift Support - The SwiftSupport folder is empty. Rebuild your app using the current public (GM) version of Xcode and resubmit it.
I searched and tried lot of things but nothing work. Also tried below link
Updated Answer of my query : I have resolved the issue by adding the required framework in watchOS folder of Swift Support. May be its Xcode issue which is creating empty folder for my watchOS. Followed below steps
- Copy watchOS lib swift file from this path " /Applications/Xcode.app/Contents/Developer/ToolChains/XcodeDefault.xctoolchain/usr/lib/swift/watchos" Or You can also get framework from your previous watch build which is successfully uploaded
- Paste the copied library in below location
2.1 Create Archive of your app -> Right click on selected build and select show in finder -> show package content -> Swiftsupport -> watchOS/"Paste here"
2.2 Paste those frame in framework folder also by following the below path Right click on selected build and select show in finder -> show package content -> Products -> Applications -> right click on ipa file -> show package content->Watch->Right click on your watch app -> show package content -> Frameworks/"Paste here"
- Set "Always embedded swift standard libraries" to yes in builsetting of you main app target and watchkitapp (Not in extension)
Optional step
if your SwiftSupport->iPhoneOS folder is also empty then just create new swift file to your objective c code it will ask for bridge rest it will do for all required things (No need to connect this file with any objective c just add it to project)
My work-around for this issue is:
Now you can submit without getting that error.
I encountered this issue on a React Native project.
I tried a lot of the most popular solutions e.g. editing Build Settings and none of those worked for me.
This is a very annoying issue and happens whenever you used third-party tools to make the application rather than Xcode. To fix this issue you must be calm first and need to follow these steps, I encountered in the same situation and after that, I wrote myself some scripts to solve that issue.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With