- Install4j execute launcher silent updater install#
- Install4j execute launcher silent updater update#
There is no need to call the Auto-Updater for a second time to launch your application using the -restartapp flag.
Implement reliable silent installation progress tracking such that my agent will be able to know when it can make the 2nd call safely. However I expect that in order for this to work the updates will have to finish installing before the 1st call terminates anyway, therefore I can safely make the 2nd call anyway in this scenario.ģ. Make the -restartapp flag work in the first call such that I do not have to make a 2nd call. Make the event chronology fit what is expected as above.Ģ.
What I can think of are these 3 solutions.ġ. I want to confirm is whether all I have described above is the expected behavior and to ask for possible solutions if it is expected. The reason why there are two calls is because the -restartapp flag only works if all updates have been installed which at the time of the first call is not the case. One more problem is that if the application is restarted while updates are still installing it may result in resources being locked, which results in a force reboot without warning. 10 seconds waiting time is sufficient for 2 small patches amounting to 48KB but insufficient for a 120MB~ full installer which is necessary for major updates. Presently my agent has a mandatory wait time between the calls in order to allow the updates to finish installing but this wait time is static and cannot really cater for the difference between different machines nor for large updates.
Install4j execute launcher silent updater install#
Observed Event Chronology - 1st Call Start -> 1st Call End -> Updates download and install in the background -> 2nd Call Start -> 2nd Call End -> Updates finish installing in the backgroundĮxpected Event Chronology - 1st Call Start -> Updates download and install in the background -> Updates finish installing in the background ->1st Call End -> 2nd Call Start -> 2nd Call End This results in the observed event chronology below. The problem is this, when the 1st call is triggered the updates start to be downloaded and installed only after the 1st call have ended instead of before the 1st call ends. After this call terminates, it makes a second call to the Updater with a -restartapp flag to restart the app.
The first is a /silentall call so that all updates can be set to be installed.
Install4j execute launcher silent updater update#
Presently my application will start a small program, a agent of sorts that will make the necessary calls to the Updater before the main application terminates itself so that the update can proceed without any resources being locked. One more use case for this request that hopefully will bump this up the priority list as this can be potentially blocking for me.
0 kommentar(er)
