I just released an update (v0.9.54) to my wyBuild-enabled application.
I've had two customers write me today and say that they are on v0.9.46 but when they "check for updates", AutoUpdater says they're running the current version.
What's the best process for debugging/diagnosing this situation?
I know my wyBuild update process is working in general, and I just installed 0.9.46 on a test machine and it successfully detected the newer 0.9.54 and offered to upgrade to it, so it seems the issue is specific to these two customers. What are the next steps I should take to determine why it's not detecting the newer version for them? Thanks.
What's the best process for debugging/diagnosing this situation?
Almost always this is the problem: FAQ: wyUpdate says "You already have the latest version" when it isn't. What's wrong?.
If that's not it then it's likely a caching problem on the customer's end (a proxy caching your *.wys file, and thus always serving an old file).
My issue isn't covered by the FAQ, since I know it works on some machines so the client.wyc file must be OK.
So I guess it must be the caching issue. Is there a recommended way to resolve or work around that? If it's a proxy server issue in a large organization, I'm not sure the user is going to be in any position to get their I.T. people to clear the cache on the proxy server...
Make sure your server is configured to send out the correct headers for the *.wys file. That is, make sure there's absolutely no caching of the *.wys file.
I am now seeing this issue today. My last update was pushed out Feb 19th.
Our FTP server is Filezilla which hasn't changed in years. We have no proxy.
Assuming the issue is a caching problem, why would that suddenly develop? If not, what might some other causes be?
OK, NVM found the problem.
I had pushed out an update that inadvertently had an extra digit like so:
13.1.44826.36488 instead of 13.1.4486.36488
So all of the current client.wyc files are embedded with the higher number.
Manual replacement, here I come!
😳
You don't have to do manual replacement you can just push the next new version with a higher version than the mistake version. Version numbers don't cost anything. Most users don't care what the version number is. And since it's a "minor" version number, it probably won't screw up anything noticeable (e.g. upgrade policies, etc.).
Good to know.
Thanks.
