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

AndroidIn App-PurchaseIn App-Billing

Android Problem Overview


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?

Android Solutions


Solution 1 - Android

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

Solution 2 - Android

I know this is a year old, but none of the answers/tips presented helped me so I thought I would add my solution.

First, I was experiencing the same issue. Namely, made a test purchase, cancelled it, still received a purchase state indicating valid purchase.

What I forgot was that I recently switched the 'License Test Response' field on the settings pane of the Google Play Developer Console from 'RESPOND_NORMALLY' to 'LICENSED'

After switching it back to 'RESPOND_NORMALLY', the purchase state of the cancelled purchase was correctly returned as such.

So, you might want to check that before you try waiting for days

Solution 3 - Android

Step 1. Wait approximately 10 minutes; Until you see the "cancelled order" was delivered. in your google wallet.

> Sep 15 11:28 AM Cancelled The order was delivered. > > Sep 15 11:18 AM Cancelled You cancelled this order. Reason: Customer request to cancel.

Step 2. Logout your test google account on the device and then re-login.

At least that solved my problem.

Solution 4 - Android

This problem also occures when using the app on another device with the same account. The item is not received as purchased until the device is restarted, even after hours. If trying to purchase again, the google wallet dialog says "item already owned". The return code from the iabHelper still is "user cancelled" cause the real response from the purchase activity is not given back, just written in the debug log.

else if (resultCode == Activity.RESULT_CANCELED) {
        logDebug("Purchase canceled - Response: " + getResponseDesc(responseCode));
        result = new IabResult(IABHELPER_USER_CANCELLED, "User canceled.");
        if (mPurchaseListener != null) mPurchaseListener.onIabPurchaseFinished(result, null);
    }

So its not possible to react to this google billing dialog cause we are always getting the same result IABHELPER_USER_CANCELED, even if the dialog said "item already owned".

Edit:

I fix it with this:

else if (resultCode == Activity.RESULT_CANCELED) {
        logDebug("Purchase canceled - Response: " + getResponseDesc(responseCode));
        if(responseCode == 7) 
            result = new IabResult(BILLING_RESPONSE_RESULT_ITEM_ALREADY_OWNED, "Item already owned.");
        else                                                                                             
            result = new IabResult(IABHELPER_USER_CANCELLED, "User canceled.");
        if (mPurchaseListener != null) mPurchaseListener.onIabPurchaseFinished(result, null);
    }

So now if the response from the billing dialog is 7 as "Item already owned" i report it back to my listener.

Solution 5 - Android

What you can use is the autoRenewing field of the purchase data. According to the documentation:

> autoRenewing: Indicates whether the subscription renews automatically. If true, the subscription is active, and will automatically renew on the next billing date. If false, indicates that the user has canceled the subscription.

And this field get updated immediately after the cancellation.

Solution 6 - Android

if I see correctly the reference code in the trivialdrivesample is wrong, which would be a shame for the official reference project for in app billing.

if purchase == null it just means it has never been purchased. To get the real information you have to call

purchase.getPurchaseState()

according to here

purchaseState The purchase state of the order. Possible values are 0 (purchased), 1 (canceled), 2 (refunded), or 3 (expired, for subscription purchases only).

Solution 7 - Android

It’s already well answered in the Google official docs. Copying the words here. >When the user cancels a subscription, Google Play does not offer a refund for the current billing cycle. Instead, it allows the user to have access to the cancelled subscription until the end of the current billing cycle, at which time it terminates the subscription. For example, if a user purchases a monthly subscription and cancels it on the 15th day of the cycle, Google Play will consider the subscription valid until the end of the 30th day (or other day, depending on the month).

That should explain it all. getPurchase() will still return the purchase data till the end of the current subscription cycle.

Solution 8 - Android

I found the following section in the documentation (IAB API v2), but I am not sure if this can be used for IAB API v3. The broadcast might still be sent though.

>"... your application can receive an IN_APP_NOTIFY broadcast intent when Google Play receives a refund notification from Google Wallet. In this case, Google Play sends an IN_APP_NOTIFY message to your application. Your application can handle this message the same way it handles responses from an application-initiated REQUEST_PURCHASE message so that ultimately your application receives a PURCHASE_STATE_CHANGED message that includes information about the item that has been refunded. The refund information is included in the JSON string that accompanies the PURCHASE_STATE_CHANGED broadcast intent. Also, the purchaseState field in the JSON string is set to 2."

from: http://developer.android.com/google/play/billing/v2/api.html#billing-action-notify

Solution 9 - Android

I noticed the exact same thing:

Making an in-app purchase with a test account -> refunding the purchase with removing access -> getPurchaseState still returns Purchased (even after relogin and restart) and thus the access to the premium features is not removed in my app.

But when I tested the same thing with a real purchase:

Customer made a real purchase -> a couple of weeks later I refunded it -> Customer did not have access to the premium features of my app anymore.

So could it be, that this is only a problem for test purchases?

Solution 10 - Android

As of 2022 March 06, Billing Client version 4 API, you might still need to wait a few hours after cancellation until a purchased item is cancelled in Google Play.

Sometimes I saw cleaning the project also helps (In Android Studio: Build menu > Clear project)

However, in case of subscriptions you can also check and adjust the "Grace period" for your product in Google Play Console: enter image description here

Attributions

All content for this solution is sourced from the original question on Stackoverflow.

The content on this page is licensed under the Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) license.

Content TypeOriginal AuthorOriginal Content on Stackoverflow
QuestionToni KanoniView Question on Stackoverflow
Solution 1 - Androidlalit_samView Answer on Stackoverflow
Solution 2 - AndroidJannonView Answer on Stackoverflow
Solution 3 - AndroidpinuxView Answer on Stackoverflow
Solution 4 - AndroidKeduView Answer on Stackoverflow
Solution 5 - AndroidElyess AboudaView Answer on Stackoverflow
Solution 6 - AndroidtmantheyView Answer on Stackoverflow
Solution 7 - Androiduser1938357View Answer on Stackoverflow
Solution 8 - AndroidmvandillenView Answer on Stackoverflow
Solution 9 - AndroidNickreyView Answer on Stackoverflow
Solution 10 - AndroidZP007View Answer on Stackoverflow