Implications of changing an app's bundle identifier
Implications of changing an app's bundle identifier
- Subject: Implications of changing an app's bundle identifier
- From: Bill Cheeseman <email@hidden>
- Date: Sat, 24 Feb 2007 15:17:28 -0500
- Thread-topic: Implications of changing an app's bundle identifier
My products have used a bundle identifier in the Info.plist file that
includes the company's name, in compliance with standard Mac OS X protocol.
Now, however, for good and sufficient business reasons, it is necessary to
change the bundle identifier in the next versions of the products.
I wonder what repercussions I will have to deal with in my code when I do
this. It occurs to me that others have likely been through this process,
since company names do change.
The only thing I've thought of so far is that a user of a previous version
will suddenly appear to have "lost" all the old preference settings, because
the preference files are named using the old identifier. Offhand, I think I
can easily hard-code a one-time search for the old file names and rename the
files.
Is there anything else I should watch out for? In particular, I wonder
what's going to happen in the Launch Services database in terms of the
Finder recognizing the new version as the owner of old document files. (I'm
not concerned about UTI's for Spotlight, because I haven't used UTI's in
previous versions, but it would be interesting to hear thoughts on that
issue, as well.)
Bill Cheeseman
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden