itunesconnect using application loader behind a firewall

Question

I was trying to upload the app store build zip file of my app to app store.

When using behind my office firewall, the TCP/IP connection failed.

I need to k

Answer 1

I had the same problem.

The Application Loader Guide shows the range of IP addresses and ports that need opening.

After following the document I was able to successfully submit a binary for approval.

https://help.apple.com/itc/transporteruserguide/#/apdATD1E112-D1E1A1303-D1E112A1126

Answer 2

Go to Preferences, Advanced, select DAV only.

This will use port 443 (aka HTTPS) for uploading.

There is no way the company will open those ports for me ;p

Answer 3

Try the build and archive option under the build menu and submit it that way. It should work. That way you don't have to use the application loader. And you won't need to zip it either.

Answer 4

I came across this issue too, when using Fastlane to automate the upload of binaries to App Store Connect.

The error message was saying that connection timed out.

The reason ended up being that Fastlane's Ruby script was using a java program in the background (visible from nettop), which ignored the proxy settings set in the bash profile or in my case .zshrc

To fix this, add this line in your bash profile:

export JAVA_TOOL_OPTIONS='-Dhttp.proxyHost=xx.xx.xx -Dhttp.proxyPort=xxxx -Dhttps.proxyHost=xx.xx.xx -Dhttps.proxyPort=xxxx -Dhttp.nonProxyHosts=xxx'

This will force the java runtime to use your desired proxy, and in my case, fixed the issue of fastlane failing to upload builds to App Store Connect.

Hopefully that helps someone

Answer 5

In your mac - go to security and privacy - firewall option - click on '+' icon and add 'Application Loader' to that list.

Magic - Uploads works now.

Answer 6

With the Application Loader v2.8 I tried to set the delivery mechanism to just DAV but that didn't help on Mountain Lion. Seems the Java-Backend of the Application Loader does not pick-up the proxy settings of the System. You you have to hack them in /Developer/Applications/Utilities/Application\ Loader.app/Contents/MacOS/itms/java/lib/net.properties.

See http://blog.schneidexe.de/2013/08/apple-application-loader-und-proxy.html for more details.