Android In-App Billing: Purchase state stays “purchased” after order cancelation

Question

I'm currently testing my InApp billing mechanism (using the InApp Billing version 3 API, therefore taking the TrivialDrive example as reference).

I have one managed item, which is upgrade to premium version.

Now, purchasing the item with my test account works, but when I do a cancellation of the entire order in Google checkout afterwards, my code still tells me that the item is purchased an therefore grants the premium features.

Here is how I check for the purchase in my MainActivity. I do not save the purchase state locally somewhere, as I understood that the with the billing API v3, you can query for purchases ad hoc as needed.

@Override
    protected void onStart() {
        // TODO Auto-generated method stub
        super.onStart();

        iabHelper = new IabHelper(this, Helper.getPKey());
        iabHelper.enableDebugLogging(true);

        iabHelper.startSetup(new IabHelper.OnIabSetupFinishedListener() {

            @Override
            public void onIabSetupFinished(IabResult result) {
                Log.d("IAB", "SETUP FINISHED");

                if(!result.isSuccess())
                {
                    Log.d("IAB", "SETUP NOT OK");
                    return;
                }
                else
                    Log.d("IAB", "SETUP OK");

                iabHelper.queryInventoryAsync(
                    new QueryInventoryFinishedListener() {

                        @Override
                        public void onQueryInventoryFinished(IabResult result, Inventory inv) {
                            Log.d("IAB", "Query inventory finished.");
                            if (result.isFailure()) {
                                Log.d("IAB","Failed to query inventory: " + result);
                                return;
                            }

                            Log.d("IAB", "Query inventory was successful.");

                            // Do we have the premium upgrade?
                            boolean mIsPremium = inv.hasPurchase(Helper.premiumSku);
                            Purchase p = inv.getPurchase(Helper.premiumSku);
                            if(p != null)
                                Log.d("IAB PURCHASE STATE", IabHelper.getResponseDesc(p.getPurchaseState()));
                            else
                                Log.d("IAB PURCHASE STATE", "Purchase is null");

                            Log.d("IAB", "User is " + (mIsPremium ? "PREMIUM" : "NOT PREMIUM"));


                        }
                    }                       

                );              
            }
        });       
    }

I keep getting getPurchaseState = 0, which means is Purchased, even one hour after I cancelled the order. Why?

I don't have the answer but can confirm I am also seeing this problem. 1. do purchase 2. go into google checkout and cancel order 3. observe email is sent confirming order cancelled 4. subsequent requests give PurchasedState = 0 (ie purchased) Perhaps it takes a while for the changes to filter through? Also see the following discussion in the comments section of this page, someone else reports the same problem. plus.google.com/u/1/+AndroidDevelopers/posts/R8DKwZDsz5m — Steve
I see a similar issue. I use IAP v3 API and I buy an item and I cancel the order in google checkout. But when I try to buy it again, IAP v3 returns "7:Item Already Owned". I'm using the trivialdrive sample also. The inventory shows the purchasestate as "0" for the item and the purchasedate as 1358439773 is 01/17/2013 4:22pm GMT. which is exactly the date and time that google checkout shows as the cancellation date. — Ralph Yozzo
This is tangential to your question, but I just wanted to point out that using IabHelper.getResponseDesc(p.getPurchaseState()) to obtain a description of the purchase state is not appropriate, since getResponseDesc() is for retrieving a description of a response code, rather than a description of a purchase state indicator. For the latter, per developer.android.com/google/play/billing/…, "Possible values are 0 (purchased), 1 (canceled), or 2 (refunded)." These constants don't seem to have been defined or even used in the original TrivialDrive sample code. — Carl
@Toni: I have now tested canceling an order with a modified version of the TrivialDrive sample app and had the same problem. I went into Checkout and canceled the order that I had placed from my own test account (not the developer account) and fifteen hours later the app still reported a purchase type of 0 (Purchased). This is on Nexus 7 with Google Play Store version 3.10.10. After this, I cleared the Google Play app's cache, stopped the TrivialDrive app and started it again. Still no change. Then, installed TrivialDrive for the first time ever on my Nexus One phone; still purchased. — Carl
OK, the answer is that it can take up to 72 hours. See this other SO page's accepted answer: stackoverflow.com/questions/13861625/… — Carl

lalit_sam lalit_sam · Accepted Answer · 2015-10-27T02:36:34

After having waited for about 12 hours and having tried everything suggested here, I was still facing the same issue. What did the trick for me was the following adb command:

adb shell pm clear com.android.vending

Android In-App Billing: Purchase state stays “purchased” after order cancelation

9 Answers