Code Signing "No account for team" message when signing for different developer account

65,587

Solution 1

For me the solution was to set the team in both General settings AND Build settings.

I'm using xcode 9.

Solution 2

The solution for me was to set the team in General settings of the target and in General settings of the Tests.

enter image description here

Solution 3

In my case, the error was caused by obsolete team ID in the project settings. I.e. I got a project from a person long gone. So, I just copied the team ID from error message and used a search within the project in XCode to find where this team ID is. It found me two places in the project settings, I put a new developer id there and the error was gone.

Solution 4

If you are on Xcode 13, select the project and go to Signing and Capabilities-tab, there you can change the Team and Bundle Identifier:

enter image description here

Solution 5

Apparently there was a bit of "broken telephone" going on with me and my client and we managed to solve this issue simply by selecting their team in the Signing section of the General tab in the project settings.

Share:
65,587
chmod
Author by

chmod

Updated on October 16, 2021

Comments

  • chmod
    chmod over 2 years

    I’ve been working on an app for a client using my own Apple Developer account so far while waiting for them to register a Developer account themselves.

    They have done this— and the time has come for them to be able to build and run the project on their machine, but they’re getting this error:

    Code Signing Error: No account for team "59xxxxxxxx". Add a new account in the Accounts preference pane or verify that your accounts have valid credentials. Code Signing Error: No signing certificate "iOS Development" found: No "iOS Development" signing certificate matching team ID "59xxxxxxxx" with a private key was found.

    The team ID in the error message is mine, what I’ve been using to build the project on my computers.

    Their account has already been set in their Xcode's preferences pane, and I have been added as a member to that team.

    I have worked on other projects with other developers where we could build the project simply by selecting our respective Team in the drop-down menu within the Signing section of the General project settings. For some reason when my client selects their team and tries to build the project it still produces this error.

    Does anyone know what we're doing wrong?

  • lamo_738
    lamo_738 over 5 years
    I am unable to find team preferences on General and Build settings in xcode 9.4 . can you please elaborate
  • Anton Eregin
    Anton Eregin over 5 years
    It worked for me! Build settings > Signing > Development Team > type name of development team manually.
  • eis
    eis over 5 years
    note to myself. for xcode 10, see this thread: stackoverflow.com/questions/52424462/… - TLDR: using legacy build system was one workaround that worked
  • Arno Teigseth
    Arno Teigseth over 5 years
    Interestingly I had the same problem with the Tests team only set to the wrong team. Didn't think Tests were run on Archiving… :P
  • AXSM
    AXSM about 5 years
    I have had changed my signin mechanism to manual, I did set up my provisioning profile for the specific target, but turns out you also need to setup the provision profile for test targets too. It worked.
  • DanG
    DanG about 5 years
    This worked for me, in Xcode 10.1. To find where the additional team info is needed, I searched using the ID in the "No account for team "2X94RM7457"" message. There were three places, all in Build Settings, under Development Team, such as WatchOS and WatchExtension.
  • benjamin.keen
    benjamin.keen almost 5 years
    This, worked for me too, thanks. Boy this xcode interface is a peach...
  • skyshine
    skyshine almost 5 years
    you saved my day bro
  • freedev
    freedev over 3 years
    an image worth a thousand words
  • Zachary Drake
    Zachary Drake almost 2 years
    Yeah, using Xcode 13.3, I had to search for the team in the "No account for team "59xxxxxxxx"" message. Just changing it under the "Signing & Capabilities" tab wasn't enough. It was used to sign the framework, sign the tests, etc.