Problem with in app purchasing on Google play

DanielKotzer

You say this line shows I got a back a response from the server:
PlayBillingController::onPurchasesUpdated( 0, [] )

but maybe the array is empty?

ma

The 0 is the response code which is "OK" and means the purchases were updated.

There are 3 possible scenarios from that response:

If there were no purchases in the response you will receive a PURCHASE_FAILED event
If there are purchases but they fail validation (i.e. either they are faked or your billing key is wrong) you will receive a PURCHASE_FAILED event
If there are valid purchases you will receive the PURCHASES_UPDATED event

DanielKotzer

ma you should receive a PURCHASES_UPDATED in any case, this is how the new District in app billing ane is working, and even if you got a purchase failed event, I have a handler to deal with it in my code, and I would see a message if such an event was received, now I don't see anything.

FliplineStudios

@DanielKotzer Just a couple things I've noticed in your class is that the purchases_updatedHandler (as well as some of the other handlers) aren't declared as private or public, and are just standalone functions -- not sure if that might be impacting things with handling the purchases correctly. Also, somewhat unrelated, but I believe you should be calling finishPurchase for everything except STATE_PURCHASING and STATE_DEFERRED, and some of your cases near the bottom (FAILED, REFUNDED, RESTORED, REMOVED, CANCELLED) are missing the finishPurchase call. Might be worth a try to update those and set the handlers to be private methods to see if that makes a difference.

DanielKotzer

FliplineStudios You do a finishpurchase only for a good purchase, not for a failed one, the user might want to pay you directly, so you should say when the purchase is final or else it is canceled after 3 days. the missing of the private declaration can't be the problem, remember this code is working fine on another product I have.

FliplineStudios

DanielKotzer The docs do mention that you need to call finishPurchase on anything that's not "PURCHASING" or "DEFERRED". Finishing doesn't necessarily mean it was a successful purchase, just that your app has done whatever it needed to do with that attempted purchase, whether there was an error, or cancelled, or not allowed, or successful (your own purchase_failedHandler also finishes failed purchases):

// For all other states you should handle appropriately and call finish purchase 
            case Purchase.STATE_FAILED:
            case Purchase.STATE_REFUNDED:
            case Purchase.STATE_RESTORED:
            case Purchase.STATE_REMOVED:
            case Purchase.STATE_CANCELLED:
            case Purchase.STATE_NOTALLOWED:
                InAppBilling.service.finishPurchase( purchase );
                break;

As a rule it is important that you call finishPurchase() when you have completed the purchase and either handled the error or deployed the product to the user's inventory.

Not really sure what else the problem could be, I was just pointing out parts of your Class that didn't fully match how the docs and example files are set up, in case those might be problem areas. Very strange that the same code works in another app but not this one, do they both have the same up-to-date ANEs and same manifest additions in the application XML?

DanielKotzer

I tried to send a message when the PurchaseEvent.PURCHASES_UPDATED happens with the number of items in the event.data.length, but nothing happens, this event is simply not happening, the server seems to sent it though:

09-02 23:17:15.897 8663 8663 I com.distriqt.InAppBilling: InAppBillingContext::onActivityStateChanged( PAUSED ) android.intent.action.MAIN 09-02 23:17:29.386 8663 8663 I com.distriqt.InAppBilling: InAppBillingContext::onActivityStateChanged( RESUMED ) android.intent.action.MAIN **09-02 23:17:29.452 8663 8663 I com.distriqt.InAppBilling: PlayBillingController::onPurchasesUpdated( 0, [] )** 09-02 23:17:29.457 8663 8663 I com.distriqt.InAppBilling: PlayBillingUtils::encodeReceipt( com.jewishsoftware.mastermishna.sheviit ) 09-02 23:17:51.670 8663 8663 I com.distriqt.InAppBilling: InAppBillingContext::onActivityStateChanged( PAUSED ) android.intent.action.MAIN 09-02 23:17:51.854 8663 8663 I com.distriqt.InAppBilling: InAppBillingContext::onActivityStateChanged( STOPPED ) android.intent.action.MAIN

So I do get the available products and their prices from the server properly, I do get an event when I do restore purchases, but no purchases are restored because no purchase was ever successful, also I don't know if this message is coming from the product update event or from the InAppBillingEvent.RESTORE_PURCHASES_SUCCESS event. But there seems to be a communication with the server.

What am I supposed to do next?

FliplineStudios

DanielKotzer So I do get the available products and their prices from the server properly, I do get an event when I do restore purchases, but no purchases are restored because no purchase was ever successful, also I don't know if this message is coming from the product update event or from the InAppBillingEvent.RESTORE_PURCHASES_SUCCESS event. But there seems to be a communication with the server.

If you're getting other events successfully from the server (available products and prices), that would lead me to believe there's something wrong with your listener for the PURCHASES_UPDATED event, either it's having an issue accessing the handler, or there's some error in your code in the handler causing the whole for-each loop to fail. I'd maybe try just commenting out your whole purchases_updatedHandler and creating a new one just to test that it's able to receive communication at all:

private function purchases_updatedHandler( event:PurchaseEvent ):void {
      trace("Update Handler Working");
 }

Then if you're seeing the trace, you know it's communicating with the server correctly and there's just something in your code that's hanging things up, and slowly work towards rebuilding each case in your handler.

DanielKotzer

Maybe there is another ANE that works on Flash Builder 4.7 and supports billing library version 3? if they both will have the same problem something has to be wrong on the server side...
Maybe I need an ANE that supports billing library version 4? maybe this has become a requirement lately? Some times things like that happen on google plays server, it is not consistent sometimes...

DanielKotzer

FliplineStudios The docs do mention that you need to call finishPurchase on anything that's not "PURCHASING" or "DEFERRED". Finishing doesn't necessarily mean it was a successful purchase

thank you for this information, I'll fix it.

DanielKotzer

FliplineStudios Then if you're seeing the trace,

How do I see the trace? using the command line you showed me:
D:\FlashBuilder\new_33.1.1.554\lib\android\bin>adb logcat com.distriqt.InAppBilling:V *:S

ma

It could also be important to check where and how you are attaching the listener and that the InAppAndroid class you are using isn't getting garbage collected or something along those lines?

FliplineStudios

DanielKotzer If you're using remote debugging with a debug build you should be able to see your trace statements, or if you're not using a debugger you can instead use adb logcat while testing on your device, though you'd need a somewhat different command:

https://help.adobe.com/en_US/air/build/WSfffb011ac560372f-5d0f4f25128cc9cd0cb-7ff8.html

Make sure you've published the SWF with debugging enabled (and I believe you need to use "apk-debug" as the target for publishing the APK as well?), and then you can use your app's application ID with logcat. In this example it will show your app's trace statements, and also the InAppBilling logging, but will silence everything else:

adb logcat air.com.your.app.here:V com.distriqt.InAppBilling:V *:S

And just to clarify, with this debugging/tracing test this would be for a separate debug build that you're making and installing directly on your device with adb, not a build that you'd be uploading to Google Play (once they've reviewed a build in the alpha track, you should be able to access any of the in-app purchase SKUs from local test builds and don't have to keep uploading, though they can take a day or so before they're available in your app)

DanielKotzer

I did find out a problem that could make a difference between the 2 products, I'm testing it but when I upload an Alpha build for closed test on Google play it takes them a week to review this build, so it is very slowly.
The difference I found is that one app has a list of in app products it asks for with:
InAppBilling.service.getProducts( productIdList);
and all these products were created by me, and are ready for sale,
While the other product that is not working, has a list of 62 products and only about 20 where made.
This wasn't a problem before I was using the district ANE, because if I was asking for a product that didn't exist it wasn't sending anything back but now you get an error message which might interrupt the purchasing process.
And another thing I found out is that I do get one item in return:

function purchases_updatedHandler( event : PurchaseEvent ):void { SendErrorMsg("NUMBER OF ITEMS:#"+event.data.length);...

this gives me 1, but for some reason it is not activating anything in the switch case code, so I did something else to see what are the details of this item I'm getting in return:
`function purchases_updatedHandler( event😛urchaseEvent ):void
{
//SendErrorMsg("NUMBER OF ITEMS:#"+event.data.length);

		for each (var purchase:Purchase in event.data)
		{
			var massege:String = "";
			massege += "\nProduct ID: "+purchase.productId;
			massege += "\nTransaction Date: "+purchase.transactionDate;
			massege += "\nError: "+purchase.error;
			massege += "\nError Code: "+purchase.errorCode;
			massege += "\nTransaction Id: "+purchase.transactionId;
			massege += "\nTransaction State: "+purchase.transactionState;
			
			SendErrorMsg("ITEM INFO:#"+massege);
			
			switch (purchase.transactionState)
			{
				// These transactions are in progress, so don't finish them unless you don't want them to complete
				case Purchase.STATE_PURCHASING:
					SendErrorMsg("PURCHASING!#"+massege);
					break;...`

Though now I have to wait a week for Google Play team to review this Alpha build and make it available, so I can test it and see what I'm getting.

DanielKotzer

Issue was resolved.
this function had a problem:
addPurchaseToInventory( purchase );
it was using a global function that existed in one app, but not on the other and it was causing the code to stop running, fixed it and everything is OK.
What can I do, that is programing, sometimes a small mistake can cause a lot of trouble...
Thank you for your time.

Interestingly, after I opened my device for debugging, it was running the billing process even on a version I was running on an Android device connected to my Desktop while FB was running. I don't know if this is because I had an Alpha testing build uploaded with the same version number, but it did run the billing process just without charging my credit card, jus by clicking on the Buy now button, I was receiving an update purchase event. So in the end I've learned many new things on who to debug the billing process. Thank you very much for the help.

FliplineStudios

That's great to hear, glad you got it figured out!