From 6d82966ebe3c4437d7e78284d7ef9b78ee86505f Mon Sep 17 00:00:00 2001 From: Adrien Fery Date: Fri, 2 Mar 2018 14:25:37 +0100 Subject: [PATCH] Update inAppPurchase API doc (#12072) * Update inAppPurchase API doc `addTransactionsListener` is no longer supported. Users have to listen for the `transactions-updated` event instead. * Tweak `transactions-updated` timing description Make the documentation edit suggested by @felixrieseberg and thumbs-upped by @AdrienFery --- docs/api/in-app-purchase.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/docs/api/in-app-purchase.md b/docs/api/in-app-purchase.md index 970464158565..0757bfd5cba7 100644 --- a/docs/api/in-app-purchase.md +++ b/docs/api/in-app-purchase.md @@ -25,8 +25,10 @@ The `inAppPurchase` module has the following methods: * `productID` String - The id of the product to purchase. (the id of `com.example.app.product1` is `product1`). * `quantity` Integer (optional) - The number of items the user wants to purchase. -* `callback` Function (optional) - The callback called when the payment is added to the PaymentQueue. (You should add a listener with `inAppPurchase.addTransactionsListener` to get the transaction status). - * `isProductValid` Boolean - Determine if the product is valid and added to the payment queue. +* `callback` Function (optional) - The callback called when the payment is added to the PaymentQueue. +* `isProductValid` Boolean - Determine if the product is valid and added to the payment queue. + +You should listen for the `transactions-updated` event as soon as possible and certainly before you call `purchaseProduct`. ### `inAppPurchase.canMakePayments()`