Thanks Kostya Vasilyev for your reply. I'm aware of the developer known issues. What is weird is that it's been written there for some time now and seems to affect people on a large scale only recently. This is just getting worse... I don't have enough experience on the maket for remembering a 25% canceled orders, but I find 12% cancelation rate is far too much already ;)
On Wednesday, October 3, 2012 1:09:16 AM UTC+2, Kostya Vasilyev wrote: > > > 2012/10/3 spocky12 <[email protected] <javascript:>> > >> I was about to post about the exact same problem when I saw this. Good >> news is I'm not alone. Bad news is we don't have any kind of information >> regarding this. > > > This is the best we have at this time, I believe: > > > http://support.google.com/googleplay/android-developer/bin/static.py?hl=en&page=known_issues.cs > > >> > Purchasing Issues > Problems with in-app billing and licensing server > We are aware the reports regarding in-app billing and Google licensing > server (LVL) issues, and are working on resolving these problems. Please > stay tuned and thank you for your patience. > > Report this issue > > << > > > >> My app uses in-app billing too. >> >> I used to have approximately 15% of canceled orders due to authorization >> refused and about 0 to 1% of "others" each day. >> Since last saturday, "authorization refused" didn't change but "others" >> is now about 12% of my commands :( >> >> "Authorization refused" was not so problematic because it's often related >> to bad account information. Most users usually corrected their account >> information and managed to finalize the command. This is unfortunately not >> true with "reason: other" as it seems that almost every user in that case >> can't manage to buy the app, no matter how many tries they make. This means >> I'm losing 12% of commands each day (hopefully users will try again in a >> few hours/days and won't abandon). >> >> @Nathan : I can't confirm about the "0" account age and didn't find any >> specific pattern. >> >> Can anybody confirm that removing/adding back the credit card is a >> successful workaround ? >> > > > Since I was the one who mentioned that, I can confirm that sometimes it > works and sometimes it doesn't, based on my limited interaction with users > regarding failed orders (not everyone writes, and I usually set up a > license in my own, back-up system, when Google's fails). > > Large scale, cloud-based computing sure is fun. > > Now imagine this in a different setting -- "Sorry Captain, the life > support systems have shut down due to an unexpected thread deadlock". > > HAL 9000 wasn't malicious, just buggy. > > -- K > > -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
