Ashley's Forum Posts

  • We updated the target API level to 30 a few weeks ago for r231 and this is the first I've heard of it.

    Unfortunately signing is complicated and it's going to be difficult to make changes on the build server - I'm not sure when we could get this updated to the signature scheme v2, if that is indeed now required.

    It still looks confusing: their documentation seems to specify four signing schemes (v1, v2, v3 and v4), and v2 seems to have specific support requirements (Android 6+ only)... maybe we should put back the target API version until we figure this out. In the mean time you can try building an unsigned release APK and sign it yourself as per Google's documentation.

  • I just tried creating a new key in Construct 3 and doing a signed release APK build with it. It worked fine.

    One thing that may be at work here is IIRC the keytool used by the server does not support using a different password for the key and the keystore. For this reason we removed the option to use two different passwords when creating a keystore in Construct. But we made this change some time ago and it's been in place for some time. We preserved the option to specify separate passwords when using an existing keystore though, for backwards compatibility with existing keystores. Since then we haven't changed anything apart from the target SDK version, since Google require that, and as far as I can see the signing process still works, at least with a newly created key.

    I'm afraid I can't comment on third-party software - whether or not it works is out of our control and we can't be held responsible for it, so it may be more fruitful to get in touch with the developer of the tool you use.

  • Please file an issue following all the guidelines - we need all the requested information to be able to help.

  • Apologies for the trouble - see this forum thread for updates.

  • Are you using any third-party addons? If so the addon developer may need to release a small update. You'd have to contact the respective developer about that. It's difficult to say more without seeing your project.

  • The IAP plugin uses cordova-plugin-purchase, and it looks like they've updated that to use the new Google Play Billing library v3. I'll update that for the next beta release.

    • Post link icon

    It's working fine for me. I just rebooted the build server in case that helps.

  • For the record this was announced about a year ago in the blog post Sunsetting Construct 2.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • If a build fails due to the use of a third-party addon, you'll have to contact the addon developer for support on that.

    If a build fails without using any third-party addon, please file an issue following all the guidelines.

  • New JavaScript features must be supported by all of the browser, the editor JavaScript parser, and Closure Compiler, to work everywhere. New features can take several months to appear in all three places. Sooner or later we'll update Closure Compiler and it will start working. This process will probably repeat for other new JavaScript features in future.

  • We've already contacted Sony and Nintendo, more than once, to no avail.

    That's why I say it's probably more likely they will act on it if they see there are lots of potential developers who are asking for it.

  • There wasn't previously any scripting API that covered this. I've added IWorldInstance.getMeshSize() for the next beta.

  • Apologies for the trouble - see this forum thread for updates.

  • Apologies for the trouble - see this forum thread for updates.

  • Apologies for the inconvenience everyone. We identified this as a significant problem earlier today and I've been posting updates in this thread including some possible workarounds. In order to keep updates in one place I'll update that thread with further news so please keep an eye there.

    In order to mitigate the problem, today's r234.2 release switched to a new developer account for accessing Google Drive. Unfortunately before this can return to being fully operational it must be approved by Google. This could take several days - I don't really know how long, but I've tried to emphasise the urgency of this in our submission to Google. I think at this point we just have to wait and see. Hopefully you can find a workaround in the mean time. Sorry again for the trouble.