Re: Implications of changing an app's bundle identifier
Re: Implications of changing an app's bundle identifier
- Subject: Re: Implications of changing an app's bundle identifier
- From: Ricky Sharp <email@hidden>
- Date: Sun, 25 Feb 2007 15:52:50 -0600
On Feb 25, 2007, at 2:44 PM, Uli Kusterer wrote:
Am 24.02.2007 um 22:00 schrieb Ricky Sharp:
I just ran an experiment (I became curious as well) as to what
happens with signature changes. In my example, I created an app
with some signature and had it create a document with an extension
unique to the app.
I then removed the app, and rebuilt it with a different
signature. Double-clicking on the document launched the new
instance just fine. I then did a third change to the signature
and also renamed the app (bundle name change). Bringing up the
documents inspector, the 'Open with' popup correctly listed the
app with the new name (it also didn't have an entry for the old
app). Thus, there appears to be quite a bit going on to attempt
to preserve document bindings to the proper app.
Ricky, did you also check what happens if the old version isn't
deleted? What happens when you have two apps claiming the same type
with different bundle identifiers? Which one will Launch Services
pick? The one with the higher version number? The one last copied
to the hard drive?
I'm sure there's some pattern to it all, but I cannot be 100% sure of
what it is.
For the apps I write, I of course have every version ever built. I
also have six drive volumes; many which contain a copy. I believe my
documents tend to be bound to the highest version (or last-launched
on the boot-volume?). During development, I tend to run apps on my
project volume which is not the boot volume; that may or may not be
updating launch services appropriately.
Also, the demo flavor of my app used to share the same creator and
other bundle attributes as the release version. In the past, if I
brought up a document's properties, it was sometimes bound to the
demo application. For the latest version, I've changed that to have
the demo flavor use unique metadata. What's funny is the demo flavor
never writes any files (contains canned data) so it was amusing for
it to claim the documents that release version made. But, that would
make sense as it had the same bundle identifier, etc.
___________________________________________________________
Ricky A. Sharp mailto:email@hidden
Instant Interactive(tm) http://www.instantinteractive.com
_______________________________________________
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