No accounts with iTunes Connect access have been found for the team

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.

For the XCode 12 and above. Closing the Xcode and reopen solved the issue.

Go to: Xcode > Preferences...

Remove your account Add your apple ID again

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.