WebView2 export always loads an old version of the game

Hi,

I’m having a problem when exporting my game using Windows (WebView2).

The build always loads an old version of the game, not the current one I’m editing.

Inside Construct 3, the Debug works fine and shows the latest updates, but after exporting, the .exe runs an outdated build.

I’ve already tried changing the App ID, project name, clearing cache, deleting export folders, and reinstalling WebView2, but nothing changes.

It looks like the exporter is reusing a cached version of the project instead of the new one.

Can someone from Scirra check this?

Thanks!

— Clayton Lima

The export option does not cache anything. It only loads the exported resources in the app folder. So this type of problem should not be possible.

I would guess you've made some kind of mistake, but it's hard to say without more details. (Generally to be able to help we need the information as required in the bug report guidelines.)

Hi!

I just wanted to update the thread — I found the solution.

The issue wasn’t in Construct 3 or in the WebView2 export.

What was happening is that Windows/Steam was always trying to launch the Steam version of my game instead of the local exported build, even if I changed the name of the .exe or exported to a different folder.

So every time I tried to run my local build, Steam intercepted the launch and opened an old version that was already installed.

The fix was simple:

I enabled Developer Mode in the Steamworks plugin and added the file:

steam_appid.txt

with my App ID inside the exported game folder.

After doing that, I was able to run my local exported build normally, without Steam redirecting or forcing installation.

So everything is working now.

Thank you!