I am trying to upload my app to the app store. I can archive my app and successfully upload to App Store Connect, however, it keeps getting rejected with the following error message:
Dear Developer,
We identified one or more issues with a recent delivery for your app, "Retainer Tracker" 1.0 >>(8). Please correct the following issues, then upload again.
ITMS-90424: Invalid Swift Support - The SwiftSupport folder is empty. Rebuild your app using the current public (GM) version of Xcode and resubmit it.
Best regards,
The App Store Team
I've tried a bunch of diffrent fixes I've found online but still can't get it to work. Can anyone help?
The basic reason is your application using swift and your swiftsupport folder is empty. Let's move in detail
If your application using Xcode to make .ipa file and there is no third-party IDE involve to create Xcode project, you can fix this issue by upgrading your Xcode
If you are using some other IDE to make the Xcode project then please follow that link. I already give the answer to this question. Invalid Swift Support - The SwiftSupport folder is empty
The problem occurred right after I added a specific Swift Library
Doing the following fixed the issue in my case
Go to Targets > YourApp > Build Settings
Under Packaging:
Defines Module: Yes
Under Assets:
Always Embed Swift Standard Libraries: Yes
ITMS-90426: Invalid Swift Support - The SwiftSupport folder is missing. Rebuild your app using the current public (GM) version of Xcode and resubmit it.
For us, our CICD pipeline was using an Ad-Hoc Provisioning Profile to distribute the ipa build to Testflight/AppStore.
We fixed this by using an App-Store Provisioning Profile instead.
Related
I'm getting this error when opening VS Code. Does anyone know what it means? I've done some research but didn't get any relevant information :(
I've tried creating a workflow to see if the error disappeared, but it didn't.
It seems that react native is asking for a workspace to start but is it asking that in the first place? Can I disable react native from running when opening VS Code?
The folder opened when the screenshot above was taken was the folder it opens by default, I believe it's the mac "home" personal folder, and I have a folder called "git" inside of it, with all projects.
Given the date of this posting (2023-02-07), you're probably on version 1.10.0 of the extension. This sounds like this bug report in the microsoft/vscode-react-native GitHub repo: [Bug] Extension activating when it shouldn't #1891.
A fix is coming in version 1.10.1.
But it is taking some time and has not been release yet at the time of this writing 2023-01-31:
we're facing some problems in the last release process, recently we're waiting for new publishing PAT access to republish 1.10.1 again, maybe it will publish on marketplace on next week. We have nightly version for extension in marketplace as well, maybe you can use it now.
For now, you can try installing the nightly version.
Also, note from the extension's readme documentation:
Before going any further make sure that you:
have a working React Native environment.
have the emulator utility available in your PATH if you're developing Android applications.
[...]
Got it, this annoying log came from React Native Tools extension. They specify the requirements in the docs:
In my case, I don't have a specific React Native environment or the emulator PATH is not right.
I want to submit app on AppStore, My app is having swift speech SDK library, and project is in Obj C, Whenever I am trying to upload my build, I am getting this error,Invalid Swift Support - The SwiftSupport folder is missing. Rebuild your app using the current public (GM) version of Xcode and resubmit it.
Doing Embedded Content Contains Swift Code -> YES in target setting, not working.
Incase your project is having swift classes /library:, Please ensure below settings are as follows:
Project/Target settings -> build Settings
1. Defines Module -> YES
2. Always embed Swift Standard libraries -> YES
It solved my problem.
In my case was because I was using an Adhoc provisioning profile instead of a production one when I was trying to deploy to the App Store Connect.
I am using Application Loader to upload my .ipa files (created with Adobe AIR v18) to iTunesConnect.
It's been working fine for months, but today I received two new errors:
The u option must have a non-empty value.
The password must have a non-empty value.
Can anyone shed some light on the issue?
I upgraded to Xcode 7.1 and that solved the problem!
Note: Xcode 7.1 comes with Application Loader 3.3.
You have 2 solutions:
1) Update your Xcode to 7.1 (but since you are not coding natively, use the solution #2 below)
or
2) Download and use the Application Loader v3.1 (Download link: https://itunespartner.apple.com/en/apps/tools ) to submit your IPA
Apart from low-belly's answer you can try to use XCode's built-in upload feature. If you go to the Organizer, just click on Upload to App Store:
This solved the problem for me in XCode 7.0.1.
Xcode 7.1 was downloading too slow (more than 4GB) and the update failed every time, so for now I downloaded the Application Loader 3.1 from iTunes Connect and it worked fine.
To download it you login into iTunes Connect -> Resources and Help -> click on View Tools (under the title Other Resources at the bottom of the page) and there is the download link.
I got the same error last night. Fixed it by signing out of Application Loader (3.6) and logging back in.
I got the same error with Application Loader 3.2. Submitting with Application Loader 3.0 (bundled with Xcode 6.2) or 3.1 (bundled with Xcode 6.4) solved the problem.
I am trying to upload my mac xcode project on mac app store, but each-time it shows invalid binary status. I have checked many answers in stack overflow as well. But issue is not resolved. That's why I am posting new question here
I tried some options -
1.. Removed all warnings
2.. Checked by quiting xcode, cleaned container folder
3.. provisioning profile is valid, and matching to the bundle id. I checked by deleting all certificates and provisioning and install required ones again.
4.. Created new provisioning profile and certificate 3 times. But same issue
5.. uploaded 3 times directly through xcode 5.1.1, and 2 times by Application Loader. But showing Invalid binary for all.
6.. App is properly sandboxed with proper permissions
Any idea. Thanks in advance.
Invalid Binary
When you get this error, apple will send you a mail with reason. In my case this was the email:
Dear developer,
We have discovered one or more issues with your recent delivery for
"App-Name". To process your delivery, the following issues must be
corrected:
App sandbox not enabled - The following executables must include the
"com.apple.security.app-sandbox" entitlement with a Boolean value of
true in the entitlements property list. Refer to the App Sandbox page
for more information on sandboxing your app.
App-name Mac.app/Contents/MacOS/app-name
Once these issues have been corrected, you can then redeliver the
corrected binary.
Regards,
The App Store team
Also, you shouldn't be using XCode 5.1.1 itunes connect has changed a lot now.
Please update to 6.0.1 or use the new beta version 6.1
Xcode 6.1 GM seed for OS X Yosemite
hope this helps
I am trying to install my application extension on my iPhone device, but I am getting the following error:
This application or a bundle it contains has the same bundle identifier as
this application or another bundle that it contains. Bundle identifiers must be unique.
The app container have the bundle id: com.companyName.AppName and the bundle identifier for the app extension is com.companyName.AppName.WidgetApp.
I have tried to sign the extension with the same provisioning, also I have installed a different AppID from the apple developer site and new provisioning profiles for the App Extension and Also tried to set the signing for the extension Widget to Automatic but still the same error and the app cannot be launched on the device.
What should i do in order to install my application extension to the device?
Here are screenshots of my General Tab for both my app and the Extension:
App:
Extension:
Thank you.
Executing a clean command worked for me.
This is done through the XCode menu item; Product > Clean or SHIFT + COMMAND + K
I had this exact problem and it was due to having a duplicated framework included in the build. I had included both a test and non-test version of the same dynamic framework. Once I removed one, the installation proceeded as expected.
I'm sharing this in the hopes that it will help someone else in case they encounter this particularly obscure situation.
In Swift :
If you installed pods then you have to change bundle identifier as org.cocoapods.podName in general identity. Make sure deployment target of all pods should be same to the project’s deployment target.