I was about to upload an app to iTunes connect,but the application loader has been stuck at the stage of "Authenticating with the iTunes Store" and pending for almost an hour.Network is fine and I have never seen this before.Has anybody encountered this kind of issue? what is the solution?thanks in advance.
25 Answers
I had this problem when behind a firewall.
I got around it by editing:
/Applications/Xcode.app/Contents/Applications/Application\ Loader.app/Contents/MacOS/itms/java/lib/net.properties
If you do not find net.properties
in above mentioned path then try, as it is changed now.
/Applications/Xcode.app/Contents/Applications/Application\ Loader.app/Contents/itms/java/lib/net.properties
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.
To be honest, this may not be an answer but it really worked for me.
- I launched
Application Loader
and started submitting. While sumbitting was going on, - I launched
Organiser
and selectDistribution over archiver in Xcode
as well and started uploading concurrent.
They worked together and 2nd one completed the submission.
Just my experience.
I tried many solutions like using port 80 for https connection but none of the solution worked for me.
https.proxyPort=443
to https.proxyPort=80
Whenever I face this issue, I upload application from two different instances of application loader and it works like a charm.
I have two different versions of application loader on my machine, one came with XCode4 and one came with XCode5. It always works if I upload application from two instances simultaneously.
I was quite frustrated by this - not only by the problem itself but the uncertainty till when I need to wait to call it "It won't - try again." - at which point I will quit the Application Loader app, re-package my ipa file and try again. Probably with a port change to net.properties file. But it didn't always work the same way as it did last time. So I am writing it here, mostly for the sake of myself!
I was about to just call another day thrown when this worked, almost like a charm:
1) Open file. Applications > Xcode > Contents > Applications > Application Loader > Contents > MacOS > itms > java > lib - net.properties
2) Change the line:
# https.proxyPort=<whatever>
to
https.proxyPort=80
Make sure that you do not uncomment # https.proxyHost=
- just leave it as shown (commented).
3) Start Application Loader. Follow usual steps and start uploading your ipa using Send command.
4) If it seems to be getting past "“Authenticating with the iTunes Store” in reasonable time (say 10 minutes at which time my patience ran out) - you are lucky. Go sleep or hang out.
5) Launch Xcode Organizer. Select your archive and click Distribute button. It will show slanting progress lines for couple of minutes. If it doesn't stop, kill Xcode and retry.
6) After about 2 slant minutes, the blue solid progress will appear, and there flies your "Flappy Bird"...! (mine was neither Flappy nor Bird)
(Keep the Application Loader alive, just for the sake of having it around, I don't know if it's useful anymore, but I am just superstitious)
- Workarounds apart, this is something Apple must fix before releasing iOS 8 or iPhone 6. Seriously. If they don't, I am not wasting my $100 next year.
(Or - will this bug be still around to prevent those "Flappy" clones from flooding the app store, forever?)
Tested with xCode 5: In my case nor organizer or application loader worked: they got stacked in “Authenticating with the iTunes Store”.
I solved it sending the app by application Loader, and when it got to the “Authenticating with the iTunes Store” I opened the organizer and upload the app: application Loader and organizer sending the app at the same time.
It seems that something is going in my router port configuration and my computer can not receive the answer from itunes store saying that authentication was successful. Maybe the process is this way:
1- Application loader request authentication.
2- Itunes store authentication is done but application loader never receives the answer. [But it is authenticated anyway!]
3- Organizer sends the app because it is already authenticated by application loader.
You may give a try to application uploader
. Yesterday me too faced this problem and even application upload didn't work for me then I tried this:
For uploading it via XCode:
Step1: Firstly Validate your archive file by clicking on validation button of Organiser.
Step2: Then Upload it to App Store via Oraganiser. By clicking on distribute and then first option and so on.
it really worked for me
If validation is successful while uploading through organiser then it must be network issue. Application loader uses some specific ports including port 443. If any of those ports are blocked by your internet service provider or on your local network then application loader can stuck. Certain applications also block these ports. If you are running Skype close it. If it does not work then this solution worked for me finally. Make modifications in net.properties file. You can access this file by going to Application folder via terminal.Then move into Xcode.app with cd Xcode.app next
Contents with cd Contents next
Application Loader.app with cd Application\ Loader.app next
Contents/MaxOS/itms/java/lib
Now you find net.properties.
Now write sudo pico net.properties and add following lines in the file
https.ProxyHost=
https.ProxyPort=
https.ProxyUser=
https.ProxyPassword=
Now launch application loader to upload you ipa file and it will work like a charm.
Contents/MaxOS/itms/java/lib
Now you find net.properties. Edit that with your favourite text editor. Add the below lines
https.ProxyHost=
https.ProxyPort=
https.ProxyUser=
https.ProxyPassword=
You may have problem uploading through app store via xcode if you have slow internet connection, but using Application loader you can achieve the submission.
We tried lot of things which is giving in this and other posts, but it did not work.
Finally we gave the IPA file to the client to upload it via Application Loader from his end. And it worked.
So, I would strongly suggest that if your app validates fine and it still remains struck in Authentication, then rather than trying out anything, just try uploading it from totally different network in different geography.
That will save you lot of time and headaches.
I faced similar issue today while uploading .ipa via application loader which was opened directly from spotlight. Every time it was passing all the steps but getting stuck at Authentication. (AL Version 2.9)
After dozens of failed trials, I launched Xcode and opened application loader from Xcode (AL Version 2.8) and repeated earlier step. Interestingly it failed at first checking step itself! It said it had some issue with certificate .. so followed all the steps again to get new certificates in itunesconnect and on mac. (if some one wants.. here are good instructions with pics)
It got authenticated and the binary file uploaded fine.
I had the same issue. Trying all these answers may work sometimes, but usually it takes much time and may not work at the end like in my case.
I figured out a solution which will probably work for all.
Create your .ipa file by: Product -> Arcive -> Disribute(Save for Enterprise or ...) -> Next and save .ipa at target
Xcode -> Open Developer Tool -> Application Loader -> Deliver your app -> Pick your .ipa file
Withing few minutes your app will submit to iTunes. Good luck
After struggling for days with this problem the only working solution for me is to use the Application Loader with only the DAV protocol selected.
Application Loader -> Preferences -> Advanced -> Use only DAV.
The problem is due to my corporate network restrictions. DAV uses https so it's not blocked.
Solution found here: itunesconnect using application loader behind a firewall
open terminal and run these commands
- cd ~
- mv .itmstransporter/ .old_itmstransporter/
- "/Applications/Xcode.app/Contents/Applications/Application Loader.app/Contents/itms/bin/iTMSTransporter" got it from here