You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+12-3Lines changed: 12 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,4 +1,4 @@
1
-
# Google In-App Billing Library v7+ [](https://android-arsenal.com/api?level=21)[](https://jitci.com/gh/moisoni97/google-inapp-billing)[](https://jitpack.io/#moisoni97/google-inapp-billing)
1
+
# Google In-App Billing Library v8+ [](https://android-arsenal.com/api?level=21)[](https://jitci.com/gh/moisoni97/google-inapp-billing)[](https://jitpack.io/#moisoni97/google-inapp-billing)
2
2
A simple implementation of the Android In-App Billing API.
3
3
4
4
It supports: in-app purchases (both consumable and non-consumable) and subscriptions with a base plan or multiple offers.
@@ -24,7 +24,7 @@ It is recommended to implement the `BillingConnector` instance in your MainActiv
24
24
25
25
This is necessary because sometimes (due to different reasons) the purchase is not instantly processed and will have a `PENDING` state. All `PENDING` state purchases cannot be `acknowledged` or `consumed` and **will be refunded** by Google after 3 days.
26
26
27
-
The library automatically handles acknowledgement and consumption, but for that, it needs the `BillingConnector` reference. It cannot happen in a background service. So if the `BillingConnector` is set in a remote activity that the user **rarely interacts with (or not at all)**, it will never receive the `Billing API callback` to acknowledge the new updated purchase status and the user will lose the purchase.
27
+
The library automatically handles acknowledgement and consumption, but for that, it needs the `BillingConnector` reference. It cannot happen in a background service. So if the `BillingConnector` is set in a remote activity that the user **rarely interacts with (or not at all)**, it will never be instantiated to receive the `Billing API callback` to acknowledge the new updated purchase status and the user will lose the purchase.
28
28
29
29
The library provides `ACKNOWLEDGE_WARNING` and `CONSUME_WARNING` error callbacks to let you know that the purchase status is still `PENDING`. Here you can inform the user to wait or to come back a little bit later to receive the purchase.
0 commit comments