XCode 5 hangs with a timeout error when validating/uploading a "ready to be uploaded" app

Question

I've been developing and uploading apps for some months. Whenever they needed being uploaded to the app store, I could do it without problem, but now, I'm stuck with one that doesn't want to be validated/uploaded. XCode says "the request timed out" after MANY minutes with a spinwheel on screen.

The differences between my old updates to the app store and the one I'm trying right now are:

-Xcode 4.X before, Xcode 5 now.

-I had to recreate the app store certificate/provisioning profiles, because they just expired.

-I inherited this project from other coworker (not here anymore) and maybe my "developer profile" is somewhat conflicting with some certificates, etc... (Still many dark areas for me).

I've kind of tried "everything". Erasing provisioning/profiles, closing Xcode, resetting, cleaning my project. But no luck. My current Xcode 5 is able to compile my app perfectly, I'm even able to select the distribute option before uploading (the app is ready to be uploaded onto itunes connect), I even login with my client credentials onto itunes connect, I can even select the correct provisioning profile (app store profile, not a developer one), but no luck:

If I choose to upload or validate, Xcode just complains with some kind of "dull" timeout error.

Any hints? Any way to debug what happens behind the curtains?

Greetings, I'm at a loss.

EDIT: Apparently, the timeout failing event appears in the validation process. If I try to upload, the status log says "Failed Validation". If I try to validate, obviously there's also a "Failed validation" error. Where can I find some log to see what part of the validating process is failing?

Answer 1

Well, apparently: "Problem solved".

After 2 boring days trying to upload my app (via Xcode 5, and via Application Loader), I've discovered that Apple upload servers seem to be overloaded (unless a better explanation arises).

I'm in Europe, and from 9 to 14 h my app was ALWAYS rejected. But once I tried it after 16h, the upload and validation processes worked like a charm (both with Xcode 5 and with Application Loader).

Why this? No idea, but I didn't change anything in my upload process, so it's sad, but the solution is: "Have patience, and wait to upload your app on a time slot where Apple upload servers are not overloaded". The sad part is: No one knows WHEN is that time :)

Answer 2

I solved it by switching Internet provider.

I simply connected my laptop to my iPhone via Personal Hotspot and used LTE network to upload the app.

It worked for me twice.

Answer 3

for Xcode 13 and Mac OS Big Sure

1. Install the "Transporter" app from the MacOS app store.
2. From Xcode's organizer, select your archive and press "Distribute App"
3. Instead of "Upload", select "Export" and proceed as usual.
4. Drop the exported .ipa into the transporter and press "Deliver".

Answer 4

Faced the error many times, not sure why.

Try this

1. Export the ipa after the archive

1. Add and upload in Transporter

I get 100% success in uploading and feel a little quicker than Xcode's upload.

Answer 5

I actually called Apple Developer Support about this and they solved the problem!

It turned out that my recovery email address in my Apple ID (not the main email address but the recovery one) was not verified. They had me go to http://appleid.apple.com, login with my Apple ID, and then go to the 'Password and Security' section (on the left).

After answering my security questions I was able to resend the verification email, and once verified I was able to log in on Xcode straight away!

Answer 6

In my case I changed the dns server from my provider to the google dns server (8.8.8. and 8.8.4.4).

I think you can try any other, if your providers dns or what ever doesn't work

Answer 7

I have the observation that with Mavericks and App Nap enabled, a hidden Organizer window within XCODE will cause the network connection to be dropped.

Even if the window is occulated (hidden) for just a second).

Make sure the window is always visible and the problem does NOT occur.