Posts by Olivier

Glad you sorted it out. And thanks for confirming that by using the In-App Android extension alone one must also declare "something". Of course, that something depends on what you do with user data in your app.

I've answered to you in this Please login to see this link..

I strongly believe that this is a new requirement from Google. Could you please confirm that you're not using the Google Play Games (GPG) suite of extensions in your app? If that's the case, then maybe this new requirement also applies to apps using the In-App Android extension. Though I couldn't find any official information about this.

This is likely not caused by the Android runtime or extensions. If you are using the Google Play Games suite of extensions, it seems that from now on you must disclose data collection/sharing in your app's Data safety form. The exact disclosure requirements for your app depends on what you do with the data. More info about this here: Please login to see this link.

I would say that if you simply submit scores and/or update achievements, you'd only need to disclose this in your app's Data safety form: Device Or Other IDs shared for app functionality.

Quote from Tiny

Unfortunately Google did not accept my update made with the patch due to the Play billing . Have no idea how to fix this.
This is their message:

"This app targets Android 14 or above and your current Play Billing Library version doesn't support Android 14. To target the latest Android version, please update your PBL version to either 5.2.1 or 6.0.1 and above."

Sorry for the delay, we've just released a patch to address this issue: Please login to see this link.

Sorry for the delay, we've just posted a patch here to address this issue: Please login to see this link.

Here is a patch for both the standalone and Steam versions of the Android runtime. This is a hotfix that addresses two important issues that you may encounter in the Google Play Console, the outdated Google Play Billing Library version and the Play Core Maven dependency.

Standalone: Please login to see this link.

Steam:
1. Open the Fusion settings in the Steam client
2. Select the Betas tab
3. Enter the following password: xyz555pbx444 and click the "Participate to the "androidinapp295update - Build 295 Android Play Billing Update" tests"

Please check the following release notes:

Quote

Changes in InApp Billing v6
---------------------------

Google migrated the in-app library from 5.x to 6.x, this new version required some changes in the events, see the help file (still in progress, not reviewed yet).

Old commands have been clarified and regrouped, and new ones have been added.

We recommend reviewing your implementation so that you make changes if necessary.

Note: new conditions are added to the conditions to show the pending status of subscriptions and products in case the user pays in cash.

We have implemented new actions to manage subscriptions as required by Google and its new version 6.1.0.

We suggest you to visit and read Please login to see this link. for more detailed information on these actions.

In addition, there are new actions to manage notifications to your users when they purchase and when their purchase is pending.

There are also new expressions for values offered by the new library.

New properties allow you to configure purchases, which will be recognized automatically or will depend on your code.

Typically, you will need to implement your process of validating and converting the purchase to items in your request and perform this acknowledgment at the end.
Please note that if you do not do so, your purchase will be reversed in approximately 72 hours.

A property is also added to select whether to inform the user that a purchase received an update from the Google Store and inform them via a message.
This message is important to inform the user that they need to visit the store in your application and with this the conversion to purchased items is carried out.
As a developer, your role is crucial in handling pending purchases, a key feature in the new version.

It is important to include the new conditions in your store programming to effectively manage these new situations.

-------------

Note 1: It is recommended to handle pending purchases, i.e. purchases that are not processed immediately by the user's bank or purchases that are delayed
for example when the user uses cash by a physical store .

Query the purchases and use the expressions "PurchaseState()" and "PurchaseAcknowledged()" to check:
- if a purchase is pending, and if that's the case display a relevant message to the user. For example "Your purchase is pending."
- if a purchase is purchased and not acknowledged, and if that's the case acknowledge it and display a relevant message to the user. For example "Your purchase succeeded."

It is crucial to acknowledge a purchase once it has been processed by Google. Otherwise the purchase will be refunded automatically by Google after 72 hours.
For this reason it is recommended to unlock the content only upon acknowledging a purchase, and not before. You acknowledge a purchase using the new action "AcknowledgeSKU()"

Note 2: new V6 MFA examples are provided in Examples\InAppAndroid.

Display More

We sincerely apologize for the delay in releasing this update.

Quote from Lecherbault

what's wrong?

Please make sure that you use the quick patch that Yves posted earlier in this thread. Then please notice that after having updated your app the warning message won't disappear from the Google Play Console, as stated above by Janette5, simply archive it.

I think it would be wiser to set the minimum Android version to 6.0 instead of 5.0, be it only to benefit from a stronger protection from Google. Moreover, people using Android 5.0 today must be scarce.

Quote from JasonDarby

Can I actually call a different include frame, as I am guessing my UI frame would be the core frame?

It's actually the other way around, sort of. Each "Level" frame via its properties would include the same "Level UI" frame. Here's some more info about this feature, among others:
Please login to see this link.
Please login to see this media element.

Si vos éléments d'interface textuels sont composés d'images, il faudrait les remplacer par des objets "Chaîne de caractères" pour voir si un lecteur d'écran peut les interpréter. Il s'agit d'une suggestion, je n'ai pas testé. Un lecteur d'écran est un procédé logiciel / service d'accessibilité permettant à certains utilisateurs souffrant d'un handicap de pouvoir comprendre l'interface de votre app.

Plus d'info au sujet des libellés de contenu: Please login to see this link.

Please select the build type "Android app bundle" or "Android app bundle with expansion" if you app is bigger than 150 MB.

"Landscape automatic" is working here, with any of the 3 build types for Android. Maybe try updating Fusion if you're not using the latest build.

By compiling your application as an "Android App Bundle with expansion" you end up with a single .AAB file. Simply upload it to the Google Play Console as you would do with a regular .AAB.

The HTML5 Object allows you to call Javascript function.

Clickteam does not take donations. But there is a way to support us financially, become a patron: Please login to see this link.

About calling Javascript functions, the HTML5 Object allows you to do that.

Unfortunately the HTML5 runtime still doesn't support such a feature. Several users asked about it, in this thread among others: Please login to see this link.
The good news is that we are actually working on it, but we can't tell when an update will be available.

Quote from Dobermann

On a toujours pas les icones compatibles Android 8 et supérieur... C'est prévu pour quand ?
Android 8 commence a être bien répandu et nos applis affichent toujours une icone toute naze en mode legacy au lieu de profiter des vraies icones, c'est un vrai handicap côté qualité.

D'après ton image, j'ai l'impression que l'icône de ton app ne répond pas aux nouvelles spécifications de Google introduites le 24 Juin dernier. Pour y remédier il suffit de se rendre dans la Play Console > Fiche Play Store puis de fournir une image et de cocher l'option "qui va bien".
Source: Please login to see this link.

Fusion ne supporte pas les nouvelles icônes adaptatives introduites dans Android 8.0 (API level 26), en tous cas pour le moment.

It appears that there is an issue with the bouncing ball movement. I found out that you can't really set a deceleration of 0, doing this is equivalent to setting a deceleration of 1. It's easily noticeable with the attached example.
This explains why the object stops immediately when you set it at speed 1 and deceleration 0.

The second issue (minor) is that the deceleration expression returns 0 unless you set it by action.

Sorry for the delay, we're all very busy.