Related
In Xcode, when I try to Product > Archive > Validate App I get the error:
No accounts with iTunes Connect access have been found for the team "TEAM_NAME". iTunes Connect access is required for App Store distribution.
and/or
No accounts with App Store Connect access have been found for the team "TEAM_NAME". App Store Connect access is required for App Store Connect distribution.
and/or
Unable to authenticate with App Store Connect
How can I fix this issue and validate my app?
Solution 1:
Quit Xcode completely and re-open it to resolve the problem.
Solution 2:
Please verify if it's App Store distribution profile or not.
If yes then try to login to Xcode with your apple Id which has access
to iTunes Connect or App Store Connect.
While validating the archive file please choose the same profile. It
should work fine.
When this happens to me, closing Xcode completely and re-opening it solves the problem.
Ran into this problem just now. Complete shutdown and restart of Xcode did the trick for me.
Just restart Xcode and it will work :)
Definitely it will work in Xcode 9 alternate you can try with Application Loader.
Swift 5, iOS 13
Just restart Xcode, everything works
Make sure that your network firewall doesn`t block iTunes connect domain. You might experience with the same message if it is blocked.
For me, iTunes & AppStore access is blocked firewall network level. I restart Xcode and mac, it worked like charm.
Restart Xcode or Restart your mac, In my case I just restart Xcode
UPDATE XCODE 10
September 2019
If closing Xcode doesn't work, try logging out and logging in with the Apple Developer Account, which may not be the same as the iCloud account in many cases.
These two steps would solve 95% of these error cases.
Another solution that works for me is to disable Automatically manage signing and then restart the Xcode.
Then I enable again the Automatically manage signing to upload the application.
Hope that helps.
Go to: Xcode > Preferences...
Remove your account
Add your apple ID again
For the XCode 12 and above.
Closing the Xcode and reopen solved the issue.
Just restart not only Xcode, but also the OS.
Didn't believe it, but really, just restart.
I tried these three solutions and things were back to normal
Solution 1:
Completely close Xcode and Safari.
Solution 2:
Logout and login your apple developer account in Xcode preferences
Solution 3:
Go to your Keychain and deleting the old expired certificates.
Make sure apple store domain can be accessed, in my case it was blocked by network admin, i found this after struggling for 2 days in this
I had a similar issue. Turned out that App Store was blocked by IT (arrrggggg!!!). Try a different network or ask IT to unblock then should work but first check that you can access App Store
Previous answers didn't work for me, including restarting, quitting Xcode and refreshing profiles.
Disconnected from company VPN and instantly started working.
Seems to be a lot of solutions to this problem and none of the above worked for me. What did work for me was going into Keychain and deleting some old expired certificates.
UPDATE XCODE 11
If the restarting of Xcode doesn't work, then try logout and login again in with the Apple Developer Account in the xcode.
Process:
Xcode > Preferences
Remove your account by clicking on - sign button
Add your apple ID again by clicking on the plus (+) sign button
I experienced this problem just now.
Complete shutdown and restart of Xcode did NOT do the trick for me at first!
I also had to close the Safari browser which was running in the background.
After both Xcode and Safari was completely closed.
I open Safari and navigated to the "App store connect" page -> login.
Then I opened Xcode -> run Archive - Validate. and it worked :)
Explanation of problem maybe.
I have changed WiFi connections, from office to home office with both Xcode and the Safari browser open, and they must then have gotten confused of the wifi change, and remembered old connection data.
I had the same issue today .I had logged in with the apple id to an iOS device and linked with iCloud that was creating issue to me so once i removed the account from the device it worked fine for me.
For me, this happened when I have the same Apple Id added to the accounts of Xcode on two devices. After removing the account from one device, the other one can upload to App Store fine. I did restart Xcode after removing, not sure if that's necessary. Maybe it's more like a session expires or connection issue.
I know this has been solved, but none of the listed solutions worked for me and in case someone else is also experiencing this issue- it could be due to not enabling Two-Factor Authentication.
I was having no problems uploading builds to the App Store and within the span of 1 hour got this same issue. Once I followed Apple's documentation and enabled Two-Factor Authentication for both my organization's Team Agent as well as my own developer account, I restarted XCode and was able to successfully upload builds again.
I had this same error. I tried rebooting etc. and nothing worked. I tried again several hours later and managed to submit successfully. I can only assume the service was down.
Please use Application Loader, if all the above fails.
Step 1:- Create a .ipa file for app store distribution.
Step 2:- Login to Application loader with your apple developer account for which you are uploading your app.
Step 3:- Choose .ipa file from application loader, read the instruction asked and follow the steps.
I got the same issue, after spending lots of time and doing each and every thing but no solution work for me, at the last I just upload me .ipa file in Application Loader. And it work.
Xcode 10. Aug. 2019
Press the Manage Account then see a reminder said my account is expired.
Logging in again fixes this problem.
While developing using XCode, I found many errors only solved with restarting XCode and Macbook. Just restart the Macbook and it will be gone. Anything else except restarting is not worth of time. I have tried many things to solve this error. I tried to log in again and again with AppStore but only restarting MacBook worked for me.
If closing Xcode or restarting the Mac didn't help, try deleting Derived Data.
Remove all apple accounts
close xcode
restart mac
add apple account
it will work
make sure that project navigator under both pods and runner, and signing & capabilities tab the team is selected.
Deleting DerivedData and restarting XCode solved the issue.
I have been building on an hybrid app with PhoneGap for about a month. Have been using the PhoneGap Developer App for mobile all the time and have been working good all the time.
But suddenly, when I'm about to test the app today. It doesn't work. It just "Downloading" forever.
When I visit the build.phonegap.com website and watching my app build details there is an "Error" at iOS saying: You must provide a signing key, first. Find out how to fix this..
I'm reading the text on the "Find out how to fix this" link. But no info about why I suddenly need a signing key.
In order to get an signing key you have to have an "iPhone Development Certificate". And that costs. That's why I want to use PhoneGap. To be able to build and test the app before I buy the iPhone Developer Certificate.
Bottom line: Why do I suddenly need signing key for PhoneGap Developer App?
Yes, you must have an iOS developer key to make signed .ipa file. You need it because without it you will not be able to deploy to any devices.
I have solved it now.
First of all: PhoneGap Developer App has nothing to do with PhoneGap Build. So that was two separate problem.
What caused the problem was something got wrong after I upgraded to latest Beta version.
Solution: When I downgraded to latest stable version, everything started working again.
I distributed version 1.0, build 1, of my app via TestFlight, and everything worked perfectly.
Yesterday I archived and sent out build 2, and now upon tapping the update button, every user seems to be getting an error:
Unable to Download App
[App name] could not be installed at this time
I haven't heard from any users who didn't have build 1 installed already, but looking at iTunes Connect, no user has build 2 installed.
Encountered exactly the same problem today, trying to install a new testflight version downloading it through our company WiFi. We noticed that we could still download and install the app from mobile devices through LTE which lead us to the conclusion that for whatever reason testflight must have blocked our office IP (temporarily) for unknown reasons.
I hope this actually works for someone else. I was seeing the same result over and over again. I restarted my phone. I took my account off the Test Flight list and re-invited myself. Same result. 2 other people were able to install, but I wasn't. I furiously tapped "Install" several times as fast as I could, then tapped "Retry" when the alert box came up. Continued to tap "Install" over and over again, then "Retry". Install, Retry, Install, Retry. Then it finally started installing...
I wish I were making this up.
Bump the build number and resubmit your app. This is a TestFlight/iTunes Connect-side error that, as far as I can tell, we can do nothing about.
Update 12/7: The bug I filed on this (rdar://23296795) was recently returned to me as "We believe this issue has been addressed through changes on our side." – So if you're still seeing this error, please file another radar and let them know it's still not working.
Update 12/10: According to Remy in the comments below, it is still not fixed.
For future readers
This could be a Certificate / Provisioning profile issue.
I just had this issue after wiping my mac and reinstalling OS X (i.e. all my certificates and profiles was gone from my keychain), and I did the following to fix it:
Delete / Revoke any existing certificates and Prov. profiles. (In my case Xcode had tried to download the certificates for my old computer, and they somehow became invalid in doing so).
Then, in the following order:
Create a new Development AND Distribution Certificate
THEN create a Provisioning profile for Development AND Distribution
Xcode signs your app with your Distribution certificate when it builds it for TestFlight, or the app store for that matter. That's why it is important to have a Dist. Cert. when uploading to test flight even thought it's just for internal testing. I don't know if it matters wether you have a valid Dev. certificate and Prov. profile for test flight, but it doesn't harm to have it. You need it to build to your phone anyways
I hope this helps.
]
I've got this error many times, but I saw a really strange pattern and I have a pretty weird theory.
Next time, after you submit your app to Apple, don't submit it immediately for beta review. Download the app at least once with TestFlight on your iOS device as an internal tester. Do that before you submit the app for beta review and it should work.
Sounds crazy and I can't really confirm if downloading the app as an internal tester "triggers" anything, but it seems to be working for me that way. Could be a random coincidence though, would be interesting if someone can confirm/deny my theory.
Definitely one of the more annoying bugs of TestFlight right now. :/
Same error for me. The only thing that worked for me was to uninstall the TestFlight app and then reinstalling.
I faced the same issue under the follow case:
Created a Test users group in iTunes Connect even before the Build was approved (i.e. it was in "Waiting for Review" state). We did receive notifications from TestFlight, but when clicked on "View in TestFlight", received this error.
I added the approved build to the Group and Resent the invites. This worked perfect for me.
We had a user who had, for reasons only they know, disabled cellular access for the Testflight app. Later, when he'd also turned off Wifi (again, for reasons...) he was in a situation where Testflight had no connectivity.
The error he saw was "could not load apps". It was driving us crazy as our other users were able to install and run without issue!
I had a previous version of this app with the same name. Just deleted it from my device and testflight installation worked.
I encountered the same issue. Not only it fails in TestFlight but also it is rejected by Apple Team in the submission process for not launching. I was able to solve this problem by renaming Project and Target names excluding wildcard characters.
The names were like following;
I spent almost two days to discover the issue. Hope it helps!
I was able to fix this problem by removing the 0s from my build number as described here.
As funny as it sounds, TestFlight currently has a bug that prevents deployment if your buildnumber has a 0 in it.
Buildnumber 102 failed to install on all devices I tested it on, simply changing the buildnumber to 112 (nothing else changed!) and uploading it again fixed it immediately.
I have two iphone devices( 4s and 5 ) connected to my computer and i am trying to install an application in both the devices. It installs pretty well in iphone 5 but it gives an error 'The application could not be verified.' when attempted to install in the iphone 4s device.
The UDIDs of both the devices have been added in the provisioning profile generated for the application.
Also, to add a note, I have just updated my iphone version to 8.1.3 in my 4s device. I am not sure though if the error has anything to do with it.
Any help on this would be much appreciated. I have been stuck on this for some time now.
EDIT:
I just connected this to another iPhone device and the issue seems to be there again. Basically this means that the app, for some reason, installs only in the phone which I have been using for some time now and not in any other phone. Once again, I am pretty sure that the provisioning profile contains the UDIDs of all these 3 devices.
I had something similar happen to me just recently. I updated my iPhone to 8.1.3, and started getting the 'application could not be verified' error message from Xcode on an app that installed just fine on the same iOS device from the same Mac just a few days ago.
I deleted the app from the device, restarted Xcode, and the app subsequently installed on the device just fine without any error message. Not sure if deleting the app was the fix, or the problem was due to "the phase of the moon".
As I notice The application could not be verified. raise up because in your device there is already an app installed with the same bundle identifier.
I got this issue because in my device there is my app that download from App store. and i test its update Version from Xcode. And i used same identifier that is live app and my development testing app. So i just remove app-store Live app from my device and this error going to be fix.
just delete the app and try again, it happens to me when i try to launch over a device that has the same app but generated by an ipa file.
You probably used the "Fix Issue" option in Xcode when plugging in a new device. Old question but I believe this is the actual answer to WHY this is happening. When you install an app on a device it is signed with a specific development provisioning profile. If, for instance, you plug in another device that is not registered on your developer account Xcode will ask you to "fix the issue". When you press that the device is added and another provisioning profile is created/modified. If you try to overwrite an existing app you'll receive that error. Deleting the app and reinstalling it works since the profile has been altered. I find this often happens when a Team is set and a member plugs in a new device then Xcode "Fixes" the problem.
Might have figured it out... Deleting the app from the device worked for me, as others mentioned before (thanks!).
I think the reason is that the app on the device was actually signed with a separate provisioning profile, specifically a distribution profile in my case.
I faced this issue a lot. I am not sure if this is the issue, but I think, when xCode saw that there is an app with the same bundle identifier as of the app, I am trying to install, it didn't allow me. So, I had to delete the older one and attempted to install and it worked. However sometimes for testing purpose, I needed multiple version of the same app and in that case, I would change the bundle identifier and try to install. It only works if, I am using an wildcard provisioning profile.
To others not using RubyMotion and don't think that deleting the app is acceptable (as in, you want to do upgrade testing). Check out the bottom of these docs from Apple:
https://developer.apple.com/library/ios/technotes/tn2319/_index.html
It looks like they changed something in 8.1.3 to check for this new rule.
The Fix
"[Add] the installed application’s application-identifier value, as logged in the second parentheses, to the previous-application-identifiers entitlement’s array value for the app being installed (by resigning it or re-building it) and requesting new special provisioning profiles as shown below."
<key>previous-application-identifiers</key>
<array>
<string>{Your Old App ID Prefix}.YourApp.Bundle.ID</string>
</array>
EDIT:
In order to do this, you need special provisioning profiles. You can request these from Apple:
"To enable signing with the previous-application-identifiers entitlement new special provisioning profiles are required that can be obtained by going to the Contact US page and requesting them." (from the docs linked above).
Had the same issue on my iPad running 8.1.3 Deleting the app and installing again fixed the issue. I use two different provisioning profiles on two different machines and that could have caused this issue.
Working & tested solution, which does not require to delete application:
It looks like AppStore Distribution Provisioning Profile or just iOS Distribution certificate have special permissions and "Could not be verified..." problem does not apply to them. They will always override previous certificate.
In other words: AppStore release will install successfully, even if already installed (testing, adhoc or enterprise) app has been signed by the certificate from different team.
If you are lucky and have previously uploaded app to the AppStore account owned by the same team as in certificate you have a problem with - then things are very simple: just download & install app from AppStore.
When it installs - app certificate will be the same as the one you want to test with and problem goes away.
If your app is not on the AppStore yet - iTunesConnect beta comes to the rescue:
Disclaimer: I did not tested this but since cert an prev are the same as AppStore release, I bet it works:
Archive your app with AppStore provisioning profile (iOS Distribution cert) and upload to iTunesConnect (to the account owned by the same developer team as included in the provisioning profile not you want to run).
Invite person with the device you want to run on (yourself?) to beta test.
Download & install the app from iTunes connect beta.
Now you are able to install your testing version.
The application could not be verified" , in your device there could be already an app installed with the same bundle identifier.
So Simple solution Just delete the App & try again..
....
TL;DR answer - There is no real solution besides "delete app and reinstall".
This answer is not satisfactory for many situations, when you have an existing database that needs to not get deleted within the app.
Lukasz and plivesey are the only ones with solutions that don't require delete, but neither worked for me.
I resolved this issue by changing the Build System to legacy in xcode.
I had the same problem but the mentioned solutions above didn't work for me. Even I had no previous app on device, I got this error when deploying on my device.
How to do:
Simply, go to menu File > Project Setting, inside Share Project Settings, change Build System from "New Build System (default)" to "Lagacy Build System".
I also encountered the same issue. Deleting the app didn't work, but when I tried deleting another app which was the current one's 'parent'(I copied the whole project from the previous app, modified some urls and images, then I clicked 'Run' and saw the unhappy 'could not be verified' dialog). Seems the issue is related to provisioning and code signing and/or some configurations of the project. Very tricky.
I had changed the team but I forgot to change it in my Tests target it so it caused that. Maybe this helps someone.
Just had the same problem and I found out that the issue is with expired certificate.
My app was distributed (AdHoc) through firebase and few days ago app was working just fine.
Today I've realized that I can't install it because 'The application could not be verified'.
Finally I realized that certificate that I was using for app signing has expired 2 days ago.
You need to upload it again and you'll be able to install it.
I had the same problem. But, I realised I was using a single plist with (debug) and (release) configuration, like this.
So, I changed few things..
Keeping a separate scheme for (release).
I added a new scheme for development purposes.
Edited the new scheme > run > Build Configuration > and set it to (release)
Generated a new archive using the new scheme and voila!!..
I'm able to install on all my devices.
My case:
jailbreak'ed iPhone
Final solution:
Install tweak AppSync Unified via Cydia
to bypass signing/certificate verification
Same issue occurred for me when I was installing through link. I tried to install using different link. Then I could install the app.
I am facing an issue while submitting my app from Xcode to the App Store. I have done everything regarding my project, and its running fine on my iPhone and iPad. But when I submit my project I am facing a huge problem.
First after archive I have done the validate. Now my archive file in Organizer is showing status pass validation as well. So I believe I am at the final step of submitting the app.
I have clicked on distribute and selected submit app to app store.
After login I have selected provisioning files as well.
I am stuck here. You can see in the screenshot below. And I have never seen any
progress bar where I can see the submission progress or something like that.
Only screen I can see is:
Edited:
It was near about 1.30 hours. And internet connection is working. My ipa file is only 3.5 MB.
And last when I tried Application loader to upload the same I received the following screen as well for a long time in Authenticating with the iTunes Store... ..
What should I do now?
As I felt a serious issue on this. I believe this answer might be helpful.
After trying for around 10 to 12 hours to fix this issue and as everything else regarding my project and coding was fine enough, it became a headache for me. But after getting some valuable comments from some of the expert users of stack-overflow and after doing some more search on the internet, I have found some quality answers.
This answer helped me the most:
application loader stuck at the stage of "Authenticating with the iTunes Store"
If you are going to upload it through Application Loader and it gets stuck on "Authentication with the iTunes Store..."
or
You are going to upload it through XCode and it stucks on “Your application is being uploaded”
Then just keep your head cool and check this first method:
Check if your firewall protection is off. If not then turn it off. It maybe blocking you to connect your computer with iTunes
Store.
Try a different internet connection. The purpose for trying a different internet connection is that your current internet connection maybe blocking a required port for connection to Apple servers.
If the above steps doesn't help you then follow this second method:
Xcode needs java runtime for uploading your apps to the App Store.
enter 'java -version' in the terminal, java version should be 1.6 .If not then download
latest compatible java only from apple download center:
http://support.apple.com/kb/DL1572?viewlocale=en_US
If this still doesn't help then follow this third method:
This method enables the application loader to use the HTTP port instead of HTTPS.
Go to
Application Loader java folder :
/Applications/Xcode.app/Contents/Applications/Application Loader.app/Contents/MacOS/itms/java/lib
Open net.properties file using any text editor application like text mate or sublime text
Change this particular line : #https.proxyPort=443 proxy port to
https.proxyPort=80
Save the file. And that's it !! You can easily upload your binary file to App
store now.
If the above methods still doesn't help then follow this fourth method: Regenerate your certificate
Goto iOS developer portal (https://developer.apple.com/membercenter).
Revoke current certificate which is used by your App for signing.
Remove current "iOS distribution provision profile" from Developer
portal.
Regenerate the iOS distribution certificate and add them in developer portal.
Regenerate "iOS distribution provision profile" for app store
distribution and download to mac.
Install it.
Try again using xcode/application loader to upload the build.
There is definitely a problem if your app stuck on "application stuck process". I suggest you to go with Application loader rather than Xcode itself as Application loader shows the activity status. You can clearly know in which step you stuck.
The most frequent issue faced is to stuck on the "Authentication with the iTunes Store..." step.
There are possible two work around which I followed and finally submitted my app to app store. You can try both. For me both worked at least once.
Method One : This method plays with proxy port to use http connection over https
Go to Application Loader java folder : /Applications/Xcode.app/Contents/Applications/Application Loader.app/Contents/MacOS/itms/java/lib
Open net.properties file with "sublime text" or "text mate"
Change "#https.proxyPort=443" proxy port to "https.proxyPort=80"
Save the file and reopen Application Loader and Try again.
Method Two : Regenerate your certificate and iOS distribution provision profile and Try to upload
Goto https://developer.apple.com/membercenter
Delete previous certificate referenced by your App for signing.
Revoke your distribution certificate and download it to your mac. And install it by double clicking it.
Delete current "iOS distribution provision profile" from Developer portal.
Regenerate "iOS distribution provision profile" for app store distribution and download to mac.
Install it by double clicking it.
Try again using application loader to upload the build.
Edit: I again got this problem while uploading new build. Both of above methods were followed but was stucking in "Authentication..". Restarted the mac book and it worked. When you restart, the previous itunesconnect connection (which you might have opened in browser prior to submit your app) are reset which allows restarted mac to easily authenticate iTunes Connect. Yesterday (jan 26, 2014) the iTunesConnect authentication step proceeded within 2 mins. Hope this helps someone who is loosing patience while stuck on authentication step.
Edit 2: Before deleting distribution Certificate, try only regenerating "iOS Distribution Provision Profile". It worked for me else you can redo as above.
I Hope this helps. All the best.
I tried all the steps from Rajan's solution; none worked. However, this threads on apple dev forum (https://forums.developer.apple.com/thread/76803) gave me the solution in my case :
Try this, it fixed it for me. 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.
For me, just logging out from ituneconnect website and developer.apple.com does work.And just using xcode to upload. No need to restart
I got this issue today. But finally I found it's caused by my wrong settings.
In 'Build settings' of the target, change settings "Code Signing Identity -> Release" to your production certificate, and "Provisioning Profile -> Release" to your distribution provisioning file.
Then archive and distribute it again.
You can try to cancel the upload and retry. If that does not work you may want to try the Application Loader from Apple. It essentially does the same thing, but does not resign the binary. You can download the application loader from itunes connect. See https://itunesconnect.apple.com/docs/UsingApplicationLoader.pdf (Getting Started, Page 9)
I had the same issue.
I cancelled and ran a validation check. It turned out I had written a URL Scheme incorrectly.
Xcode did not gave any errors when uploading and simply got stuck but validating gave the error.
So, try validation first. Hope this helps someone.
try this on terminal
cd ~
mv .itmstransporter/ .old_itmstransporter/
"/Applications/Xcode.app/Contents/Applications/Application Loader.app/Contents/itms/bin/iTMSTransporter"
worked for me after hours of researching
This is Happened Due to the iTMSTransporter
Try this, it fixed it for me. Open Terminal and run:
Use these commands one by one on the terminal. Hope it will help you
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.
I met this issues many times, I tried all steps but it still not working (home network) and try other network work fine (company network).
I fixed this problem by update latest Java SE from 1.6 to 1.7 and it work like a charm
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.
For me the issue was that I've changed my Dev. Account at some point of time and Application Loader itself was not authorized anymore. You have to manually to go it (Xcode -> Open Developer Tools -> Application Loader) and fill in your account details
I had the same issue. I as able to fix it by:
Remove/delete all distribution certificates and provisioning profiles from my machine.
Revoke distribution certificates and delete distribution provisioning profiles from Member Centre at developer.apple.com
Create a new Distribution certificated by generating a new certificate signing request from keychain access
Create a new provisioning profile for app store distribution
Download newly created certificate and add it to keychain access
Download newly created provisioning profile and add it to xcode. OR sync from Xcode from account settings.
Try to upload again.
This is some silly issue that Apple needs to fix asap. I wasted 2 days from something as silly as this.
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
All i did was duplicate my Application Loader.app in /Applications and ran both Application loaders at the same time.
I had the same issue after updating Xcode5 to Xcode6. After hours of craziness, the one and only thing that helped me was to delete my account in Xcode preferences and add my account again.
Last week I had the same issue after update to Xcode7, this helped me again...
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.
This worked for me:
Logout from iTunes portal in all the browsers.
Restart your Mac machine.
Open Application Loader
Click on your Apple Login in the Top Right corner of the Application Loader Window.
Clicking Next will succeed your authentication process.
Now, do your process as usual by clicking upon the "Deliver Your App" and following the procedure beyond that.
My problem was I forgot to change the Bundle Identifier in info settings for the target. Hope it help someone.
I had similar issue while uploading iOS apps through application loader.Then once after i opened iTunes parallel all of the sudden uploading apps was faster.Not sure if iTunes has any dependency with application loader.
None of the answers worked for me and my upload was hanging for days without any error. (my build was generated using Expo). Here's what I did to make this work:
In the apple's guideline, it says one way to upload the build is to use the Transporter.
Using the Transporter, it was able to detect and output the error.
It turns out the root cause for me was the XCode version was 9 but it has to be 10.
I hope this helps others who are struggling on this issue.