Post above now in more details (via ChatGPT):
Hi Scirra team,
I’ve encountered a serious issue with the Windows → WebView2 export in Construct 3 that seems related to an outdated export being cached or reused on your build server. Here are the detailed steps and findings:
🔎 Context:
I’m working on a project that is currently at version 0.1 RC3
I am exporting this project as a Windows WebView2 app
The export consistently outputs the previous version (RC2), even though RC3 has clear, visible changes
I verified multiple times that I am working in the correct .c3p project file and have the correct version set under Project Properties → Version
I even added a large, visible “RC3 Test” text label to the layout to confirm changes visually
✅ What I’ve already tried:
Confirmed I am editing and exporting the correct .c3p file
Deleted the previous RC2 folder and ZIP entirely from disk
Exported multiple times as WebView2 – always got RC2
Verified in-game using a text label + runtime.projectVersion → it shows RC2
Changed version name to RC3b, RC3c etc. – no effect
Exported via NW.js → result is correct and shows the updated RC3 version and visible layout changes
Tried the same from a private/incognito browser window (Chrome) → still got RC2 from WebView2 export
Attempted exporting after clearing browser cache, re-logging into Construct 3 – same result
No local Construct Desktop install or PWA, so everything is happening through the browser version
I also tried exporting from a project saved as folder instead of .c3p → still same result
📌 Findings:
NW.js export behaves as expected and reflects all recent changes
WebView2 export always outputs an outdated version (RC2), regardless of what’s currently in the editor
This suggests that the build server for WebView2 may be using a stale cache or outdated intermediate files
This started happening just today, so just one day after the maintenance apprently
Thank you.