When Apple says a bundle ID is already used, it is because bundle identifiers are globally unique across all Apple Developer accounts, so once one is registered it cannot be taken again. Deleting it is not a reliable way to reuse it: a bundle ID that was ever used with an app stays reserved even after you delete the identifier, and you cannot delete an ID that belongs to another account at all. If the ID is used by an app on another account you control, you can transfer that app to your account, which brings the bundle ID with it. If it belongs to an unrelated third party, you cannot reclaim it, and the fix is to choose a new, unique bundle ID.
Short answer
A bundle ID being already used means it is registered somewhere, and identifiers are globally unique, so it cannot be reused. Per Apple's identifier guidance, an App ID is registered once, and one already used with an app cannot simply be re-registered. Deleting the identifier does not reliably free it, and you cannot delete one owned by another account. If the ID is on another Apple account you control, transfer the app to your account per Apple's app transfer guidance, which moves the bundle ID with it. Otherwise, if it belongs to a third party, choose a new bundle ID, since you cannot reclaim it.
Why a bundle ID is already used
A bundle ID, or App ID, is the unique reverse-DNS identifier for your app, and Apple enforces global uniqueness on it. That means the identifier is unique not just within your account but across every Apple Developer account, so once anyone registers a given bundle ID, no one else can register the same one. The already-used message is Apple telling you that this exact identifier is taken.
There are two situations behind it. Either you or an account you have access to registered the ID before, perhaps on a different team or a past project, or a completely separate developer registered it first. The first is often recoverable; the second is not. So the first useful step is to determine which case you are in, because that decides whether you can reclaim the ID or must choose a new one. Checking every team you belong to matters here, since it is easy to forget an old company or personal account where the identifier still lives.
Can you delete a bundle ID?
You can delete an App ID from your own account, but deleting it is not a reliable way to reuse the identifier. In Certificates, Identifiers, and Profiles, you can remove an identifier you own, yet a bundle ID that was ever used with an app, or associated with an App Store Connect record, generally stays reserved and cannot simply be re-registered afterward. So deletion frees the entry from your list without freeing the name for reuse.
There is also a hard limit: you cannot delete a bundle ID that belongs to another account. If the identifier is registered under a different developer, it is not in your account to delete, and no action on your side removes it. So do not count on deletion as the path back to a taken bundle ID, since for a used or externally owned ID it does not achieve reuse. This design is deliberate, because a reused identifier could let a new app impersonate an old one on users' devices.
Can you transfer the app to reclaim it?
Yes, if the bundle ID is tied to an app on another Apple account you control or can coordinate with. Apple's app transfer moves a published app, along with its bundle ID, from one developer account to another. So if the identifier you want is used by your own app on a different team, or a partner's account willing to transfer, transferring that app brings the bundle ID to your account, which is the legitimate way to obtain an ID that is already in use.
App transfer has conditions, such as the app meeting Apple's transfer requirements and both parties agreeing, and it moves the whole app rather than just the identifier. But when the ID is genuinely on an account you can access, transfer is the mechanism that works, because it relocates the app and its bundle ID together. What it cannot do is claim an app or ID from an unrelated third party who is not transferring to you. In that situation there is simply no mechanism to take the identifier, whatever the reason you want it.
When you must choose a new bundle ID
If the bundle ID belongs to an unrelated third party, or was used and effectively reserved in a way you cannot recover, you must choose a new one. There is no way to force the release of a globally taken identifier, so continuing to try to reuse it is time lost. Selecting a fresh, unique bundle ID is the practical and only real fix in these cases.
Choose the new identifier deliberately, using a reverse-DNS name based on a domain you actually control, such as com.yourcompany.yourapp, to reduce the chance of a future collision. Then update the bundle identifier in your Xcode project and your provisioning to match, since Xcode and App Store Connect must reference the same, unique ID. A well-chosen new identifier avoids the problem recurring and lets you move forward without further collisions.
What works versus what does not
Knowing which paths actually reclaim an ID saves effort. The table below sorts the situations.
| Situation | Can you reuse that bundle ID? |
|---|---|
| ID used by your app on another account you control | Yes, via app transfer |
| ID used then deleted in your own account | No, it stays reserved |
| ID registered by an unrelated third party | No, choose a new ID |
| ID registered but never used, in your account | Yes, reuse the existing identifier |
Read the table against where the ID lives. Reuse only works when the identifier is on an account you can transfer from, or is an unused entry already in your own account, and in the other cases a new bundle ID is the answer.
Checklist
A short sequence resolves an already-used bundle ID. The checklist below covers it.
| Check | Action | Done? |
|---|---|---|
| Find the registration | Search your accounts and Identifiers for the ID | [ ] |
| On your other account | Transfer the app to bring the ID to your account | [ ] |
| Do not rely on delete | Accept that deletion will not free a used ID | [ ] |
| Choose a new ID | If unrecoverable, pick a new reverse-DNS identifier | [ ] |
| Update Xcode | Set the new bundle ID in the project and profiles | [ ] |
The step that decides everything is locating where the ID is registered, since that tells you whether transfer is possible or a new ID is required. If it is on an account you control, transfer the app; if not, choose a new identifier and update your project.
What to take away
- A bundle ID being already used means it is registered somewhere and, because identifiers are globally unique, cannot be taken again.
- Deleting the identifier does not reliably free it: a used ID stays reserved, and you cannot delete one owned by another account.
- If the ID is on an Apple account you control, transferring that app brings the bundle ID to your account, which is the way to reclaim it.
- If it belongs to an unrelated third party or is otherwise unrecoverable, choose a new reverse-DNS bundle ID and update Xcode to match.
- Bundle IDs are account admin, not app security; scan your build with PTKD.com for the security matters an identifier does not touch.
