Consequences of Changing CFBundleName? iOS 7 and iOS 8

The wrong app name is displayed in the Apple Watch app in the My Watch list. It shows the CFBundleName contents. Advice has been given in the Apple Developer forum to set the CFBundleName and the CFBundleDisplayName in all 3 apps (iPhone App, Watch App, Watch Extension). Changing the CFBundleDisplayName is not enough.

So, I am considering changing the CFBundleName. Our team has an existing app. I need to know what will happen if I do change the CFBundleName. The Apple doc Core Foundation Keys says it's "The short display name of the bundle".

Items of concern are:

• Existing App Updates Succeeding
• Accessing old content via NSUserDefaults.standardUserDefaults
• Accessing old content via NSKeyedArchiver (un)archiveRootObject to/from NSSearchPathForDirectoriesInDomains(NSDocumentDirectory, NSUserDomainMask, YES) related location.

The SO post Should I avoid changing the CFBundleName of my iOS app for a new release? is what got me concerned about app updates.

We store stuff that the user has paid for into the NSSearchPathForDirectoriesInDomains(NSDocumentDirectory,.. related location.

It's important to get this right and treat our existing users well. I appreciate any help. Thanks!