watchkit - Consequences of Changing CFBundleName? iOS 7 and iOS 8 -


the wrong app name displayed in apple watch app in watch list. shows cfbundlename contents. advice has been given in apple developer forum set cfbundlename , cfbundledisplayname in 3 apps (iphone app, watch app, watch extension). changing cfbundledisplayname not enough.

so, considering changing cfbundlename. our team has existing app. need know happen if change cfbundlename. apple doc core foundation keys says it's "the short display name of 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 post should avoid changing cfbundlename of ios app new release? got me concerned app updates.

we store stuff user has paid nssearchpathfordirectoriesindomains(nsdocumentdirectory,.. related location.

it's important right , treat our existing users well. appreciate help. thanks!

items of concern are...

none of affected. change away! app uniquely identified bundle id. defaults , archiving not consult name in way. names user-facing strings , all are.


Comments

Popular posts from this blog

asp.net mvc - SSO between MVCForum and Umbraco7 -

Python Tkinter keyboard using bind -

ubuntu - Selenium Node Not Connecting to Hub, Not Opening Port -