Android InApp Purchases and Public Key

Radiesel · December 2012

Hi folks,

I successfully implemented InApp purchases for Android. What a stupid thing compared with iOS. I can share my experiences and problems if somebody has a needs for it.

However, I still have a question regarding GoogleBilling:setPublicKey(publicKey). I read several Pages on google, but wasn't able to fully understand the need of this function. Can anyone explain? InApp purchases still work without calling this function.

thanks in advance!
Michael

mefisto · December 2012

Hi @Radiesel .Even at google search result there is nothing directly related to setPublicKey method

and google suggest that "Did you mean: Google Billing getPublicKey ". Are you sure that getPublicKey is not absolute or not implemented.

ar2rsawseen · December 2012

@Radiesel I think many on forum would want to see a step by step tutorials and prerequisites.

gorkem · December 2012

@radiesel yes yes yes! Please share your findings with the community <:-P

atilim · December 2012

You can find some information about public key here: http://developer.android.com/google/play/billing/v2/billing_integrate.html

> What a stupid thing compared with iOS.
Exactly

I've read these pages https://developer.android.com/google/play/billing/index.html again and again to grasp the logic behind. And probably now I've forgotten everything.

hgvyas123 · December 2012

+1 for share

atilim · December 2012

oh yes +1 for share

mertocan · December 2012

Actually i didnt use many functions from google billing page but it still works.

http://www.giderosmobile.com/forum/discussion/2229/android-in-app-usage-on-gideros#Item_1

Radiesel · December 2012

Thanks! I will soon share my experience. Code part is really small (thanks to a fantastic SDK..), I basically only use requestPurchase() - most problems came from google itself...

Hope I can put it together...

best regards
Michael

atilim · December 2012

@mertocan, @Radiesel - you should call confirmNotification after receiving Event.PURCHASE_STATE_CHANGE event (just pass event.notificationId to confirmNotification function) This is the only trick you should be careful about.

btw, I realized that the reference manual isn't really enough to implement google billing inside your applications

Radiesel · December 2012

@Atilim, this is what for? After I call requestPurchase() I am only testing for GoogleBilling.OK. Either billing worked, or not... I am not testing for PURCHASE_STATE_CHANGED. Well, might be too simple... However, seems to work for me...

atilim · December 2012

From http://developer.android.com/google/play/billing/v2/api.html

CONFIRM_NOTIFICATIONS
This request acknowledges that your application received the details of a purchase state change. Google Play sends purchase state change notifications to your application until you confirm that you received them.

and

Keep in mind, you must send a confirmation when you receive transaction information from Google Play (step 8 in figure 2). If you don't send a confirmation message, Google Play will continue sending IN_APP_NOTIFY messages for the transactions you have not confirmed. As a best practice, you should not send a CONFIRM_NOTIFICATIONS request for a purchased item until you have delivered the item to the user. This way, if your application crashes or something else prevents your application from delivering the product, your application will still receive an IN_APP_NOTIFY broadcast intent from Google Play indicating that you need to deliver the product.

It's very similar to the StoreKit:finishTransaction function.

Radiesel · December 2012

got it, thanks! Will modify my code. Just realized, that I was implementing more or less the same as mertocan...

atilim · December 2012

It's correct. You just need to add one line of confirmNotification and that's all. Basically your listener function should be like:

local function onPurchaseStateChange(event)	
	if event.responseCode  == GoogleBilling.OK then
		-- unlock
	end
 
	googlebilling:confirmNotification(event.notificationId)
end

Radiesel · December 2012

Aha ;-)) Just realized that in that case your sample code in the documentation is wrong

)

Honestly, documentation of StoreKit function finishTransaction() says:

Your application should call this function only after it has successfully processed the transaction and unlocked the functionality purchased by the user.

Sample code in documenation is implemented that way, that finishTransaction is called if purchase failed or succeeded... correct?

Same to your code above...

Michael

atilim · December 2012

Your application should call this function only after it has successfully processed the transaction and unlocked the functionality purchased by the user.

I've copy-pasted this information from Apple's reference manual

But you should call finishTransaction even if your transaction is failed. If you look at this documentation: http://developer.apple.com/library/ios/#documentation/NetworkingInternet/Conceptual/StoreKitGuide/AddingaStoretoYourApplication/AddingaStoretoYourApplication.html finishTransaction is called in step 8 (completeTransaction), step 9 (restoreTransaction) and step 10 (failedTransaction).

The only requirement for a failed purchase is that your application remove it from the queue. Therefore you should call finishTransaction to remove it from queue when your transaction fails.

Radiesel · December 2012

So, to make sure, this is different between Android and iOS? Because the above Android documentation says:

As a best practice, you should not send a CONFIRM_NOTIFICATIONS request for a purchased item until you have delivered the item to the user.

So if it failed, I have not delivered it to the user and should not call
googlebilling:confirmNotification(event.notificationId)

Is that correct? Thanks for your quick replies!
Michael

atilim · December 2012

I think documentation is not very clear about this situation. But google's official example code sends CONFIRM_NOTIFICATIONS even when the transaction fails.

To summarize, If the transaction fails or user cancels, don't deliver to user but send CONFIRM_NOTIFICATIONS request.

Radiesel · December 2012

thank you!

mertocan · December 2012

I got it thanks

mertocan · December 2012

@atilim
Event.REQUEST_PURCHASE_COMPLETE
Dispatched when requestPurchase function completes. It contains event.responseCode, event.productId, event.productType and event.developerPayload fields.

There isn't event.notificationId in request purchase. There is a problem in my phone now i can not access it. So i can not try. Will it work although it doesnt contain event.notificationId??

atilim · December 2012

@mertocan - you need to call confirmNotification function in Event.PURCHASE_STATE_CHANGE event (not in Event.REQUEST_PURCHASE_COMPLETE event).

atilim · December 2012

And don't blame me about these confusing event names. It's all google's fault

mertocan · December 2012

Oh okay now i understand completely

Thanks alot

Radiesel · December 2012

damned! InApp Purchasing was no longer working after playing around with Event.PURCHASE_STATE_CHANGE.

Whenever I click on "OK" to buy an item, Application crashed. Function onPurchaseStateChange() never called executed, although I set an Event Listener.

Right now, I figure out that you have to set the PublicKey to get this event. So finally I answered my question myself. After setting the publicKey, App no longer crashes and onPurchaseStateChange() function is called correctly.

regards
Michael

atilim · December 2012

Oh.. I'll look at it. If the user doesn't set the public key, there should be a logical Lua error instead of crashing.

Radiesel · December 2012

Well, I don't know how to debug that with LUA. Problem is, googlebilling does not work in an emulator, so I guess, it also does not work in GiderosPlayer, am I right? So I have to export the project and run it on a real device. Good thing is, I could use Android debug and that said:

java.lang.RuntimeException: Unable to start service com.giderosmobile.android.plugins.googlebilling.BillingService@41591608 with Intent { act=com.android.vending.billing.PURCHASE_STATE_CHANGED cmp=.....

As already mentioned, purchaseStateChanged() was never called in LUA (I added Alert boxes), but after I added the public key in googlebilling, there was no Android error any longer and also function got called correctly.

Reproducable and just for you as a hint...

best regards
Michael

mertocan · December 2012

You dont have to export the project. You just need to run project on the android device from gideros. I mean if you , have the giderosplayer lastest version on your device , you can run the project from gideros. It will also work correctly.

mertocan · December 2012

Now I am getting developer Error. When I change the api version , I am getting BillingUnavailable error.

require("googlebilling")
 
googlebilling:setApiVersion(0)
googlebilling:setPublicKey("...")
 
local function requestPurchase(event)	
 
	if event.responseCode ~= nil then
		print("error", event.responseCode)
		return
	end
 
	googlebilling:addEventListener(Event.PURCHASE_STATE_CHANGE,onPurchaseStateChange)
 
end
 
local function onPurchaseStateChange(event)	
 
	if event.responseCode  == GoogleBilling.OK then
		-- unlock
	end
 
	googlebilling:confirmNotification(event.notificationId)
end
 
 
if googlebilling:checkBillingSupported("productType") then
 
	googlebilling:addEventListener(Event.REQUEST_PURCHASE_COMPLETE, requestPurchase)
	stage:addEventListener(Event.MOUSE_DOWN, function()
		googlebilling:requestPurchase("...", "productType", "mert")
	end)
 
end

Radiesel · December 2012

@mertocan, why do you set ApiVersion? I didn't set it. If you do, shouldn't you set it to 2? Link above from Atilim showed, he implemented v2. I will also try the player on the device, thanks for the tip... I will bite my as if that works

(

@Atilim, that raises the question gideros SDK shouldn't be upgraded to v3? Google suggests to upgrade to version 3 (not sure about this).

best regards
Michael

Radiesel · December 2012

player on android and googlebilling works... gosh...

Howdy, Stranger!

Categories

In this Discussion

Top Posters

Android InApp Purchases and Public Key

Comments

Howdy, Stranger!

Quick Links

Categories

In this Discussion

Top Posters

Android InApp Purchases and Public Key

Comments