| Thanks for your reply Stephane.
One cause of the problem with the updater has been somewhat identified.
The full installer of my application bundle includes a folder inside "Resources" with a set of sound files. Since these files do not change with the updates, I do not include them in the updater package. In testing on my machines, if I don't at least leave the empty "Sounds" folder in the Resources folder, the update appears to delete this folder and its contents.
Leaving the directory structure in place, correctly leaves the required sound files post update on my machine, but seems to still remove these files on some user's machines. I am trying to verify this.
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?
Regarding the permissions issues:
- Which authorization are you requiring?
I'm requiring administrator privileges to run either the installer or the updater. The files in the package mostly show me as the owner, read-only privileges or read-execute for others. Is it normal to leave myself as the owner, or more common to set this as root or something else?
The resources folder must have read-write privileges for everyone, since the app will write encrypted registration data to this folder on its first run. It's possible this would be better if it was in the application support folder, but I prefer the concealed location in the app package.
- Do you use a default location that is not '/'? No.
- Which OS version is the update run on when it does not work?
Regarding the "does not runt at all" issue:
- Do you take into account the fact that the application may have been moved by the customer?
- Do you use a Locator to look for the location of the application? This is a valid concern. I don't currently check the installed file location, which would obviously foil the update.
- Do you use Resource Fork for resources in your application? If so, do you split fork when you're creating the packages? I'm not using resource forks, however the sound files still have resource fork data. I would like to confirm that this data is not essential. At the moment the resource fork data is being preserved in the installer & updater pkgs.
best wishes,
Robert Carroll RSM Records Toronto
|