227

We have been trying to submit an app to the iTunes store using Application Loader for three days and keep getting stuck at the "Authenticating with the iTunes store" step.
We have read many forums (including stackoverflow) and tried what was suggested:

  • making a new provisioning profile
  • using different or multiple versions of Application Loader
  • changing proxy settings
  • rebooting the Mac
  • uploading at a different time of the day, etc.

We have even left it running overnight and have not had success with getting past this step. Unfortunately, no feedback is given about what the issue may be, and we have not gotten any error messages. We have submitted multiple apps without any difficulty in the past but are completely stuck this time!
How were you able to solve it?

27
  • 22
    its 2017 and this issue is still there. apple really hates developers
    – user230910
    Commented Feb 5, 2017 at 7:32
  • 18
    its 2018 and this issue is still there. apple really hates developers
    – user230910
    Commented Jan 19, 2018 at 0:03
  • 14
    its 2019 and this issue is still there. apple really hates developers
    – Romulo BM
    Commented Feb 12, 2019 at 13:29
  • 20
    Its 2020 and this issue is still there. Apple seriously hates developer
    – spongyboss
    Commented Jan 17, 2020 at 17:38
  • 8
    It's 2021 and this issue is still there. Apple why do you hate developers? Commented Mar 11, 2021 at 0:12

40 Answers 40

345

This only started happening to me today (May 2017) and no answers in this thread solved my issue. The resolution for me was from here;

https://forums.developer.apple.com/thread/76803

Open Terminal. Change to home directory,

cd ~  

Move the current transporter directory,

mv .itmstransporter/ .old_itmstransporter/ 

Invoke the following file to let Transporter update itself.

"/Applications/Xcode.app/Contents/Applications/Application Loader.app/Contents/itms/bin/iTMSTransporter"

Wait till it updates, then open Xcode and attempt upload.

11
  • 8
    thank you, very much! None of the more upvoted and accepted solutions worked for me, but this one does. Apple needs to learn how to properly communicate error messages. Stuck on authenticating is not useful at all. Commented May 5, 2017 at 17:22
  • 1
    Worked for me. There is currently an update for XCode on the app store, but I really didn't want to do a full update today. I needed to upload a build really fast.. and this answer did the trick. Commented May 9, 2017 at 23:29
  • 1
    Thanks for the answer, upvoted. Application Loader and XCode uploader also does the same in the background though. So instead of looking at "Authenticating..." message you see a bunch of Terminal messages. It does not necessarily speeding up things.
    – Uygar Y
    Commented May 31, 2017 at 21:35
  • 4
    A year later and still the go-to answer. Thank you! Commented Jun 16, 2018 at 18:04
  • 3
    I am getting this error No such file or directory also I installed Transporter app from Mac App Store
    – iOS.Lover
    Commented Apr 6, 2020 at 10:19
82

You have to agree to a new sign up in Application Loader. Select "Application Loader" under the "Xcode -> Open Developer Tool" menu (the first menu to the right of the Apple in the menu bar). Once you open Application Loader there will be a prompt to agree to new terms and then to login again into your iTunes account. After this any upload method will work.

Image of Application Loader on Xcode

8
  • This just worked for me. I also ticked the 'stay logged on' option on the Application Loader logon dialog.
    – Herc
    Commented Nov 11, 2016 at 11:48
  • Glad I was able to help. Indeed 'stay logged on' also an option, but not necessary to fix the stalling issue, just agreeing to the new terms.
    – Conor
    Commented Dec 5, 2016 at 9:22
  • 1
    Great advice. Seems like an oversight by Apple, but worked for me!
    – atonyc
    Commented Jan 9, 2017 at 18:58
  • 1
    This worked for me but I first had to create an app specific password to login to the Open Developer Tool. Commented Apr 27, 2017 at 22:19
  • 1
    Glad it was useful, it is indeed counterintuitive. Specially given that Xcode already has access to the developer password in keychain, they should roll the Application Loader functionality into Xcode to avoid this type of issue.
    – Conor
    Commented May 1, 2017 at 8:37
70

Just wait. In a few minutes all will be ok.

8
  • 1
    For me it takes 15-20 minutes and successfully uploaded to AppStore. But please enable TCP port 443 access. Commented Jan 5, 2015 at 6:19
  • 2
    If you haven't accepted the who-knows-what Policy Agreement, do as the other answer says. Commented Dec 26, 2016 at 22:52
  • @mgarciaisaia Thank you for linking to my answer as really should be the accepted answer.
    – Conor
    Commented Jan 9, 2017 at 23:22
  • 4
    8 hours later and i still wait. my colleague has already release the android version, and the customers have it. meanwhile i wait for apple..
    – user230910
    Commented Feb 5, 2017 at 7:33
  • 11
    5 days of waiting and still nothing, that doesn't seem like the best advice Commented May 1, 2017 at 13:09
29

Dec 10th 2019, Xcode Version 11.2.1, MacOS X 10.15.1

I was facing exactly same issue yesterday and I thought it might be network issues, at least it looks like so. But this morning I had tried couple different networks and several VPN connections, none of them is working!

The highest voted answer here asks me to reset a cache folder named .itmstransporter under my home dir, the run a program iTMSTransporter under a specific folder, but I can't find both of them.

But soon I figured that it is the cache folder for the people who uses the legacy uploader program: Application Loader, which is deprecated by Apple and can be no longer found in Xcode 11. Then I found that the latest Xcode has located iTMSTransporter here:

/Applications/Xcode.app/Contents/SharedFrameworks/ContentDeliveryServices.framework/itms/bin/iTMSTransporter

And its cache folder is here:

/Users/your_user_name/Library/Caches/com.apple.amp.itmstransporter/

I removed my existed cache folder, and run iTMSTransporter without any parameter, it soon started to output logs and download a bunch of files, and finished in 2 or 3 minutes. Then I tried again to upload my ipa file, it works!!!

CONCLUTION:

  1. Either the old Application Loader, or the latest Xcode, uses a Java program iTMSTransporter to process the ipa file uploading.
  2. To function correctly, iTMSTransporter requires a set of jar files downloaded from Internet and cached in your local folder.
  3. If your cache is somehow broken, or doesn't exist at all, directly invoking iTMSTransporter with functional parameters such as --upload-app in our case, iTMSTransporter DOES NOT WARN YOU, NOR FIX CACHE BY ITSELF, it just gets stuck there, SAYS NOTHING AT ALL! (Whoever wrote this iTMSTransporter, you seriously need to improve your programming sense).
  4. Invoking iTMSTransporter without any parameter fixes the cache.
  5. A functional cache is about 65MB, at Dec 10th 2019 with Xcode Version 11.2.1 (11B500)
4
  • 1
    Thanks alot for this answer it really helped. I installed XCode-beta version-12 and then since app got rejected by Apple since it was uploaded using beta version, I downloaded 11.5 XCode from AppStore. And was facing this issue.. your instruction helped resolving the authentication stuck error... Thanks alot.
    – Mayur
    Commented Jul 13, 2020 at 16:22
  • 1
    You are a legend. If I could upvote x1000 I would. Extra points for the detailed explanation. Thank you so much. Commented Sep 20, 2020 at 10:04
  • Thanks, DELETE the CACHE save my life.
    – JerryZhou
    Commented Jan 18, 2021 at 8:10
  • You are a legend. My cache was around 60mb prior to deletion. Then ran the application, wherever it is downloading the files from, it is very slow (~10kbytes / s) and it took around 20 minutes to download ~20 megabytes of jar files. Logging didn't start until 3 minutes in so be patient. After this process, I was able to upload my archive from XCode organizer without issues. Commented Mar 11, 2021 at 1:16
25

I was stuck at "Authenticating with the iTunes Store" today. I had used the same version and build number as a previous submission. After I updated the build number, the upload went fine. I don't know if it's related, or if it was a coincidence.

6
  • Worked for me as well. Commented Mar 20, 2016 at 19:47
  • This is the correct answer, no doubt. Worked for me as well.
    – Stephan K.
    Commented Jul 12, 2016 at 21:26
  • 1
    It's not a coincidence. You can't reupload same version and build number. Usually loader explicitly gives you a warning. In your case apparently it did not
    – NSNoob
    Commented Jul 25, 2016 at 9:08
  • Same issue more than a year later, no warning that the build number is the same.
    – PaulBGD
    Commented Aug 2, 2016 at 23:28
  • Updated the build number but didn't solve the issue of Authenticatin with the iTunes Store. I would imagine that this is not exactly the case. Commented Oct 18, 2016 at 17:34
9

I had the same issue for months, I just removed hotspot shield and private tunnel applications from my computer and tried to upload my app and everything worked just fine. so I suggest if you have installed any VPN application on your computer, remove the application and then try uploading your app from either application loader or xcode's organizer.

6

Try answer mentioned in this Reference Link, it really worked for me and for others as well.

Mentioning answer here as well. Open Terminal and run:

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

iTMSTransporter will then update itself, then you can try uploading in XCode again or via application loader.

1
  • 2
    How is this answer different from what @AshHimself proposed?
    – Eric Wu
    Commented May 10, 2017 at 16:09
5

There is no magic fix. Itunes is just working bad. Lately is having more and more issues and it takes more and more to update and send an ipa to the store. I had this issue with AppLoader and Xcode organiser too and after trying multiple times it just went through.

0
5

Changing network connection helped.

  1. Turned off wifi on my phone
  2. Enabled 3G
  3. Created HotSpot
  4. Connected my mac to the hotspot and got through the authetication issue
0
4

In my case, I hadn't agreed to the newest Developer Agreement. Just run Application Loader once, click on [Accept] to agree, then quit the Application Loader and the Upload to App Store should work fine.

4

Following worked for me.

  1. Open another instance of Application Loader. ( Select "Application Loader" under the "Xcode -> Open Developer Tool" menu)

  2. "Agree" to the terms.

  3. After completing Step 2. First instance of Application Loader proceeded to the next step and build got submitted.

3

I have also encounter the same issue. One possible solution is to go to Xcode -> Preferences -> Accounts and from the left menu select on App ID then click on the View Details and tap on the refresh button. while reloading you will get following error

The selected team's agent, 'ADMIN NAME' must agree to the latest Program License Agreement.

If you will not get above error, Following solution will not work.

It means that you need to login into the developer account using Admin login and accept that latest agreement. Then you will be able to upload binary on the app store.

3

The updated answer for Xcode 11.x.x and Transporter application, open terminal:

  1. rm -rf ~/.itmstransporter/
  2. "/Applications/Transporter.app/Contents/itms/bin/iTMSTransporter"

Wait a while Problem solved!

1
  • How long is "Wait a while". Waiting 5 mins and all I see is "Logging level set to eXtreme" and no further output
    – Frank
    Commented Mar 8, 2021 at 11:34
3

I'm running MacOS Mojave 10.14.6, Xcode 11.3.1 and Transporter 1.1.1, and always got stuck at the Authentication with App Store stage, no matter how long I wait, I tried uploading using Xcode, using xcrun altool, Transporter, nada.

Finally I got it working by exporting the ipa file to a new Macbook (10.15.3, Xcode 11.3.1, Transporter 1.1.1), and used the Transporter app to upload it there.

The key difference is the Transporter tool on my new Macbook asked for a 6-digit code as authentication while the old Macbook did not, I suspect the authentication token on my old device expired but the system didn't ask for a new one when trying to upload the app. I had 2-FA enabled.

So I think forcing a manual re-authentication when you upload the app is the answer, the only other difference is the MacOS version, but I didn't test if it'll make a difference.

1
  • 1
    my man! I have been looking EVERYWHERE for a solution. Although your exact steps did not yield a successful result for me I did figure out another set of steps. After all the logging out / deleting I still wasn't able to upload. So, i created a new local account on my macbook to test it there. Sure enough, it worked! Then, I logged out and went back to my main account and that also seems to be working now!
    – AKrush95
    Commented Mar 31, 2020 at 6:35
3

I solved the problem by removing ~/Library/Caches/com.apple.amp.itmstransporter. For safety, renaming will be better,

cd ~/Library/Caches
mv com.apple.amp.itmstransporter com.apple.amp.itmstransporter.old

Then, xcrun altool uploaded my ipa successfully.
By the way, I'm using Xcode 11.x & 12.2, macOS Catalina.

3

In 2020 Dec, the fix did finally worked for me was restarting my mac.

1
  • 1
    This, a thousand times this. No frustrating hacky work arounds. 1 reboot, prolem solved.
    – SeanMC
    Commented Aug 19, 2021 at 19:27
2

Today I ran into this issue, on Xcode 11.2.1 I solved it by going to Xcode -> Preferences -> Accounts -> Tapped on the '-' next to my Apple ID, then signed in again. This fixed it for me!

1
  • Thx! I have try this suggested step and my issue has been fixed
    – DP Dev
    Commented Sep 17, 2020 at 16:09
2

In April 21, 2021, I followed @DawnSong's answer, outlined in the image below enter image description here but I also restarted my Mac and voila it worked.

Spec Xcode 12.4 macOS Big Sur 11.2.3

0
1

You may try to relogin your ITC account via Application Loader.

1

Just try a different Internet connection. I tried all the solutions above but none worked. However, when I tried using my cellular connection (instead of my DSL connection that stands behind a firewall), it worked immediately.

1
  • did many things, that one only worked. I can't believe using my mobile as a hotspot did the trick (I still used a vpn on my computer in the evening, might have displeased itunes who knows..). Apple, your dev platform never stops to amaze me.
    – Jeremie
    Commented Apr 30, 2017 at 4:16
1

It might be a network issue. If you are running inside a virtual machine (e.g. VMWare or VirtualBox), try setting the network adapter mode from the default NAT to Bridged.

1

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

this solution is out there, it used to work for me, but today not even that! what I did and worked is that (2 instances) + uploading with XCode (organizer). Had to try a couple of times and it worked.

hope this helps someone, this bug has been there for quite a lot of time now() an apple doesn't seem to care too much

1

Another reason could be that you have changed the machine from which you're submitting the app. Or the user account on the machine. The new machine may lack the private key and/or certificate for the App Store. Although a certificate with the correct name is displayed in Xcode.

In this case, go to https://developer.apple.com -> certificates, use the plus sign (+) to add a new certificate (distribution), and follow the steps to request a certificate for the private key on your current machine. After installing the certificate, authentication may work.

0
1

For me I tried almost all the suggestions given above but the problem still reoccurred after the first success in uploading to App store. Until I found this website. In summary, do the following

  1. Open terminal
  2. Run this command:

      rm -rf ~/.itmstransporter/
      “/Applications/Xcode.app/Contents/Applications/Application 
      Loader.app/Contents/itms/bin/iTMSTransporter”
    

Note: this command(which is different from others above) will delete your ITMSTansporter folder and create a new one and ensure that xcode is quitted before running this command. 3. Start Xcode and all should be well.

1

Using Xcode 12.3 Distribute App and xcodebuild both got stuck today at this point.

I finally was able to solve this. Peeking around my system I found 3 versions of iTMSTransporter. Printing the version of each using ./iTMSTransporter -version gives the following results:

  • /Applications/Transporter.app/Contents/itms/bin/ has version 2.0.0

  • /Applications/Xcode.app/Contents/SharedFrameworks/ContentDeliveryServices.framework/Versions/A/itms/bin/ has version 2.1.0

  • /usr/local/itms/bin/ has version version 1.9.3

So it looks that old version in /usr/local/itms was used by Xcode. After deleting /usr/local/itms I was able to upload my binary within Xcode 12.2 and using the xcodebuild command line tool.

0
  1. Check your firewall
  2. Network settings - (Check with network admin, usually they have blocked apple services unknowingly)
  3. Check your system data/time.

I had same sort of issue, I resolved it by getting direct access to internet. Also check Application Loader logs to see at which point it gets stuck.

0

I think I followed all the approaches given, but none worked for me. My own approach that seems to work for me is to go thru the initial steps to upload a binary, then, after selecting the binary, do NOT click Send; instead close the window, and in the new window that will appear, start anew: hopefully it will go thru.

0

Found the solution:

I was uploading the build, Every activity went well except “Authenticating with the iTunes store”.

I disconnected my LAN cable and Connected my MAC with my mobile hotspot. and authentication problem was solved. If you have a limited internet plan then as soon as you pass authentication stage, again connect your LAN so that it will upload the app from you LAN cable's internet connection.

0

my upload failed each time when I uncheck the "include bitcode" option when uploading. So I checked the "include bitcode" option and upload went well.

0

Check your Firewall, If it is "On" then just Off it, then try

1
  • where to check this? Commented Dec 26, 2016 at 6:42

Not the answer you're looking for? Browse other questions tagged or ask your own question.