Application Loader (Apple) stuck on "Sending API usage to iTunes Connect"

Question

I am submitting an iOS app to the App Store using Application Loader, however, it never gets past the "Sending API usage to iTunes Connect" stage. There is no error - this stage just doesn't complete.

I have verified that the Mac is connecting to the internet (I can visit websites). Also, the app is tiny (6MB) so this can't conceivably just be a long upload. I've tried leaving this for 20 minutes.

The background to this is that I developed in Flash CS5 on a Windows PC, built it for distribution there, and now on the Mac I am loading the final file into Application Loader to submit it. It verifies/validates the file just fine, but won't go beyond this point.

Any ideas anyone? Perhaps it's a network issue?

Solution 1

I had this problem when behind a firewall. I got around it by going to Xcode > Contents > Applications > Application Loader > Contents > MacOS > itms > java > lib - Open net.properties with TextEdit and change the line # https.proxyPort=443 to https.proxyPort=80. This enables the application to use the HTTP port for HTTPS. Worked straight away after this. Hope this helps.

Solution 2

You can solve this with a different approach using your iPhone. Disconnect ethernet internet cable connection (if you have one) and/or switch off wifi connection on your mac. Switch off your iPhone's wifi connection so G3 or G4 is active and turn on personal hotspot. Connect your iPhone with a usb cable with your computer and check in System Preferences -> Network if you're connected to internet via usb with iPhone. Start delivering your app with Application Loader program on your computer via your iPhone's internet connection. And yes you will cross the “Sending API usage to iTunes Connect” barrier and you will be able to upload the package to the iPhone store. At least I was!

Solution 3

If your Mac is has both a WiFi and an Ethernet connection, try turning off WiFi. That solved the problem for me (this time anyway).

Comments

[radnoise]

But that line is disabled, right? The '#' is a comment marker. Changing it shouldn't have any effect. So are you sure that actually is what solved it?

[JT Mudge]

user2957268 had it correctly as a workaround. Except that you need to remove the # as radnoise indicated. old line: # https.proxyPort=443 new line: https.proxyPort=80

[Olivier de Jonge]

This is a working solution if you remove the # too indeed, so I edited it to let it be right.