Tagged: General Coding
MemberApril 27, 2019 at 4:41 pm
I don’t use AutoUpdater. I wrote a similar tool, Molu Update Server, circa 2007 that handles all update tasks except replacing the Omnis engine itself. Omnis Studio 10 has an option of running a script at launch, which promises to ease the update process.
The challenge of writing to the xcomps directory is the access permissions enforced by the operating system. I am using an iPad at the moment so I cannot verify this, but any file that is put into the “first run” target directory in the user application support area should be writable by an Omnis app or external app designed to update your application.
MemberApril 28, 2019 at 6:17 pm
To follow up, the xcomp directory in the application tree, not in the app data directory created by firstrun. So, you will need a method to assert proper permission to add to the xcomp directory. FWIW, it can be done; we do it although keeping up with new rules from Apple is a challenge. If you support windows only, you may enjoy an easier time with it.
MemberJune 5, 2019 at 9:52 am
Have a look at https://developer.omnis.net/onlinedocs/Programming/01omnistools.html#auto-updates
You can use the update.sh/bat file to copy over new XCOMPS or externals.
Log in to reply.