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
Hi,
I'd suggest you use the In-App purchase testing facilities Google provides
- https://developer.android.com/google/play/billing/billing_testing.html -
to test your theories about perceived failure scenarios.
When In-App purchases was initially introduced Google also recommended
using your o
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
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
4 matches
Mail list logo
