I have several games with web versions, and whenever I’ve updated them, the update is reflected instantly on Itch.
In all my years on Itch, yours is the first and only case I’ve heard of involving this specific problem.
For that reason—and I’ll say it again—I’m almost certain the issue is on your end; however, years of working in IT have taught me that no matter how sure you are about something, it’s always best to double-check.
Add a text element to the game that displays the version number so you can quickly tell which version you’re playing. Make sure you’re uploading to the correct channel and that you aren’t playing a version stored in a local cache on your machine.
If, after testing and ruling out all potential issues on your end, the problem persists, your best bet is to contact support with all the relevant technical details—because if it turns out to be an Itch-side error, it would be a significant one.
I suspect that, somewhere along the line, a cache is causing you to play an older version of your game.
no matter how sure you are about something, it’s always best to double-check.
Yes!
This is good advice. Not only for software. Humans often make errors and are adamant that they are right, not even allowing for the possibility to be in error. Or they tell intentional lies and deceive people. Very popular in politics. But software can have very obscure bugs, especially if you take things for granted. Like how a float is handled. Or mtu in networks.
For this problem, as far as I know there are data servers with load balancing. It could be possible that the host serving the game was not updated fast enough. Or the isp is using a proxy.
There was no time frame given, how fast the update was checked, and if this would resolve by itself after a while.
Just to clarify, I don't doubt what you're saying.
What I do question is whether the issue lies with the Itch servers (for the reasons I explained earlier). It’s most likely that there’s an error in one of the steps—perhaps during the build and push process, or maybe a caching issue when running the game.
Have you tried running the local version of your game (the same one you're pushing) to verify that it is up to date?
Do you use the automatic or manual versioning method when pushing?
Have you checked the version Itch reports via the dashboard or API to confirm it matches the one you're uploading?
EDIT: When you perform a push, you also have the option to preview it so you can see what changes will be made. This can be useful for verifying exactly what is going to change.
On "how can I tell the difference": right after the push, run butler status with your user, game and channel. It prints a table with each channel's current build id and version. If that already shows the new version while your title screen shows the old text, the stale copy is between the server and your browser, and a private window is a quick test. If the table still shows the old build, the push never landed.
We check this way because a butler push of ours once printed an API error (400) and still exited with code 0. Only the status table showed the build was missing.
Written with AI help.
