Very slow application loading / error message - application loader

Question

I have been using the application downloader since one year. But over the past few months, I have problems with the application loader.

When I click the submit button in the application loader, it shows "Authentication" in the iTunes Store. This authentication step takes about 5 minutes. After that, it shows the connection with the iTunes Store for 10-15 minutes, and then causes a communication error:

Communication Error. Please use diagnostic mode to check connectivity. You need to have outbound access to TCP Port 443. An exception has occurred:Operation timed out. Could not connect to Apple web service. An error occurred while connecting to the transport host https://itmsdav.apple.com: Operation timed out. Could not start delivery: all transports failed diagnostics. 

I tried googling and many told me that there would be problems with the firewall / Java. I checked it out. The firewall is not enabled or there are any problems with another Java application. This is just a problem with my application loader.

I tried to download the application from my college and it works great there. But in my house it always works.

The only difference is that in my college I just plug in my Ethernet cable and connect to the Internet, and in my house, as an ADSL modem that needs to establish a PPP connection. I also found out that the application loader sends UDP packets.

Will there be a problem in my ADSL modem? Does anyone have similar problems?

Answer 1

Make sure you are not using Charles proxy (or any proxy software). I was bitten by this and took a couple of hours before I realized that Charles swallowed all the requests :)

Answer 2

I tried many solutions, such as using port 80 to connect https, but none of the solutions worked for me.

 #https.proxyPort=443 

to

 https.proxyPort=80 

Changing the port did not work for me.

After many attempts at many solutions, I tried to download the application from two different instances of the application loader, and it worked like a charm.

I have two different versions of the application loader on my machine, one of which comes with Xcode4, and one with Xcode5. It always works if I download an application from two instances at the same time.

Answer 3

The problem is that Application Loader uses Java, and Java does not inherit Mac proxy settings. The solution is to specify proxy information in Java.

If you are on Mac OS before 10.7.5 (more or less), just find the Java Preferences app through the limelight. If not, this SO question determines how to do this.

Answer 4

In my case, I used Charles Proxy. So, I closed Charles Proxy and was able to download.

Answer 5

I had the same problem while downloading my first application. After I tried so many changes, nothing worked for me.

Finally, I changed the version of Application Loader. It. Worked well for me. I used Application Loader 2.5.2.

Answer 6

I still have this problem despite trying all the suggestions in the stream. Launching the application loader 2.9.1; Java version 7 build 1.7.0; Yosemite beta 4; Xcode 5.1.1. Also tried all the settings in the General / Network Settings section of the Java Control Panel. All firewall ports are open for outgoing traffic.

Any further suggestions appreciated ...

Answer 7

Adding this line to my bash_profile worked for me

 export _JAVA_OPTIONS="-Dhttp.proxyHost=my-proxy-server -Dhttp.proxyPort=1080 -DsocksProxyHost=my-socks-server" 

• Xcode 5.1.1 (5B1008)
• Yosemite Beta li>
• java version 1.6.0_65

Answer 8

After many unsuccessful attempts, I went to System Preferences → Network → Proxies and turned on Auto Proxy Detection. Worked like a charm afterwards.

Answer 9

If you didn’t mention Charles proxy and the download failed “out of nowhere”, just try changing your network and rebooting your Mac. In my case, the implementation of these two worked, just changing the network did not work.

Answer 10

Go to "System Settings → Network → Advanced → Proxies → Unselect Proxy" if something is selected.

Note. If you want to double-check it, open the Apple developer account in a browser. If it is loaded, this error will not appear.