- Official Post
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:
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.
We sincerely apologize for the delay in releasing this update.
