Re: [android-developers] Re: Working around API-purchase-logic-flaws for consumables in Google Play's Billing API v3 (Relevant to everyone using consumables with API v3)

2016-02-24 Thread Markus A.
Hi Gary, thank you for your reply! Unfortunately "trusting" the Google Play API is exactly what I'm having a problem with in this case: I'm convinced that Problem 2 in my original post is a fundamental design flaw in the API. And I still haven't found a good way to work around it (other than add

[android-developers] Re: Working around API-purchase-logic-flaws for consumables in Google Play's Billing API v3 (Relevant to everyone using consumables with API v3)

2016-02-23 Thread Markus A.
Bump! I'm really amazed that nobody seems to care about this! Shouldn't this be relevant to everyone selling consumable items on the Play Store? Has no-one ever experienced this failure mode coming up in production? Obviously, there's always the possibility that I'm just misunderstanding somet

[android-developers] In-App Billing v3 getSkuDetails() returns empty "description" on old versions of Play Store

2016-02-16 Thread Markus A.
When testing In-App Billing on an cheap, but relatively current device (the Samsung Replenish M580) that runs Android 2.2.2 and only supports Play Store v3.9.16, I found that the DETAILS_LIST returned by getSkuDetails()

[android-developers] Re: Working around API-purchase-logic-flaws for consumables in Google Play's Billing API v3 (Relevant to everyone using consumables with API v3)

2016-02-16 Thread Markus A.
PS: This is a cross-post from StackOverflow (http://stackoverflow.com/questions/30921789/working-around-api-purchase-logic-flaws-for-consumables-in-google-plays-billing) where I haven't been able to get any answers to this. Also: My apologies for all the line-breaks. Not sure where they all cam

[android-developers] Working around API-purchase-logic-flaws for consumables in Google Play's Billing API v3 (Relevant to everyone using consumables with API v3)

2016-02-16 Thread Markus A.
Version 3 of the Billing API removed the distinction between consumable and non-consumable products . Both have been combined into a new type called "managed" and behave somewhat like a hybrid: The app needs to actively call