After releasing a game update, opening it from the Telegram bot still showed the old version.
Clearing the server cache did not help. Network inspection showed that Telegram did not request the resources again because the updated build used the same filenames and paths.
Custom scripts that appended version suffixes broke Cocos Creator’s file index. The built-in solution is to enable MD5 Cache in the build settings:
The generated assets then contain content hashes in their filenames:
Test the build locally to ensure every resource resolves, then upload it to the server or CDN. Changed content now receives a new URL, while unchanged assets can remain cached.
