updates does not happen in one step but in many steps

I also just have checked the wyserver.wys file and in the tab for 2.3 version is points to path: 2.3.to.2.3.2So i see not obvious reason why would it do the update in two steps, first to 2.3.1 and then to 2.3.2

I'll assume you're using the AutomaticUpdater. When an old update is already downloaded and ready to install, then the AutomaticUPdater will install that (instead of discarding it and downloading the newer version).

Yes indeed we use automatic updater. Is wyUpdater doing it differently?Is there any plan to change it in the future? It seems that our clients notice that as an inconvenience.

What I see is that freshly installed 2.3 checks for updates and it fetches 2.3.1 instead of 2.3.2 (the newest version).It is not so that 2.3 was installed and 2.3.1 is the newest version and in the mean time 2.3.2 came available so 2.3.1 could be discarded (just an optimization).

Do you have any idea how to achieve the second question I have posted?

Thx for help!

Is wyUpdater doing it differently?

The AutomaticUpdater caches updates until they can be installed. wyUpdate doesn't keep updates past the life of the wyUpdate instance.

You can force the AutomaticUpdater to recheck after you've recently installed and update to install any other pending updates.

Ok. Our client is annoyed by the multiple steps of updates. What concretly we can do to force wyUpdate to fetch only the highest available update and not all intermediary updates?

I can remove by hand the intermediary updates on the server (2.3->2.3.1) when releasing 2.3.2 so whyUpdate will see only 2.3.2. But is is just a short therm workaround.

Thank you for fast response.

What concretly we can do to force wyUpdate to fetch only the highest available update and not all intermediary updates?

Immediately install an update upon receiving it. Use the events, properties, and methods to detect & install a new version immediately.

So we can detect the newest update and skip the intermediate by using properties, method and events?

Patches are direct. wyUpdate never downloads or installs intermediate updates (not yet -- we're adding it as an option in wyBuild 2.7). So what's happening, then? Your app is downloading and extracting an updating .... time passes ... the user eventually installs the update, but by the time they install the update you've released N other updates.

So how do you get the user to install the update immediately upon detecting it? Use the properties, events, and methods to detect, download, and install the update immediately.

We use autoUpdater in automotic mode so it installs new version at next restart (or user clicks to do it immediately).

Well we wish it was that the lates update only is installed. This is not what we see happening. Fresh installation of version 2.3.0 should (as you say) update to the newest 2.3.2, however this freshly installed 2.3.0 downloads 2.3.1 and then downloads 2.3.2. Depending on user action it results in 2 restarts or at least visible action of downolading 2.3.1 and few seconds later 2.3.2.

This is not what we see happening. Fresh installation of version 2.3.0 should (as you say) update to the newest 2.3.2, however this freshly installed 2.3.0 downloads 2.3.1 and then downloads 2.3.2.

This would only happen if you changed the download site in the client.wyc in 2.3.1. If your download site is the same, then if the user has 2.3.0 (and no pending updates are ready to be installed) then 2.3.2 will be downloaded and installed.