site_archiver@lists.apple.com Delivered-To: installer-dev@lists.apple.com On vendredi, septembre 7, 2007, at 01:35 PM, Robert Carroll wrote: HI, Regarding the permissions issues: - Which authorization are you requiring? - Do you use a default location that is not '/'? - Which OS version is the update run on when it does not work? Regarding the "does not runt at all" issue: - Do you use a Locator to look for the location of the application? _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.a... I'm new to this list, so please excuse me if this has been previously covered. I am using packagemaker built installers for both the full install and the updates for my software. So far, the installer works as expected on all client machines (with a couple of minor exceptions). The updater on the other hand, fails on about 25% of user's machines. That is, the updater process appears to work and exits correctly, but the updated app usually has lost the user's authorization, or just will not run at all. The updater is set up to replace the app file in the MacOS folder of the client's currently installed version. It shouldn't touch any other files in the same package (ie. resource files or the encrypted registration info) and doesn't not replace or change anything elsewhere on the computer. Is this a known issue? Is there a safer and more reliable way to accomplish this kind of update? - Do you take into account the fact that the application may have been moved by the customer? - Do you use Resource Fork for resources in your application? If so, do you split fork when you're creating the packages? This email sent to site_archiver@lists.apple.com