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
The sample now handles pending. It's only enabled if you enable it in the billing library. The only logic needed is to not deliver the entitlement until the purchase switches to the purchased state, and to listen for the state change. In the sample, I allow the user to re-enter the purchase flow so they can see that they have a purchase pending. That being said, you may wish to remind the user that they have a pending purchase in your UI, and the pending state is exposed to the UI for that reason.
In function processPurchases, we have Purchase.PurchaseState.PENDING case.
What is the recommended logic to handle: Purchase.PurchaseState.PENDING
The text was updated successfully, but these errors were encountered: