A single extension can be used in numerous ways so what everyone wants for them particularly can’t be demonstrated by extension developer.
Instead the developer can provide some standard examples and users will have to adapt them according to their need.
Although what you are looking for is PurchaseSuccessful event.
Hello. Does this extension still work to be used in Kodular? How long could it last if I purchased it today, until a new update is required? Does the purchase include future updates? Thank you
Hello, I am using the InAppBiling extension.my blocks are as I show in the picture, but I get the error in the 2nd picture.the extension is active in google play “closed test” suanda.I did not find any error, what is the problem?
After creating the product, I updated the app in the Play Store.
Hello, I am using the InAppBiling extension.my blocks are as I show in the picture, but I get the error in the 2nd picture.the extension is active in google play “closed test” suanda.I did not find any error, what is the problem?
After creating the product, I updated the app in the Play Store.
Hi, what are the play console settings to make the extension communicate with the products in the app in play console?
Is it necessary to have internal or closed tests?
Does the inserted bundle need to be reviewed?
In short, what are the conditions to ensure that the extensions communicate correctly with the Play Console?
I hope I wasn’t too generic, but I can’t get the product IDs recovered from play console. Furthermore, the apk generates an error when opening the app (which does not happen with companion)
This extension works fine. I had troubles before with other Billing extension, some kind of conflicts with Firebase or Admob extension, but not this one. Thanks so much @iamwsumit, some donation will be done!
I have integrated this extension into a client’s project, and their app is live on the Play Store. However, there’s an issue when users select the option “Ask someone to pay”—the payment is automatically marked as successful without actual completion.
It might be an SDK bug or some implementation issue. For now, I suggest validating the purchase and purchaseToken variables in the PurchaseSuccessful event to ensure that the user has paid.