Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[TrivialDriveKotlin] What is the recommended logic to handle: Purchase.PurchaseState.PENDING #411

Open
antranvn opened this issue Jan 5, 2021 · 1 comment

Comments

@antranvn
Copy link

antranvn commented Jan 5, 2021

In function processPurchases, we have Purchase.PurchaseState.PENDING case.
What is the recommended logic to handle: Purchase.PurchaseState.PENDING

@DAGalpin
Copy link
Contributor

DAGalpin commented May 3, 2021

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants