ITMS-90477: Invalid Bundle Identifier - Attempting to change bundle identifier

Here I tried to explain the problem more clearly.

We have an iOS App with watch app and its extension. It's also available on the store. We developing a new version of this app.

The problem that we faced is we accidentally deleted the bundle identifiers of WatchOS and WatchOSExtension from both Xcode side and AppStoreConnect "Identifiers" section.

Scenario 1 - When we upload a new binary of new version (2.4.0 Prepare for Submission Version) with new bundle identifiers that we registered from App Store Connect, we get back a mail about "trying to change bundle identifier" naturally.

For example: our 2.3.3 bundle identifiers also deleted identifiers are; "com.company.app.watchkitapp" and "com.company.app.watchkitapp.watchkitextension". When we use new registered identifiers (com.company.myapp.watchkitappp) mail comes like;

"ITMS-90477: Invalid Bundle Identifier - Attempting to change bundle identifier from com.company.app.watchkitapp.watchkitapp to com.company.app.watchkitappp is disallowed for bundle My App.app/Watch/My App Watch.app."

Scenario 2 - Yes we deleted our watch identifiers. So when we try to register these identifiers back again, it says;

"An App ID with Identifier 'com.company.app.watchkitapp.watchkitapp' is not available. Please enter a different string."

Any help is appreciated.

Thx.

I have the same problem.

Hi,
I have the same problem. are you able to find the solution? because of this Bundle Identifier Issue, Apple reject submitted new build.

At that time we were struggling to transfer the application to another account when we got this error. I don’t know if we faced with some kind of bug but the problem was fixed when we deleted the identifiers in all accounts and added them again. I don’t know if this solution fit for you but you may consider this.

im some problem what can i do

Same issue here.

I am having the same issues. Was anyone able to figure it out? I contacted Apple Support and it has been 20 days and they just keep saying that they are still looking at the issue but no meaningful response.

Any help will be appreciated.

@rlarrosa, I'm exactly in the same situation. I have not deleted my Apple Watch identifier of my app which has been live and getting updated every couple of months since 2018. A month or so ago I wanted to push a new version and suddenly xcode says that my Apple Watch identifier is not available to my team. Apple support has been looking into this for over a month and this is going no where. Meanwhile competitors are pushing new releases and I'm blocked.

Support recommended using a new identifier for the Apple Watch and I said that it will confuse end users since they will end up with 2 apps looking the same but only 1 working. I gave it a try and I'm now hitting this error of this thread which makes sense since apps should not change their identifiers.

In summary, I have no clue how my identifier got removed from my account and Apple support is taking a long time to solve this which honestly seems like they will not solve it. At the moment I'm blocked and not sure if there is any solution to this. I cannot release a new app and lose the existing user base. Very disappointed at the quality of support I'm receiving.

Identical problem. Opened a case with Apple Support two months ago as well and still no updates. The only answer I get is that there still working on it with no update in status. This is a debilitating problem because there's no way to work around this without changing the name of the app and resubmitting. Which is completely unacceptable since we have users that have purchased the app or on an active subscription. To make matters worse, with iOS/iPadOS 15 and watchOS 8 now out, we can't patch the app for the OS updates. I feel like I'm being held hostage with no options. I understand that my app is only one of millions on the App Store, but this issue is not of my making. I have no idea how the bundleID got changed in the App Store. Disappointed is not a strong enough word for this.

Hi, I have the same issue and since I wrote that it's not me but a problem with Apple, I no longer get a response from support. Have a critical update and can no longer update. Disaster.

Have you been able to solve the problem in the meantime?