On Dec 16, 2011, at 1:36 AM, Charles Srstka <[email protected]> wrote:
> On Dec 15, 2011, at 10:28 PM, Mark Munz wrote: > >> I've not seen Mac OS X fail to run an app I've double-clicked on, but >> it is notorious for grabbing seemly random old versions of plugins >> like Automator actions, quicklook plugins, Services from older apps >> that are still around -- sometimes giving precedence to apps on >> non-boot volumes (over one on the boot volume). >> >> It is especially an annoying mess for developers, who are more likely >> to have multiple versions lurking about. > > Don’t forget document-application bindings. Double-click a file that belongs > to application “Foo” when you have both Foo 1.0 and Foo 2.0 installed on your > machine, and who knows which one you’ll get — but boy, does it ever love to > pick things out of ~/Library/Mail and ~/Library/Mail Downloads. > > If Apple updated LaunchServices to have it look at the CFBundleVersion when > multiple applications have the same bundle identifier and always pick the > latest one, I’d be a happy man. I believe this is what it's supposed to be doing. Part of it might be a LaunchServices bug, but another part of it might be that your CFBundleVersionNumbers don't conform to the spec that LS is using: http://lists.apple.com/archives/carbon-dev/2006/jun/msg00139.html Our build system currently produces bundle version numbers of the form NN.0.SVNREV for bundles built from trunk. This doesn't conform to the format Christopher posted. Bundles built from branches have the form NN.N.0.SVNREV, which _does_ conform. I am curious if that is the reason LS prefers to launch old versions of my apps rather than the version under development. --Kyle Sluder_______________________________________________ Cocoa-dev mailing list ([email protected]) Please 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: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [email protected]
