Invalid Bundle Identifier...

Question

Created Oct ’15

Replies 6

Boosts 1

Views 8.7k

Participants 2

I have an in the app store for about 6 years...on latest update to the app it is rejected with this message:

Invalid bundle identifier. Your app's bundle identifier can’t begin with "com.yourcompany." Bundle identifiers must be unique and contain your actual domain name, company name, or email address. Change your Bundle Identifier in your Xcode project, rebuild with a matching provisioning profile, and submit your app again.

Great advice - to change the bundle identifier. Accept its an app with thousands of paying customers. If I have to create a new app, just to change the bundle identifier, all of my paying customers will not get the updates they paid for.

Any one have an idea on how to handle this?

And wish - I hadn't just cut and pasted the bundle identifier 5 years ago when I create the app. But, I did.

Boost

Answer 1

KMT OP

Oct ’15

The advice to change would seem to mean change to match the app you're trying to update, certainly not to casually change for an app with customers, etc.

Time for a sanity on the bundle ID used in the update, the bundle ID wanted by the store and the bundle ID you think you need, I think. If those match, the immediate issue should clear itself. Be sure to do an option-clean build folder when leveling the id in the project/update.

Still no joy, contact Apple directly to see if the issue is theirs/on the backend.

0

Answer 2

kennethstott OP

Oct ’15

I don't understand this comment:

Be sure to do an option-clean build folder when leveling the id in the project/update.

Do you mean to just do a clean, before I build the project?

As best as I can determine its an issue with Apple, who created this rule, and is applying to app updates (and not just new apps). I have filed it with them, and am waiting to hear back.

0

Answer 3

KMT OP

Oct ’15

Use Xcode's 'Product' menu with the option key pressed, then select 'Clean Build Folder'.

A 'clean' doesn't seem to really do much to encourage Xcode to dump a previously indexed build and cached/stale settings, etc.

If Apple is denying updates while insisting on throwing existing users to the wolves, I have to say I will be shocked. Do you honestly think they would blindside devs and users alike in that way?

0

Answer 4

kennethstott OP

Oct ’15

Didn't know about the Clean Build Folder. Will try that.

But, it seems pretty obvious how its working. My guess is that its an error, or an unintended consequence, that they will resolve. Soon. I hope.

0

Answer 5

kennethstott OP

Oct ’15

Did your 'clean build folder' idea. But same error on submission.

0

Answer 6

KMT OP

Oct ’15

The backend is prone to acting out like this, so yes, hope it clears. Good luck in any case,

0