Reputation: 1253
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?
Upvotes: 82
Views: 109481
Reputation: 3367
Under 'select a method for distribution' select 'use custom'
this will allow you to specify a provisioning profile. Using the 'App Store Connect' option seems to be dependent on automatic signing.
In my case, automatic signing is not an option. I build apps for multiple clients. I manually send the admin my CSR in exchange for a distribution certificate and provisioning profile.
This error started for me with Xcode 15.4
Upvotes: 3
Reputation: 36373
In my case, it was because the account expired (it needs an annual fee). If this is a possibility for you, be sure to double-check that with the account owner.
Upvotes: 0
Reputation: 3098
1-re-login into your account in xcode
2-restart mac
3-Uncheck Auto manage sign
4-Re-check Auto manage sign
Upvotes: 0
Reputation: 31
Another fix I found (Xcode 11) Select your project root: go to the 'signing & capabilities' sub-window, and for the field 'team' your team will shown as red because not found, and reset this field.
Upvotes: 2
Reputation: 1779
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
:
Upvotes: 5
Reputation: 31
Using Xcode 11 and having already suceeded to build and archive my project before (having my account settings and build settings already well configured with theire keys and certificates), I fixed it on my side with 'Product > Clean Build Folder' and then re-launched a build (doesn't work everytime unfortunately).
Upvotes: 0
Reputation: 1142
using xcode 10 here ... my appleID wasnt signed in, so i rectified that via preferences > accounts > re-entering my password.
BUT, that still didnt work even after cleaning and restarting xcode.
i finally resolved this by doing file > workspace settings > build system ... and choosing "Legacy Build System" from the dropdown.
Upvotes: 3
Reputation: 293
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.
Upvotes: 4
Reputation: 6098
The solution for me was to set the team in General settings of the target and in General settings of the Tests.
Upvotes: 65
Reputation: 912
For me the solution was to set the team in both General settings AND Build settings.
I'm using xcode 9.
Upvotes: 52
Reputation: 1253
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.
Upvotes: 2