{Detailed Article} Submitting a New App Version on the iTunes Store for iOS 13 and beyond
By: Tejeshwar Singh Gill
Tags: Submission, Programming, iTunes, Itunes Connect, iOS

Tip: The upload can be pretty long. And sometimes it’s not working. When Xcode displays an error, the problem can come from you, but it can also come from the Apple servers. In this case, you can’t do anything but repeat the upload until it works. Sometimes slow internet also hampers the upload process.

Now you need to wait. It can take some time before your build is actually visible on iTunes Connect.

If this doesn’t work, read on for some solutions to likely problems.

If uploading in Xcode doesn’t work

If you see “Cannot verify client,” “Not authorized,” “This action could not be completed,” or other errors not related to signing and provisioning profiles, then you’ve got a problem with Xcode’s upload function.

Usually the problem is on the other end, so wait and try again. Use the time productively: Grab a cup of coffee, go for a walk, or do a few push-ups.

If you want do something, here’s a list of things to try:

Make sure you’re not using a beta version of Xcode. Disable any virus scanners. Restart Xcode, clean, and rebuild. Hit “Validate” first, then try to upload again. Use Xcode to generate an archive, and then use Application Loader to upload it. Choose “Save for iOS App Store Deployment” to get Xcode to generate the archive. In Application Loader, select “Deliver You App,” and choose the IPAfile that Xcode generated.

Using Application Loader to upload the IPA seems to work for most people when Xcode times out.

Archive menu option grayed out

If you can’t create an archive in Xcode, usually it’s because you have the destination set to the simulator. Switch to an iOS device (it should work even if you don’t have one connected).

Another cause for the grayed-out archive option is that it’s disabled for your scheme. Under the Product menu, choose “Scheme,” then “Edit Scheme…” With “Build” selected on the left, make sure that the checkbox for “Archive” is enabled.

Signing and provisioning errors

Xcode takes care of most signing and provisioning now, but issues still crop up. Eventually you’ll have to fight with a provisioning or signing issue, so it’s worth reading Apple’s “Maintaining Your Signing Identities and Certificates” docs so you know how it all works.

The error messages for these errors are often misleading. A quick trip to Apple’s Troubleshooting list is usually more productive than trying to reason out the issue based on the message.

If your error isn’t listed there, then try Google. Sometimes errors crop up for everyone for a while, like when Apple’s WWDR intermediate certificate expired recently.

Status as “processing”

Sometimes after uploading a build, the status will change to “processing,” and you won’t be able to select that build for your app version. Usually this step only take a few minutes at most. But once in a while a build will seem to randomly get stuck at this stage. Even on my tests while writing this article I had one build upload that decided to take an hour to process.

Usually the best thing to do is wait it out. It should only take a few hours at most. If it takes more than 24 hours, contact App Store Connect support.