Unable to reuse Bundle ID across accounts after TestFlight-only usage

Question

kedar-d OP

Created 16h

Replies 1

Boosts 0

Participants 2

I’m working with two Apple Developer Organization accounts and ran into an issue with Bundle ID reuse.

In Account A:

I created an App ID: com.example.app Created an app in App Store Connect using this Bundle ID Uploaded builds and used it only for TestFlight (never submitted for App Store review)

Now I want to move development to Account B.

However:

When I try to create the same Bundle ID (com.example.app) in Account B, I get:

“An App ID with Identifier 'com.example.app' is not available.”

What I’ve considered:

The app has never been submitted or approved
It has only been used for TestFlight testing
I have not yet attempted App Transfer (since it requires an approved app)

Questions:

Is a Bundle ID permanently locked to the original account even if the app was never submitted for review?
If I delete the App ID and app from Account A, will the Bundle ID ever become reusable?
Is submitting the app once and then using App Transfer the only way to move this Bundle ID to another account?

Boost

Answer 1

DTS Engineer OP

Apple

7h

Thanks for the post. Once you use a bundleID, you are now attaching that one to the development portal. That’s why is very important to keep the com.company_or_portal.appname so they are always unique.

Because you created the bundle ID, that Bundle ID is now locked to Account A until the app is approved and transferred. If you had only created the App ID in the Developer Portal, you could delete it. However, once a build is uploaded (even just for TestFlight), binds that Bundle ID to that app record. It can no longer be edited or removed. You actually cannot delete the app from Account A. I’m not sure but to permanent delete it you need to least one approved version and its current status is Developer Removed from Sale, Rejected, etc. But I need to check on see if this is still the way.

You could do an app transfer, but I think the best way will be to create a new Bundle ID in the new portal with the prefix completely different as first you’ll have to submit the app for review in Account A. Get it approved by App Review. Release it (you can release it as "Unlisted" or immediately remove it from sale if you don't want it public). Initiate an App Transfer from Account A to Account B.

So my suggestion is to use a new Bundle ID. If you haven't launched the app yet, the path of least resistance is almost always to slightly modify the Bundle ID for Account B. For example, if you wanted com.example.app, change it to com.example.app.ios, com.example.myapp, or co.example.app. This avoids the headache of going through App Review on Account A just to transfer it.

Albert   Worldwide Developer Relations.

0