Xcode: bundle identifier cannot be registered
Check the selected team and App ID ownership before changing a bundle identifier.
A bundle ID must be available to the selected development team. Check whether the project is using the wrong team or whether another team you belong to already registered the ID. Choose a new unique ID only for a new app that can safely change identity.
Try these fixes in order
Identify the affected target and team
Read the complete Xcode error, including the bundle ID and target. Inspect Signing & Capabilities for the selected team. An app, widget, and extension may each have separate IDs.
Check whether your organization owns the ID
Ask the team administrator to inspect its registered identifiers. If you belong to multiple teams, the ID may already be associated with a different one; select the intended team before editing the app identity.
For a new app, choose a unique ID deliberately
Use the target’s Bundle Identifier field and a reverse-domain identifier your team controls. Review related extension, App Clip, and entitlement identifiers when changing it.
Protect existing distribution identity
For an app already uploaded to App Store Connect, do not casually change the bundle ID; Apple says it cannot be changed after the first upload. Resolve team access or ownership with the administrator instead.
Interpret what you see
The ID belongs to another developer team
What it suggests: The chosen identifier is already registered outside the selected team.
Next check: Choose a unique reverse-DNS identifier you control and update related targets consistently.
The app ID exists in your team
What it suggests: The local Xcode target may be using a different team or identifier spelling.
Next check: Compare the portal record to the exact bundle ID and team on the failing target.
An extension is the target that fails
What it suggests: Its identifier must be distinct and consistent with the containing app.
Next check: Inspect the extension’s bundle ID and entitlement configuration instead of renaming the app ID blindly.
Why this happens
- The ID belongs to another team or is otherwise unavailable.
- The target selected an unintended development team.
Still not working?
Record the target, team, and exact error for Apple Developer support. Repeatedly trying new identifiers can complicate a project with associated app services.
Official sources
These steps are based on the linked documentation and general diagnostics. BugMedic has not independently tested every product and system configuration. Review commands before running them.