Ashley's Forum Posts

  • It's definitely not a virus. It must be a false positive by MalwareBytes. I guess it's also possible that your system is infected, and it also infected the APK that you downloaded to your system.

    If you did a debug or unsigned APK export for testing, it is probably not trusted since it is missing the digital signature that verifies the author. You might need to enable some extra developer settings on your device to allow testing unsigned APKs.

  • (viewportright("HUD")-viewportleft("HUD"))/2

    The correct expression is:

    (viewportright("HUD") + viewportleft("HUD"))/2

    i.e. plus, not minus. You want the value half way between the two, not half the difference.

  • I don't believe we've changed anything to do with that for several months. Perhaps a browser update affected it.

  • I don't see much that we can do here: the APK signing tool is the official one by Google, we didn't make it, and the build server just runs that. If you use a third-party tool, we can't support that - any issues will need to be taken up with the respective developer. (As with addons, this is another reason why you should choose third-party tools carefully and make sure they are actively supported and maintained in case they cause any problems.)

    For general advice on building and signing Android apps, you can refer to Google's official documentation, such as Sign your app. You can also export Android Studio projects from Construct and continue to do building and signing with Android Studio, which Google's official guides also cover.

  • Thanks! We've worked hard to make a wide range of major performance improvements in the new C3 runtime. Some (fairly old now) blog posts with more details and benchmarks include Announcing the Construct 3 runtime, Compiling expressions to JavaScript, Optimising events with function binding and Construct 3's new redesigned functions.

  • You do not have permission to view this post

  • Reports like this occasionally come up, they seem to be device-specific, and they have remained a mystery for some time.

    The best approach would be to report the problem to Google at crbug.com, mentioning that it is smooth in the browser but stutters in the APK, and include the device model and specs.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • I did a signed release build in Construct and ran the following command on it:

    .\apksigner.bat verify --verbose .\test-signed.apk

    It produced the following output:

    Verifies

    Verified using v1 scheme (JAR signing): true

    Verified using v2 scheme (APK Signature Scheme v2): true

    Verified using v3 scheme (APK Signature Scheme v3): false

    Verified using v4 scheme (APK Signature Scheme v4): false

    Verified for SourceStamp: false

    Number of signers: 1

    The line "Verified using v2 scheme (APK Signature Scheme v2): true" appears to indicate the APK is already signed with the APK Signature Scheme v2.

    So I don't know why the Play Store would show an error. Perhaps if you are using your own key it is that key which does not support the v2 scheme? It seems to be valid if you use Construct to both create the key and sign with it. The build server uses apksigner, which is the official Android build tool for signing APKs, and according to the documentation, it appears to automatically detect the signing schemes to use, and according to my test it appears to indeed be correctly adding the v2 scheme. Maybe you could run a similar apksigner command to identify the schemes being added to your own APKs.

    If I speculate, perhaps the v2 scheme can only be added if you use the same password for the keystore and the key - after all, the official keytool program no longer supports different passwords (hence the headache about having separate passwords last year), so maybe the v2 scheme doesn't support different passwords either. 🤷‍♂️

  • 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.