Application Loader throws error communicating with the iTunes Store
I am trying to use Application Loader to upload a binary as is now required. I can pick my app fine and everythings works up until the point when I hit send. The application loader tries to authenticate with iTunes for about 10 seconds and then throws the error "Error communicating with iTunes Store".
Any idea how to fix this or how to get more info about the error? I've tried this several times with two different apps. One an update and one new.
Are you using little snitch, or some other firewall? I had to stop little snitch to get it to work, despite allowing all connections to Application Loader. It is clearly doing something dodgy. I think this new way sucks, so much more work to get an update up. Thanks a lot Apple!
Also, the first time I got it to work it kicked me off my connection.
I used Application Loader from another Mac and it worked! Before uploading I was asked if 'I authorize remote connection or call with Java' I responded YES.
Note that Application loader is a Java Applet. So I went to Java Preferences-Security and I noticed that a main difference between both Mac.
I noticed that the signed content http://real5.sysfx.com has an expired certificate but in the mac from where I was able to upload succesfully has a valid certificate for the signed content.
Hey guys,
I resolved the situation. Here's the deal. I just got a new MacBook Pro. There are two user accounts on it. One is the account the Mac was setup with and I rarely use that account. The other account was imported from my other mac so it has all my apps, documents, etc and it's the one I use all the time. Application Loader wouldn't work on this account. When I logged into the user account that I never use, application loader worked from there! I talked to a Mac Genius I know and he suggested running the password reset utility and resetting the disk permissions to get application loader to work on my main user account. I haven't tried this yet, but I will when I need to do a new upload.
Hey guys,
I resolved the situation. Here's the deal. I just got a new MacBook Pro. There are two user accounts on it. One is the account the Mac was setup with and I rarely use that account. The other account was imported from my other mac so it has all my apps, documents, etc and it's the one I use all the time. Application Loader wouldn't work on this account. When I logged into the user account that I never use, application loader worked from there! I talked to a Mac Genius I know and he suggested running the password reset utility and resetting the disk permissions to get application loader to work on my main user account. I haven't tried this yet, but I will when I need to do a new upload.
Good point!
As you Application Loader does not work with the imported account from my old MacBook Pro. I just repaired the disk permissions and I will see with the next app updload.
I just uploaded a new binary and I confirm that resetting the permissions did fix my communication error. Hopefully this helps someone else.
If you're not familiar with the Password Reset Utility note that the Password Reset utility I used is found on the Snow Leopard Install disk. You have to boot from the disk to use it.
I just uploaded a new binary and I confirm that resetting the permissions did fix my communication error. Hopefully this helps someone else.
If you're not familiar with the Password Reset Utility note that the Password Reset utility I used is found on the Snow Leopard Install disk. You have to boot from the disk to use it.
I try login as new user account, I did repaired the disk permissions and Password Reset Utility as well ... but still the same error msg come out:
error communicating with the iTunes Store
expert pls helpppp
If that didn't work, open settings panel, goto user account and create a new admin account, transfer the compiled binary over to the other account somewhere and then login to that account , open the application loaderfrom there and sign in
You know the rest.
(this would be considered a temp solution) until you figure out why your normal Mac user account won't work).
If that didn't work, open settings panel, goto user account and create a new admin account, transfer the compiled binary over to the other account somewhere and then login to that account , open the application loaderfrom there and sign in
You know the rest.
(this would be considered a temp solution) until you figure out why your normal Mac user account won't work).
yes, i just try create a new admin account, copy the app file to new folder and compress it then sign in application loader , but still the same error
yes, i just try create a new admin account, copy the app file to new folder and compress it then sign in application loader , but still the same error
Try turning off your Firewall in Settings->Security. If that doesn't work, try another WiFi network in case the one your on has some weird firewall settings.
he guided me to use console.app to monitor all background process messages. finally I realized that is because of my java version are outdated. after I upgraded and fixed my java, everything fine now and can upload to appstore.
he guided me to use console.app to monitor all background process messages. finally I realized that is because of my java version are outdated. after I upgraded and fixed my java, everything fine now and can upload to appstore.
Hi guys,
i'm still seeing this "error communicating with itunes store" error message after running the disk repair permission and reinstalling java.
It's definitely an issue with a file pointer with Java. This is my console output.
Code:
10-10-11 9:02:35 AM Xcode[144] Error:
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.webobjects._bootstrap.WOBootstrap.main(WOBootstrap.java:71)
Caused by: java.lang.NullPointerException
at java.io.FileInputStream.<init>(FileInputStream.java:103)
at com.apple.transporter.util.ConfigurationUtil.getConfigurationFileStream(ConfigurationUtil.java:84)
at com.apple.transporter.util.ConfigurationUtil.loadPropertyDefaults(ConfigurationUtil.java:30)
at com.apple.transporter.Application.main(Application.java:112)
... 5 more
I've also tried showing the path of the archive file in finder and changing the permissions to 777.
Any other ides?
Hi guys,
i'm still seeing this "error communicating with itunes store" error message after running the disk repair permission and reinstalling java.
It's definitely an issue with a file pointer with Java. This is my console output.
Code:
10-10-11 9:02:35 AM Xcode[144] Error:
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.webobjects._bootstrap.WOBootstrap.main(WOBootstrap.java:71)
Caused by: java.lang.NullPointerException
at java.io.FileInputStream.<init>(FileInputStream.java:103)
at com.apple.transporter.util.ConfigurationUtil.getConfigurationFileStream(ConfigurationUtil.java:84)
at com.apple.transporter.util.ConfigurationUtil.loadPropertyDefaults(ConfigurationUtil.java:30)
at com.apple.transporter.Application.main(Application.java:112)
... 5 more
I've also tried showing the path of the archive file in finder and changing the permissions to 777.
Any other ides?
ok - resolved my issue as well.
I reinstalled xcode and then it gave me a different error about permissions on my home directory. I went into terminal and "chmod 777 <dir>" and then build, archived and tried uploading again and it finally worked. Although it hung up xcode and I had to force quit it, I checked out itunesconnect and says it did receive it.