Les versions Beta ne sont pas autant testées que les versions Stables

Les versions Beta ne sont pas autant testées que les versions Stables

Branche Beta

Construct 3 r402.2

Hotfix for r402

07 August, 2024 ()

Envoyez-moi un courriel lors de nouvelles parutions

Don't miss out on the latest and greatest new features in Construct 3

Créer un compte

Notes

Beta releases are for testing, and occasionally unexpected issues slip through. A fix for an issue with single-file playable ads in r402 accidentally broke other kinds of exports, so we're releasing a hotfix to correct the issue, particularly as no beta release is scheduled for next week. Single-file playable ads are extremely difficult to support with very tough requirements that make them very hard to develop and maintain, which is part of the reason we've been encouraging to move over to the zip format for playable ads - if the single-file mode proves too difficult to support in the long-term then we may have to retire it. So as we've said before, if you rely on this mode, please contact your ad provider and ask them to support the zip format if they don't already, as that is easy to support long-term, and will mean you can continue using playable ads if the single-file mode is retired.

In case you missed it, see the r402 release notes here.

Please note: due to staff time off, there will be no beta release next week (August 12-16). The next beta release will be the following week (August 19-23).

Vous aimez cette parution ?

Faites-le nous savoir avec un pouce haut !

21
Exécuter r402.2

Corrections de bug

4 favoris
Exports not working (regression r402)

Partager Construct 3 la parution r402.2 maintenant

  • 9 Comments

  • Order by
Want to leave a comment? Login or Register an account!

  • Ad Networks already support zip format. However they want a zipped single file or a HTML file and a .js file. Majority do not support multi file zips.

    The industry standard is single fill w/ Data URI base 64 for images. Regardless of how old or inefficient this may seem -it's how it's done. Calling the ad networks to support ZIP is as useful as asking facebook to fix their playable testing tool that's been busted since release.

    At the moment I can deploy on just about every ad network aside from facebook. Kinda sad you are willing to let single file go to wayside. I understand if it's affecting core product... just not what some of us want to hear.

    Currently I use r379 stable (upto r381) for playable development as it seems to be the most compatible release for playable dev.

    Are you going to continue to host the older releases of C3 so we can continue to develop playables with C3 OR should we begin to think about alternatives?

      • [-] [+]
      • 1
      • Ashley's avatar
      • Ashley
      • Construct Team Founder
      • 1 points
      • (5 children)

      A single file with base64 encoded images is actually an unusual format and as far as I'm aware not needed anywhere else in the industry outside of ads. Every single other platform uses separate asset files, including some ad platforms that now accept zips. It's unclear why this single-file format is even needed - why can't they just have normal separate asset files? By the zip format I mean a zip of web assets, with separate HTML, CSS, JS and image files. This is the only format it's easy for us to support, and if supporting an unusual format with extreme restrictions ends up causing major problems or otherwise holding back improvements to Construct for all customers, that would be untenable and so we'd rather drop support for the single file format in that case. We are doing our best to forewarn people of a possible outcome, so people can advise the ad networks of the change they want, and any ad networks that can be upgraded to support a much better format can do so ahead of time.

    • "Single-file playable ads are extremely difficult to support with very tough requirements that make them very hard to develop and maintain"

      "sad you are willing to let single file go"

      I mean, not their fault, obviously

  • from google play console:

    The Play Console advertising ID statement indicates that your app uses an advertising ID. A manifest file in one of your active artifacts does not include the com.google.android.gms.permission.AD_ID permission.

    If you do not include this permission in the manifest file, the advertising identifier will be converted to a string of zeros. This can cause advertising and analytics use cases to stop working, resulting in lost revenue. More information