Fix: Development Team Not Showing in Xcode Team List

Written by

in

Quick answer: Being added in App Store Connect is not enough for signing. You must also be invited to the Apple Developer Program team at developer.apple.com and have “Access to Certificates, Identifiers & Profiles” enabled under Users and Access. Then re-add your Apple ID in Xcode > Settings > Accounts and select the team in Signing & Capabilities.

If you were invited to a client’s App Store Connect team you can see the app in App Store Connect, but Xcode still only shows your personal team under Signing & Capabilities > Team and complains about the bundle identifier or missing provisioning profile. That is expected until your Apple ID has the right Developer Program membership and permissions.

Why this happens

Apple has two separate permission systems that look like one account but are not.

  1. App Store Connect (Users and Access) controls who can manage apps, TestFlight, sales, and App Review. Being added here lets you see the app record, but it does not give you any signing assets.

  2. Apple Developer Program (developer.apple.com > Membership / People) controls who can create Bundle IDs, App IDs, certificates, and provisioning profiles. Xcode’s team list, automatic signing, and manual profile downloads all come from this system.

For years these were completely separate portals (developer.apple.com vs. iTunes Connect). Apple has since unified the login and added a bridge permission called Access to Certificates, Identifiers & Profiles inside App Store Connect, but the underlying distinction remains. If the team owner only invited you in App Store Connect, Xcode will never list that team for signing, and any provisioning profile they created for you will not attach to your Apple ID.

A second common cause is the permission level. Even when you are in the Developer Program team, you need explicit access to Developer Resources. Without Access to Certificates, Identifiers & Profiles checked, Xcode treats you as an App Store-only user and hides the team from the signing selector. This checkbox only appears for Organization teams, not Individual teams, which is why freelancers hit this more often when joining a company team.

How to fix it

Work through these in order. In most cases step 1 or 2 resolves it.

1. Confirm you are in the Apple Developer Program team, not just App Store Connect

Ask the Team Holder or an Admin to check the Developer portal:

  1. Go to https://developer.apple.com/account and sign in with an Admin account.
  2. In the top-left or top-right team switcher, select the correct Organization team. The team name must match the one that owns the Bundle ID.
  3. Go to Membership or People (the label has changed over the years, but it is the member list for the Developer Program).
  4. Verify your Apple ID appears in that list and the invite status is Accepted, not Invited or Pending. If you are not there, click Invite People and send an invite to the exact Apple ID you use in Xcode.
  5. Give you a role that allows signing. Admin always works. App Manager or Developer with additional access can also work if the next step is done, but Admin avoids ambiguity while you troubleshoot.

If you received an email invitation, accept it before continuing. An unaccepted invite will not appear in Xcode.

2. Enable Access to Certificates, IdentIdentifiers & Profiles

This is the unified permission that connects App Store Connect to the Developer portal. An Admin must enable it for you:

  1. Go to https://appstoreconnect.apple.com > Users and Access.
  2. Select your user from the list. If you do not see yourself, you were not added correctly — go back to step 1.
  3. Scroll to the Developer Resources section.
  4. Check Access to Certificates, Identifiers & Profiles.
  5. Save.

You will only see the Developer Resources section when the Apple Developer Program membership is an Organization. Individual memberships cannot invite other developers and will not show this option. If the team is an Individual account, the owner must either convert to an Organization or add your device UDIDs and send you manual profiles another way, which is not recommended for ongoing development.

After this change, it can take a few minutes for Apple’s servers to propagate. If Xcode was open, quit it completely.

3. Add or refresh your Apple ID in Xcode and select the team

Xcode caches teams and profiles per Apple ID. Force a refresh:

  1. Quit Xcode completely (Xcode > Quit Xcode), not just close the window.
  2. Reopen Xcode and go to Xcode > Settings (or Preferences on older Xcode) > Accounts.
  3. If your Apple ID is already there, select it and click Download Manual Profiles or click - to remove it and then + > Apple ID to add it again. Sign in with the same Apple ID that was invited.
  4. Select your Apple ID and verify the correct team now appears in the detail pane on the right. You should see both your Personal Team and the Organization team.
  5. Open your project. Select the project in the navigator, select the target, then go to Signing & Capabilities.
  6. Under Team, open the dropdown. The Organization team should now be selectable. Choose it.
  7. If you use Automatic signing, check Automatically manage signing. Xcode will now create or download the provisioning profile for the Bundle ID that belongs to that team. If you use Manual signing, choose the provisioning profile the team leader created for you from the Provisioning Profile dropdown. If it does not appear, click Download Manual Profiles again in Accounts.

If you still see No profiles for 'com.example.app' were found or Failed to create provisioning profile, the Bundle ID is owned by a different team than the one you selected. Confirm the exact Bundle ID in Signing & Capabilities > Bundle Identifier matches the App ID registered to the Organization team at developer.apple.com > Certificates, Identifiers & Profiles > Identifiers.

4. If the team still does not appear

Check these edge cases:

  • Wrong Apple ID in Xcode. Many developers have a personal Apple ID and a work Apple ID. The invite must match the ID signed into Xcode > Accounts. Check the email address letter-for-letter.
  • Pending legal agreement. If the Organization has not accepted the latest Apple Developer Program License Agreement, no new permissions propagate. An Admin must accept it at developer.apple.com.
  • You were added as App Store Connect only with a limited role like Finance or Marketing. Those roles never get Developer Resources access. You need Admin, App Manager, or Developer plus the checkbox from step 2.
  • Xcode cache. Try Xcode > Settings > Accounts > Download Manual Profiles and restart your Mac if the team appears on developer.apple.com but not in Xcode after 10 minutes.
  • Individual vs Organization confusion. If Users and Access shows no Developer Resources section at all, the program membership is likely an Individual. Only the Team Holder can manage certificates. The team will need to migrate to an Organization to add you properly.

You do not need to manually import a .mobileprovision file sent by the team leader to make the team appear. The team must appear first; then profiles become downloadable. If someone sent you a profile via email and Xcode still shows only your personal team, the root cause is still membership, not the file.

How to prevent it

  • When onboarding a new developer, always invite the same Apple ID in both places: App Store Connect > Users and Access and developer.apple.com > People/Membership.
  • For Organization teams, make Access to Certificates, Identifiers & Profiles part of your default role template for developers. Without it, Xcode signing will fail even with an otherwise correct invite.
  • Use groups or consistent roles (e.g., Developer + Developer Resources) so you do not have to remember the checkbox for each person.
  • Have the developer accept the email invite and verify the team appears at developer.apple.com/account before they open the project. Catching it there is faster than debugging signing errors.
  • Keep one Apple ID per developer for work. Aliases and alternate emails are the most common reason an invite looks accepted but Xcode shows nothing.

FAQ

Why can I see the app in App Store Connect but not in Xcode’s Team dropdown?

Because App Store Connect access and Developer Program membership are separate. Seeing the app proves the first one works. Xcode’s Team list comes from the second one. You need an invite to the Developer Program team and Access to Certificates, Identifiers & Profiles enabled.

Do I need to be an Admin to fix this?

You need an Admin to grant the permission, but you do not need to stay an Admin. Once Access to Certificates, Identifiers & Profiles is checked, roles like App Manager or Developer can usually build and sign. Many teams temporarily make the new developer an Admin to verify the flow, then reduce the role after Xcode shows the team.

I was given a provisioning profile file. Why does Xcode still say the bundle ID is unavailable?

A provisioning profile is tied to a specific Team ID and App ID. If your Apple ID is not a member of that Team ID, Xcode cannot use the profile and will report that the Bundle ID is not available or that no profiles were found. Fix the team membership first, then let Xcode download the profile automatically via Accounts > Download Manual Profiles instead of double-clicking a file.

Sources & credits

Parts of this guide are adapted from content licensed under CC BY-SA 4.0; this article is shared under the same license.