I saw a lot of documentation that describes the “correct” or “recommended” format for the AppStore package identifier as follows: com.CompanyName.AppName
This certainly makes sense, and that is what we called our first two apps in the AppStore.
But in order to confuse the change in the user interface in Apple’s web interface, our latest app has finished creating in iTunes Connect with the package ID simply “AppName”. This is not edited after input and is reported to delete the application in order to try to recreate it; it blocks you from using the application name. Changing the name of the application at the last minute is obviously not a solution if you have invested in art, branding and marketing.
I was unable to download our binary until I changed the Bundle ID in info.plist to match the “wrong” version of iTunes Connect. Our app is now approved, but we haven't made it available in the store yet. I know that as soon as the Bundle ID comes out in the wild, it will forever remain unchanged. I assume that if this needs to be fixed, it should happen now before we release our application to the world.
My question is, is there a way to save the situation now by having the “wrong” package identifier? And - is this really the situation?
Is there any actual flaw for the package identifier to be formatted the way we have it?
I wrote Apple twice in the past week asking for help / advice on this situation, but have not heard back.
I see a lot of people writing about the “proper” way to format the Bundle identifier, but what is the reason for the incorrect formatting? Unlike a convention, what makes one way more right than any other?
Do we encounter any potential problems going to the store to live? Should we hold our release until we hear from Apple about this?
Thank you for your understanding, experience and wisdom!
source share