Ashley's Recent Forum Activity

  • There shouldn't be any need to use old releases - the 'Open local project folder' option in the Chrome browser should be able to open any project folder saved with any prior version of Construct (desktop or browser).

    The project is probably corrupt. You may be able to see a more detailed error message if you press F12 and check the browser console. Beyond that it would be hard to help any further without a copy of the project.

  • We didn't remove it. I just checked and it's still there.

    It's only shown if the browser supports it, which is currently only Chromium-based browsers (Chrome, Edge, Opera...)

  • You do not have permission to view this post

  • As of r234, new projects default to using JavaScript Modules, which handle globals slightly differently. See Upgrading projects from classic scripts to modules.

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

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

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

  • 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. 🤷‍♂️

Ashley's avatar

Ashley

Early Adopter

Member since 21 May, 2007

Twitter
Ashley has 1,768,339 followers

Connect with Ashley

Trophy Case

  • Jupiter Mission Supports Gordon's mission to Jupiter
  • Forum Contributor Made 100 posts in the forums
  • Forum Patron Made 500 posts in the forums
  • Forum Hero Made 1,000 posts in the forums
  • Forum Wizard Made 5,000 posts in the forums
  • Forum Unicorn Made 10,000 posts in the forums
  • Forum Mega Brain Made 20,000 posts in the forums
  • x125
    Coach One of your tutorials has over 1,000 readers
  • x74
    Educator One of your tutorials has over 10,000 readers
  • x5
    Teacher One of your tutorials has over 100,000 readers
  • Sensei One of your tutorials has over 1,000,000 readers
  • Regular Visitor Visited Construct.net 7 days in a row
  • Steady Visitor Visited Construct.net 30 days in a row
  • RTFM Read the fabulous manual
  • x42
    Great Comment One of your comments gets 3 upvotes
  • Email Verified

Progress

32/44
How to earn trophies

Blogs