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)
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 adding and maintaining multiple versions of each consumable SKU into the Play Store (yuck!)). I'm pretty sure that that failure mode is exactly the reason why every other app store (including Google Play in the past!) does make the distinction between consumable and non-consumable items. The practical difference between the two being that ownership for consumable items is tracked on a per-device level while ownership for non-consumable items is tracked globally across all devices for a given user. Removing this distinction from the API, the way I understand it, was a mistake that Google made and Problem 2 is how this mistake plays out in the real world... What I'm really trying to do is find some way to get a hold of someone at the relevant Google team about this. I've tried StackOverflow, here, and messaging them directly on Hangouts. I just cannot get a hold of anyone. -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. To post to this group, send email to android-developers@googlegroups.com. Visit this group at https://groups.google.com/group/android-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/android-developers/CAF%2BPrGigVYONDMa%3DoVeN6_BZy_JD6DqZgwuE5586mYx-gepDUg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
[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)
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 own (secure web) server to help keep track / verify some of purchase details as well. That's still mentioned at the end of - http://developer.android.com/google/play/billing/billing_integrate.html I found that useful as alternative to the 'journaling' you've suggested. I also attempted to (securely) store some of the details on the device itself as soon as they were received, but both of these approaches have their own issues - where you server is not available & where the user has multiple devices... In the end you just need to 'trust' the Google Play API's, but your own server can also help somewhat (with any disputes) by providing an independent transaction log even if it is sometimes incomplete. Regards On Wednesday, February 24, 2016 at 6:12:48 AM UTC+11, Markus A. wrote: > > 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 > something and there really is no issue, but given that every single other > app-store that I've ever worked with does distinguish between consumable > and non-consumable products makes me think there's a good reason for it. > > But, in the unlikely event that I am just seeing things here, PLEASE TELL > ME SO! > -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. To post to this group, send email to android-developers@googlegroups.com. Visit this group at https://groups.google.com/group/android-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/android-developers/95408ad1-98b0-4b67-a87c-17f59421e188%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[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)
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 something and there really is no issue, but given that every single other app-store that I've ever worked with does distinguish between consumable and non-consumable products makes me think there's a good reason for it. But, in the unlikely event that I am just seeing things here, PLEASE TELL ME SO! -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. To post to this group, send email to android-developers@googlegroups.com. Visit this group at https://groups.google.com/group/android-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/android-developers/11a7b384-ce03-4d2a-b616-7090131105dd%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[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)
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 came from. In the editor, it looked fine... -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. To post to this group, send email to android-developers@googlegroups.com. Visit this group at https://groups.google.com/group/android-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/android-developers/1da8d81f-0767-44c8-8c52-570628f0fd16%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
