So I just upgraded my MacBook to Lion and setup all my prov profiles and Xcode 4.2.1. I followed the instructions here: http://www.weston-fl.com/blog/?p=2442 to upload my app to the App Store. I have iTunes Connect all ready for my app update – it says waiting for upload. When I try with organizer to validate or submit my archive, it says an SSL error has occurred and a secure connection to the server cannot be made. Has anybody ever seen this error before? I'm pretty stumped.
Ios – Xcode produces an SSL error when attempting to upload app to App Store
app-store-connectiosssluploadxcode
Related Solutions
This problem happens when xcode-select developer directory was pointing to /Library/Developer/CommandLineTools when a full regular Xcode was required (happens when CommandLineTools are installed after Xcode)
Solution:
- Install Xcode (get it from https://appstore.com/mac/apple/xcode) if you don't have it yet.
- Accept the Terms and Conditions.
- Ensure Xcode app is in the
/Applicationsdirectory (NOT/Users/{user}/Applications). - Point
xcode-selectto the Xcode app Developer directory using the following command:
sudo xcode-select -s /Applications/Xcode.app/Contents/Developer
Note: Make sure your Xcode app path is correct.
- Xcode:
/Applications/Xcode.app/Contents/Developer - Xcode-beta:
/Applications/Xcode-beta.app/Contents/Developer
More than one binary may be uploaded to App Store Connect for the same version, if the the Build number is increasing for each build uploaded to iTunesConnect. The build number just has to be unique (and higher) for each binary that is uploaded (select the Target, then Xcode -> General -> Build, see the picture below).
For example in the image below the build uploaded has version 3.1.4 (3.75 in the older image) and the build number is 1. Thus, after uploading this image increase the build to a minimum 2 or higher. Then this binary may also be uploaded to App Store Connect as it's a later build according to the build number.
The version notes the release version of the app your releasing to the user. The build number remarks the final build of the binary uploaded to the store, i.e. after many bug fixes.
After Xcode 9 you are not able to upload a new build (for the same version), if there is a previous build with the same build number in the store. So, check your build number and increase if not certain.
EDIT: It's more correct to use 1, 2, 3, 4, etc. for the build number, but the version number has to be increasing, 1.0 -> 1.1 -> 1.2 etc. The build number has to be higher than what was submitted previously for the same version number, if not an error is posted. So, if a new binary is submitted that has version 3.75 and a build 1 has already been submitted, then next build shall be 2 or higher, but the version can still remain 3.75.
New updated and the recommended way of having the build numbers serial:
The older image to match the one below:
After a new binary is uploaded and processed (~5-20 min processing time, if it doesn´t show up upload again and wait), then you can select the new binary and submit it for review. In the picture below you may see the old and the new binary listed in App Store Connect in the Build section of the current App version (you click the plus sign). Then the new binary is selected -> Saved -> Submit for Review. (Sometimes an error comes when submitting, then just try after a few mins or upload a new binary).
For those inclined to do this automatically with an Xcode script, here is a description of making an automatic script for updating Build numbers Better way of incrementing build number?
Best Answer
I had the same error message and I tried using Application Loader, double checking password and account information, logging in via Safari, quitting Safari, etc. What eventually worked for me was simply restarting my computer.
Very frustrating, but hopefully this helps someone else save 15 minutes of time.