Build service planned maintenance 15th May

Not favoritedFavorited Favorited 0 favourites
  • 11 posts
From the Asset Store
Pixel Sprites ala ReactorCore - Urban Maintenance - Large pack of sprites!
  • The build service has been having occasional brief outages (10-20 minutes) lately. In order to fix this we are planning to update the configuration of the build service, and this may take a few hours. This work is scheduled to take place this Thursday (May 15th) from 09:00-17:00 BST. Please be advised that the build service may be non-responsive, or builds may be failing, during this time period. Service may also be intermittent (occasionally working and occasionally stopping working again) during this time. We will post any relevant updates in this thread, including when work has finished and normal service has resumed. Thank you for your patience.

  • Update 09:01 BST: Work will be beginning on the build server maintenance shortly.

  • Update 10:47 BST: Work on the build server has concluded earlier than planned, so the build service should resume normal service from now on. If anyone notices any problems with the build server that only started today, please let us know. We will continue to monitor the build service to check its long-term reliability. Thank you for your patience.

  • Hi Ashley,

    I am trying to export my project version "0.1 RC3" via Windows Webview2.

    But it will always export "0.1 RC2" again, over and over. The export manager says: It's "RC3", but when I run it, it is "RC2".

    This does not seem to happen for NW.js (I tried that briefly), but I cannot find a workaround for Webview 2.

  • Try Construct 3

    Develop games in your browser. Powerful, performant & highly capable.

    Try Now Construct 3 users don't see these ads
  • 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.

  • This thread is about the mobile app build service which handles Android and iOS exports. It is not involved with Windows WebView2 exports.

    If you believe you have run in to a problem with Construct please file an issue following all the guidelines, as we need all that information to be able to help.

  • Hi Ashley,

    Normally, I use the ApplovinMax plugin from Chadori and the MobileAdvert plugin from Construct 3, and I export to iOS and Android without any issues. Since the maintenance on May 15th, I have been unable to export to iOS. Please reset the Mobile Advert plugin.

    "remote: Total 27 (delta 18), reused 0 (delta 0), pack-reused 0 (from 0)

    From https:/~~/Specs

    91f6ab34fa9d..b86720e7b757 master -> ~~/master

    fatal: Unable to create '~~/index.lock': File exists.

    Another git process seems to be running in this repository, e.g.

    an editor opened by 'git commit'. Please make sure all processes

    are terminated then try again. If it still fails, a git process

    may have crashed in this repository earlier:

    remove the file manually to continue.

    Running as unit: run-rfe0701312ef744b9882030958ce33c5e.scope; invocation ID: 320cd9df663246969e3e3313f283cc1a

    (node:977489) [DEP0060] DeprecationWarning: The `util._extend` API is deprecated. Please use Object.assign() instead.

    (Use `node --trace-deprecation ...` to show where the warning was created)

    CordovaError: Promise rejected with non-error: undefined

    at ~~/cordova:30:15

    at process.processTicksAndRejections (node:~~/task_queues:105:5)"

  • sgilliam30 - can you file an issue on our tracker about that? I will follow up there.

  • Hello,

    I am currently trying to export to Android but when exporting I get the log message stating that the export "Cannot connect to build server".

    I'm guessing this is related to this thread. I've tried a few times an hour apart and I have also tried an older build version which previously exported successfully.

    My internet is having no issues at the moment so I think it is an issue with the build server itself.

    Just posting this to make you guys aware and hopefully the issue is resolved soon, thanks!

  • The build server is working for me right now, so it is up and running and taking connections. So I'd guess it is more likely a connection issue on your end.

  • Ok, thanks for looking into it.

Jump to:
Active Users
There are 0 visitors browsing this topic (0 users and 0 guests)