Testing Google Play in-app purchase: android.test.canceled and android.test.refunded not working correctly

Solar2D Monetization (in-app purchases, ads, etc.)
#1

So been testing in-app purchasing in the Google Play version of my app and something is not working correctly with a couple of the Google Play reserved IDs.

If I use android.test.purchased or android.test.item_unavailable in the store.purchase() call, they work correctly.  I get the expected behavior in the Google Play dialogs and the correct store callback is returned.

If I use android.test.canceled or android.test.refunded in the store.purchase() call, the Google Play dialogs both show a purchase dialog and if I click the Buy button, the dialog displays “Payment successful” and disappears but no store callback is ever made.

Am I not understanding how those are supposed to work?  Do those not work correctly any longer with the v2 API that Corona has in place?

Should mention I am still using build 1202.

#2

Did you ever get this working thegdog?

I also get a “Payment Successful” message when testing with android.test.canceled.  I am using build 2177

#3

Honestly, I don’t remember the specifics of what was happening here when I posted this.

I do know that when you cancel a transaction that has not yet been charged, it takes a while for Google Play to return that.  For a while after, it still shows the purchase as completed.  I had to test that as part of the store.restore() functionality.  To make sure that I can lock things back up.

#4

I’m having same issue. Did you resolve it? How?

#5

Oh, I think I rememeber now.  That was using the Google test IDs.  And no, I never did understand why that didn’t work, I don’t think.  I just moved on to using my actual product IDs and tested from there.

Not sure if this is just a bug in the Corona IAP v2 API usage with Google Play, or an issue with the Google Play IAP v2 API itself, or if it still occurs with with the new IAP v3 API.  I am planning on moving to the new Google Play IAP v3 plugin, but probably won’t test using the Google IDs and will just test my existing code since most of it should continue to work as expected.

#6

Did you ever get this working thegdog?

I also get a “Payment Successful” message when testing with android.test.canceled.  I am using build 2177

#7

Honestly, I don’t remember the specifics of what was happening here when I posted this.

I do know that when you cancel a transaction that has not yet been charged, it takes a while for Google Play to return that.  For a while after, it still shows the purchase as completed.  I had to test that as part of the store.restore() functionality.  To make sure that I can lock things back up.

#8

I’m having same issue. Did you resolve it? How?

#9

Oh, I think I rememeber now.  That was using the Google test IDs.  And no, I never did understand why that didn’t work, I don’t think.  I just moved on to using my actual product IDs and tested from there.

Not sure if this is just a bug in the Corona IAP v2 API usage with Google Play, or an issue with the Google Play IAP v2 API itself, or if it still occurs with with the new IAP v3 API.  I am planning on moving to the new Google Play IAP v3 plugin, but probably won’t test using the Google IDs and will just test my existing code since most of it should continue to work as expected.