Been distant working on a plethora of other projects. What is the best means of having the app search for updates and then take the user to an install page or something of the sort? This is for a Desktop platform.
This was the first I heard of Kaju, Paul. I bought your UltraUpdater several years ago and it works great. I've modified it somewhat (i.e.: I put the update request into a thread to free up the UI, etc) but at this point, I don't know if I see a need to change it unless Kaju is way better...
@Kem T "Way better" is in the eye of the beholder. :)
If UltraUpdater works for you, great. If there is an advantage to Kaju, you'll find it in the Read Me at the site.
Intriguing. I'm going to have to look at it. I like the idea of being able to flag something as a paid update. I've had numerous times when I put it in the release notes that it's a paid update, but people still download it and then complain when they can't run it!
I like the idea as well that it just updates and doesn't need to run an installer app...Cool...
@jean-yvespochez from what I read, Kaju is not suitable to work with the app store ? ( i.e. not sandboxed ?)
No automatic updater can work in a sandboxed app. They also are not permitted in applications available on the app store. The store handles the updates for you, you don't have a choice.
But a correctly sandboxed app, regardless of the app store, simply cannot use an automatic updater. Even if you used an installer to setup a service to handle the updates, that service app would too need to be sandboxed and thus could not update the main app.
@jean-yvespochez if you compile en app that has Kaju libs inside, even if it is not launched, it will be refused by apple if you submit the app right ?
I don't see why, it's just Xojo code. There are no "libs" per se so, as Beatrix says, just don't call the code in the MAS version.