On Wed, 14 Dec 2011 05:14:36 -0500, Bill Cheeseman <wjcheese...@gmail.com> said: >Search the archives, and you will discover that you are likely experiencing a >well-known issue that has been around for a very long time. It typically only >affects the developer, not your users. It is especially annoying to the >developer if another, older version of the application is still on your >computer, in the Applications folder or perhaps in the form of earlier build >products that are still sitting around, because then trashing the help caches >and forcing an update won't necessarily stop the system from using the old >version of your Help folder in an older version of your application.
And not just with help, either. I've been in situations where a developer was sending me new versions of an application several times a day, and it would sometimes happen that I would double-click a new version and an older version's code would run. (This resulted in some really strange conversations about the behavior of the application.) There's some underlying caching mechanism here. As you rightly say, the solution is to trash the old version *and empty the trash* before launching the new version. m. PS I've also quite often seen it happen that I'll update my code for an iOS app I'm developing and run it and an older version of the app will run, but this is for a different reason, I think. -- matt neuburg, phd = m...@tidbits.com, <http://www.apeth.net/matt/> A fool + a tool + an autorelease pool = cool! Programming iOS 4! http://www.apeth.net/matt/default.html#iosbook_______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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 arch...@mail-archive.com
