“Bundle identifier is not available” in Xcode: how to fix it
What “Failed to register bundle identifier” means, why it happens when no app on the App Store uses the ID, and how to pick one that will work.
Xcode stops you with: “Failed to register bundle identifier. The app identifier “com.example.app” cannot be registered to your development team because it is not available.” Here is what that means and how to move on.
Why the bundle ID isn’t available
- A bundle ID can belong to only one Apple developer team. If anyone has registered it as an App ID, nobody else can.
- Registering doesn’t require publishing. Many IDs are held by apps that never shipped, so the App Store shows nothing.
- Generic IDs like com.app.name or com.test.myapp are the most likely to be taken.
The fix
- In Xcode, select your app target, open Signing & Capabilities, and change the Bundle Identifier.
- Use a reversed domain you own, like com.yourcompany.appname. Another team can’t realistically hold an ID under your domain.
- Let Xcode register it again with automatic signing, or add it under Certificates, Identifiers & Profiles in your developer account.
- If the app has extensions or widgets, update their IDs too. They must start with the app’s bundle ID.
The bundle ID is permanent once your app is on the App Store, so pick it together with the name. Our bundle ID guide covers the rules on iOS and Android.
Questions people ask
Can I find out who owns a bundle ID?
Only if their app is published: Apple’s public lookup returns the app for a bundle ID. Registrations of unpublished apps are private.
Does the bundle ID need to match my App Store name?
No. Users don’t see it. It only needs to be unique.
Can I change my bundle ID after release?
No. A different bundle ID means a new App Store app, without your ratings and existing users.
Check your own name
Domains, both app stores, bundle IDs and every live site using the name, in under a minute.
Check a name