On Xcode 7 I keep receiving error "No accounts with iTunes connect access"

For me I had to remove my account from Xcode > preferences > accounts > Apple IDs by pressing the "-" bottom left. Then The "+" and adding back in my details. Nothing to do with Technical accounts being required. As being Admin gives you full access and privileges anyway.

---

Remove the Apple ID you're experiencing issues with from your Accounts list. Then, add the Apple ID back to the Accounts list.

---

Check System Status here first. ☞ System Status

Make sure you click and open the service you want. It could be green but may be down.

In my case although iTune Connect was green, when I clicked to open my account, activity spinner kept going forever.

So actually iTune Connect was a problem.

I waited until I could log into my account, tried to upload binary again from Xcode, than above warning disappeared.

It had nothing to do with my Xcode or my account. It was Apple server.

---

Workaround: Export your .IPA for App Store Deployment, then use Application Loader to upload to iTunes Connect.

---

I've managed to solve this issue today. The problem was that my developer account was different from my iTunes connect account (Because I'm in different developer teams).

I only had my developer email in Xcode preferences, so adding the iTunes Connect account solved the issue.

---

In my case I have created Apple developer account, but haven't created iTunes Connect account

---

This will happen if you are using an Apple ID that is being shared between teams. So if Apple ID is used for more teams just remove that emails you don't want or create new one.

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

---

I have solved the problem.

Just turn off Two-factor authentication.

From https://appleid.apple.com

:)

---

I got this error message when trying to upload using a Beta version of xCode 9 - don't use a beta.

---

For me (working with XCode 9.3), solution was to close and restart XCode, it worked!

---

For the time being I am submitting the exported app with Application Loader that seems to be friendlier. When Apple makes up her mind and also fix Xcode I shall take the shortcut.

---

First time I faced this problem.

In my case, I just needed to wait and it fixed by itself. I sent two updates, and after successfully submitting the first one, an hour later, I had this error on the next one. I tried what other people said about removing and adding the account, but it didn't work. It's probably something on the side of Apple.

---

Remove current account you use now, and add back again, that's the only one solution for this.

---

I faced the same problem days ago and I've tried a bunch of solutions and none of them worked for me.

But what I have found is that I'm trying to upload the build using my Macbook connected to the company's guests WiFi and they're using a firewall to prevent uploading or attaching files.

just tried to upload it from anther network that allows uploading and yes it was just as simple as that :D

---

I was able to still successfully export the app (rather than clicking upload to app store) and signing still worked. Apple also allows you to use something called the Application Loader. I was able to successfully upload this way.

https://developer.apple.com/library/content/documentation/LanguagesUtilities/Conceptual/iTunesConnect_Guide/Chapters/UploadingBinariesforanApp.html

---

As has already been stated by two of the other answers here, note that an iTunes Connect account is different to an Apple Developer Account. You need to create both. Although the Apple Developer documentation states that you will need to upload to iTunes Connect, it does not explicitly state that you need to register for iTunes Connect separately.

This is not obvious when attempting to Upload / Validate / Export an application through Xcode, as this is the first step at which you will need an iTunes Connect account. On top of this, the error message shown when you don't have an iTunes Connect account gives a link entitled Add account, though this link simply takes you back to the Xcode -> Preferences -> Account tab (which doesn't actually allow you to create an iTunes Connect account).

I tried visiting iTunes Connect to create an account, though that page told me that I needed to create an account before being able to access iTunes Connect. Considering I was an admin on a team, I thought I would have permission to do this. However, the critical step that I was missing was buried deep inside the iTunes Connect help:

Initially, only the team agent (the person who joins the Apple Developer Program) can sign in to iTunes Connect and perform these steps. [...] If you are the team agent, use the Apple ID you used to join the Apple Developer Program and add other users to your iTunes Connect organization.

Getting the team agent to add me to iTunes Connect (as is described here) solved the problem for me; I can now successfully upload, validate and export applications through Xcode.

Hopefully this helps someone else who also didn't realise this!

---

I just restarted my mac and its working fine

---

I ran into this issue on my machine that's running the latest version of Xcode on a beta version of OS X. To solve the issue, I archived the app on a different machine running the latest public release of OS X and Xcode, and uploaded it from there. I simply exported my developer account and imported it onto my other machine. The app submitted successfully.

---

I had this problem with my account which is on multiple teams.

I had to:

Explicitly add the AppleId for the iTunes connect account of the new team (name+email@email.com) on xCode->Preferences. Verify my email for the new iTunes connect account by logging into https://appleid.apple.com.

Error went away after this.

---

Let me tell you what worked for me. I was getting the same issue.

Later I figured out that I was using OpenDNS to control my network and when I disabled the OpenDNS it works just fine and the issue got solved.

So, people looking for solution check whether you have firewalls. Keep it as one of your check lists.

Correct me if I am wrong.

P.S. I also tried the above given solutions but nothing worked for me until I disabled the firewall.

---

I had this issue come up after 470+ successful uploads to iTunes Connect. After deleting my provisioning profiles, revoking my certs, deleting my apple id, and re-adding it to xCode - Accounts, without any success, I called the Apple support line... They could not help.

Eventually I had a wild idea to delete myself as an Admin from a DIFFERENT team. It works now. So, for those with this problem, ask yourself if you are part of a different team that could be conflicting.

---

You may have this problem if your Apple Developer Program Membership has expired.

Just renewing it (and paying 99€) will solve it.

---

Here's how I solved it....it is unclear which of the following was key.

1) The contracts section in iTunesConnect was asking for some new banking information (i.e. was my bank account an individual or corporate account). I answered that. It took about 10 minutes to 'confirm' - meanwhile I did #2 and #3 below.

2) I deleted my iTunes Account account (myname @ gmail . com) from the accounts on my Mac. I then added that account back.

3) I quit Xcode and restarted it.

---

I've noticed you seem to have two email accounts listed there - your Gmail and your domain email address.

Which address are you using to log into iTunes Connect? Is this different to the account you use to create provisioning profiles?

I have just run into the same issue and manage to solve it after much head banging on the keyboard.

For ages, I've used my personal Gmail account (which is my Apple ID) for app development. It's always been linked to my organization's team.

However, I just realised my iTunes Connect account actually uses my work email.

When trying to sign the app in Xcode, it'd instead try to log into iTunes Connect using my personal email, which isn't actually linked to my organisation on iTunes Connect.

So, I just added my personal account to my team's iTunes Connect. Voila! All is well again. (I probably should've created an Apple ID for my work email and added that in Member Centre, but creating provisioning profiles is like getting stabbed in the eye).

Now I'm actually mind-boggled as to how it managed to work in the past.

Hope this helps.

---

I was facing a similar issue in Xcode 7.0.1 where we are packaging an app for a third-party to release. In the past, this has been no problem as our account has admin access and we have the required provisioning profiles.

However, in Xcode 7.0.1, I am receiving the same error 'No accounts with iTunes Connect access'. I tried the 'Technical User' fix mentioned above, but it did not have any effect.

I downloaded Xcode 7.1 beta 2 and the issue appears to have been fixed as I was able to build and package the app for third-party release. So, this seems as though it is a bug in Xcode that hopefully has been fixed.

---

Try changing the app's version number (not the build number) - e.g. from 1.5 to 1.6.

None of the other answers were working for me, and this (inexplicably) solved it.

---

This happened to me while trying to submit from a coffee shop with spotty/restricted wi-fi. Application Loader also failed with an SSL-related error message.

If none of the above solutions work for you, I'd suggest simply trying from another wi-fi network.

---

In my case internet was slow, so the problem was occurring. I changed network of my mac, the problem got solved.

---

i find a solution, just open this link

https://appleid.apple.com/#!&page=signin

In the Security section, click Generate Password below App-Specific Passwords.

so now you have generated password, now open application loader and you email and generated password thats it now you can upload video on itune using application loader software. Thanks

---

Restart your computer

Restart Xcode

ReArchive your app

Remove and re add user

This worked for me after 2 hours of troubleshooting and even trying application loader. Not sure which one. But try a combination of this, and it might work.

---