application loader stuck at the stage of "Authenticating with the iTunes Store"

Question

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.

This is not a programming question, it is an App Store process management question. I'm voting to close this question as off-topic because there are plausibly multiple reasons that could cause this, but the primary one appears to be simply non-responsiveness from iTunes Connect. In my view, many of the proposed solutions are things people tried while waiting, that appeared to work as they then re-tried to submit. The network/proxy issues are real, but that's still not a programming issue per se. — Duncan Babbage, May 23 '17 at 23:20

score 94 · Accepted Answer · edited Dec 24 '22 at 06:01

94

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.

edited Dec 24 '22 at 06:01

starball

20,030
7
43
238

answered Nov 12 '13 at 00:26

Wharbio

1,355
10
16

How do you do this? I am getting a permissions issue when I try to change this line (logged in with an administrator account) – Nick Nov 19 '13 at 20:23
I had the same problem like Nick ? – wod Dec 02 '13 at 10:01
Its work in xcode before, i also tried this when i stuck in xcode 5.0.1 but its not uploading app when you do this in xcode 5.0.1, so i think its not now working but any how its working good before. – Appz Venture Feb 02 '14 at 03:50
I left it `authenticating` but just as I was about to kill it and save my changes to the port that it uses, it's got beyond that step and uploaded the package successfully. In my case, it just required patience! – Alastair Feb 08 '14 at 01:39
2

I couldn't find itms folder under MacOS. Anyone knows how to modify the file in Mac OS 10.9? – newguy Mar 03 '14 at 07:14
For all peeps who faced the permission - please login as root(admin) to do this. – SRP-Achiever Sep 17 '14 at 19:37
10

Seems like the path has changed to: /Applications/Xcode.app/Contents/Applications/Application Loader.app/Contents/itms/java/lib/net.properties – etayluz Aug 17 '15 at 16:49
I have just copied the net.properties wiht ports changing to all 80 , but ti fails – Jeff Bootsholz Jan 28 '16 at 06:14
Finally after trying tons of stuff I was able to resolve this issue as mentioned. Uncommented the line "# https.proxyPort=443" and changing it to https.proxyPort=80. I was able to locate that file by manually going to that path instead of Finder "Go to" box which was complaining for path not found. I opened that file in Atom editor and edited it and saved it, it did ask Admin credentials though. – Raghav Sep 02 '16 at 21:21
5

I wonder it is 2016 and why do we have such kind of issues still with Xcode with no prompt message regarding what the exact issue is. – Raghav Sep 02 '16 at 21:23
To find the path for the file, use `find /Applications/Xcode.app/ -name net.properties`. Then `cd` to the folder with quotes (because of the space), and patch using `sudo sed -i.bak 's_# https.proxyPort=443_https.proxyPort=80_' net.properties` – ishahak Jun 09 '17 at 14:18

score 38 · Answer 2 · edited Apr 17 '14 at 12:36

38

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 select Distribution over archiver in Xcode as well and started uploading concurrent.

They worked together and 2nd one completed the submission.

Just my experience.

edited Apr 17 '14 at 12:36

Geek

8,280
17
73
137

answered Oct 14 '13 at 12:14

Murat Calim

580
1
6
11

This worked for me too after nothing else did and over a month of trying, so thanks a LOT bud :D – AMAN77 Dec 16 '13 at 09:27
12

As a developer myself, I'm ashamed of trying a solution of this kind... It's really weird. BUT this one worked for me too :D LOL! – scaryguy Feb 19 '14 at 01:07
I still don't believe it, but after almost a WEEK of unsuccesfull submission, starting both transfer actually worked at the very first try!!! – Axeman Apr 26 '14 at 19:51
This worked for me too. After a week of unsuccessful submissions it worked for me just when i gave up the hope !!! Thanks bud :) – Nikhil Lihla Jun 22 '14 at 08:05
Hahahaha, unbelievable, I actually tried this as a last resort and it actually works... wtf!?! Java issues maybe! – Simon Lee Jun 27 '14 at 15:06
holy crap. this worked after days of attempts. thanks. – Sameera R. Aug 04 '15 at 09:37
1

Running two `Application Loader`s works as well, just tried it. – user362515 Dec 09 '15 at 17:57
great answer.. you make my day – Ankur Kathiriya May 18 '17 at 07:05

score 13 · Answer 3 · edited Jun 20 '20 at 09:12

13

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.

enter image description here

edited Jun 20 '20 at 09:12

Community

1
1

answered Jan 08 '14 at 08:03

HiZaib

696
7
15

can you share the link to previous version ? – jeet.chanchawat Feb 28 '14 at 10:05
Well! even this is not a solution. I have tried multiple instances. nothing is taking me to upload stage. – jeet.chanchawat Mar 12 '14 at 06:15
Same solution in different way: Duplicate your Application Loader.app in /Applications or any other place and run both Application loaders at the same time. – HiZaib Jul 22 '14 at 12:53

score 9 · Answer 4 · answered Mar 08 '14 at 11:37

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?)

This also improved my experience, from a Xamarin Studio iOS build of software. It's an unbelievable issue. Probably Apple is assuming that we all have 100 MB/s connections to the Internet, and is timing out your connection. — Phil Ryan, Jun 25 '15 at 15:03
Seems like the path has changed to: `/Applications/Xcode.app/Contents/Applications/Application Loader.app/Contents/itms/java/lib/net.properties` — rubStackOverflow, Nov 10 '15 at 04:17

score 8 · Answer 5 · answered Feb 12 '14 at 14:30

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.

score 7 · Answer 6 · answered Dec 09 '15 at 11:10

7

I solved this problem by starting second instance of Application Loader while first instance saying "Authenticating with the App Store...". You can start second instance of Application Loader from Terminal using:

open -n -a "Application Loader"

answered Dec 09 '15 at 11:10

Vishal Rajole

1,504
1
13
19

score 5 · Answer 7 · answered Mar 24 '14 at 12:49

5

Try use another internet connection. I have the same problem when try upload app via Wi-Fi. Nothing helps me, but when I disable Wi-Fi and try do it via EDGE on my iPhone, everything is works!

answered Mar 24 '14 at 12:49

Vitalii Gozhenko

9,220
2
48
66

Probably the httpProxy workaround fixes the issue on SOME weird WiFi situations, but not the one in my case... – Brian Birtle Jul 10 '16 at 12:39

score 3 · Answer 8 · answered Sep 26 '13 at 06:28

3

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

answered Sep 26 '13 at 06:28

Mashhadi

3,004
3
46
80

1

OOPS,I did actually try your way first(with organizer),found it didn't work for me,so I turned to application loader. – piaChai Sep 27 '13 at 01:09

Farooq Nasim Ahmad · Answer 9 · 2013-11-17T15:40:07.260

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.

Closing Skype immediately fixed the problem for me! – skagedal Apr 14 '16 at 12:18 — skagedal, Apr 14 '16 at 12:18

score 1 · Answer 10 · answered Oct 09 '13 at 08:22

Sometimes it is the network trick. Connecting to different network may solve this problem.

I tried both the two ways(Xcode/application uploader) at home, neither worked.

Then, I brought my macbook from home to library, it finished uploading within 3~5 minutes there(via application uploader).

score 1 · Answer 11 · answered Feb 23 '14 at 16:49

1

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.

answered Feb 23 '14 at 16:49

Swaroop S

490
5
11

How do you fill value for those keys or just let them blank or use default value?? – Bad_Developer Feb 18 '19 at 08:58

score 1 · Answer 12 · answered Mar 20 '14 at 04:15

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.

Muhammad Irfan · Answer 13 · 2014-08-24T03:30:51.070

1

enter image description here All i did was duplicate my Application Loader.app in /Applications and ran both Application loaders at the same time.

enter image description here

edited Aug 24 '14 at 03:30

answered Aug 24 '14 at 03:23

Muhammad Irfan

280
3
17

Som Parkash · Answer 14 · 2018-02-08T12:56:44.577

1

Simple use this command in terminal it worked for me:

1. cd 
2. ~mv .itmstransporter/.old_itmstransporter/
3. "/Applications/Xcode.app/Contents/Applications/Application Loader.app/Contents/itms/bin/iTMSTransporter"

edited Feb 08 '18 at 12:56

answered Jun 29 '17 at 06:08

Som Parkash

234
3
9

Omkar Nisal · Answer 15 · 2013-10-29T20:23:53.343

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.

score 0 · Answer 16 · answered Nov 13 '13 at 13:33

I tried many things including the suggestion provided here. Once I re-login in "Application Loader" to restart the delivery. The package passed the authentication stage and start uploading. Maybe "Application Loader" needs to revalidate your authentication but can't say it loud.

score 0 · Answer 17 · answered Feb 27 '14 at 22:15

0

This happened to me today. I shutdown my Mac and then tried the application loader after couple of hours.

It worked.

I guess it was a problem at iTunes Connect.

answered Feb 27 '14 at 22:15

Bilbo Baggins

3,644
8
40
64

score 0 · Answer 18 · answered Jul 22 '14 at 06:07

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

score 0 · Answer 19 · answered Jun 15 '15 at 02:02

0

Charles Proxy (or any other proxy) could have this effect.
Review and accept any new terms in member center.

answered Jun 15 '15 at 02:02

Jeremie D

4,145
1
35
41

score 0 · Answer 20 · answered Jul 03 '15 at 11:08

0

Best and quickest fix I found is to copy 'Application Loader' from 'Applications' folder to desktop, run both 'Application Loaders' simultaneously.

Works like charm every time :)

answered Jul 03 '15 at 11:08

Pooran

1,640
2
18
25

score 0 · Answer 21 · answered Jul 03 '15 at 12:47

0

There is nothing wrong with server of any ports in my case. I have 9 MB of build. With good interenet speed it takes 5 minutes. I feel I got stucked. But after few minutes it uploaded successfully.

answered Jul 03 '15 at 12:47

Gajendra K Chauhan

3,387
7
40
55

score 0 · Answer 22 · answered Dec 03 '15 at 17:50

0

I was missing the distribution signing entity. I created and it did work.

answered Dec 03 '15 at 17:50

J.Williams

1,417
1
20
22

score 0 · Answer 23 · edited May 23 '17 at 12:10

0

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

edited May 23 '17 at 12:10

Community

1
1

answered Apr 06 '16 at 10:27

mrAlmond

393
4
17

score 0 · Answer 24 · answered Jun 19 '17 at 23:26

0

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

answered Jun 19 '17 at 23:26

Uche Dim

412
5
7

Maninderjit Singh · Answer 25 · 2017-05-23T04:05:08.427

-8

Hello Friends, Do not worry about it, Simply disable the bit code option in build Settings and make build and upload.

No need to do any extra work

Try this one

edited May 23 '17 at 04:05

answered Aug 02 '16 at 04:03

Maninderjit Singh

1,419
1
13
23

That's ok my friend, it was just your 100% working solution statement that made me respond. ;) – Adam K Dean Oct 11 '16 at 21:19
With this i was able to upload app on itunes – Maninderjit Singh Oct 13 '16 at 12:54
4

I understand, but what I'm saying is, you said "100 % working solution" based on 1 try, 1 success. So with my failed try, that's 2 tries, 1 success, 50% working solution. Right? ;) – Adam K Dean Oct 13 '16 at 15:17

application loader stuck at the stage of "Authenticating with the iTunes Store"

25 Answers25

https.proxyPort=443

Linked