fruitlangu / marketbilling

Automatically exported from code.google.com/p/marketbilling
0 stars 0 forks source link

You already have a pending order for this item #50

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
STEPS TO REPRODUCE:
1. Buy in an-app item, any application
2. Android market encounters a timeout during credit card processing and the 
user receives an email receipt which states "Took too long to deliver"
3. Subsequent attempts to buy the same in-app item results in the Android 
Market message: "You already have a pending order for this item. From that 
point on the user us NEVER able to purchase that item again. The message always 
pops up on every purchase attempt for the item.

EXPECTED OUTPUT:
User should be able to purchase the item - even after android market has 
whatever timeout is occurring. 

ACTUAL OUTPUT: You already have a pending order for this item

AFFECTED ORDER IDS (IF RELEVANT):

OS VERSION: All

MARKET/MYAPPS VERSION: 3.x+

DEVICE: All

OUTPUT FROM ADB BUGREPORT ATTACHED:
(Note: The output from "adb bugreport" is required for all bug reports.)

NOTES: I am attaching the screen shots from an application called 9-innings 
baseball. After reviewing the screen shots, it is quite clear that the issue 
resides within android market. This is where the error occurs and the state of 
the order lives. FIX THIS!!!!! The images are numbered in the order of the 
transaction steps: screen1, screen2, screen3, screen4 then screen5

Original issue reported on code.google.com by thebbk...@gmail.com on 17 Oct 2011 at 5:12

Attachments:

GoogleCodeExporter commented 9 years ago
This has been going on for months. You have had MANY, MANY tickets opened for 
this issue both from developers and consumers. You have been completely silent 
on this issue, so I suspect you guys are in a real bind somehow - opting to 
tell consumers that this is a developer issue when in fact you know very well 
that it isn't. 

The applications pass the order information to android market, then android 
market handles the processing. The applications DO NOT have any sort of state 
within the application as it relates to previous orders for a given item - it's 
all on the android market side. GOOGLE - YOU NEED TO CLEAN THIS UP AND FIX 
THIS!!! STOP HIDING, STOP PASSING THE BUCK TO DEVELOPERS, THIS HAS BEEN GOING 
ON FOR OVER TWO MONTHS NOW. FIX IT!!!!!!

Original comment by thebbk...@gmail.com on 17 Oct 2011 at 5:17

GoogleCodeExporter commented 9 years ago
Just received an update of android market to 3.1.5. The issue remains. Still 
can't purchase items that timed out in past transactions. Still getting the 
"You already have a pending order for this item". 

Original comment by thebbk...@gmail.com on 3 Nov 2011 at 10:34

GoogleCodeExporter commented 9 years ago
Same problem for my client. Still getting the "You already have a pending order 
for this item".

Original comment by iSolutio...@gmail.com on 9 Nov 2011 at 2:04

GoogleCodeExporter commented 9 years ago
Lynn from the Android Market Team sent me an e-mail last month in response to a 
compliant I filed on this issue. She acknowledged they are aware of some users 
getting stuck in a pending state and are working towards a solution. 

That was just over 1 month ago, and there has been an update to the market app 
that did not fix the problem. 

Original comment by DJGiet...@gmail.com on 17 Nov 2011 at 5:55

GoogleCodeExporter commented 9 years ago
Lynn was one of the people I've 'worked' with on this. I've opened several 
instances of this ticket. 

Lynn and I had a few emails go back & forth. Her last one was a request to send 
screen shots of how the problem manifests itself. They still did not believe 
that this was happening in the market. She wanted to see it the error was 
occurring within the app I was using (what difference does that make?). I did 
the screen shots - showing that the problem occurred as the purchase attempt 
moved from the app to the android market and occurred there. 

Once I sent that, I never heard from her again. I tried to keep the 
conversation via email going, but she (like the others) washed her hands of it 
- AND THIS is the thing that is really pissing me off. 

As a software engineer myself, this looks like a situation where they have a 
system (android market) that they simply do not have control of. It looks like 
there are multiple scenario's where this issue rears its head and they are not 
able to get their arms around it. When that happens, customers are left in the 
cold. 

I posted this question in a forum recently and I think it is a relevant 
question: 

Who would create a market system like this that was incapable of resetting or 
clearing attempted transactions which are stuck in a pending state for a month, 
two months, 3 months or more? Some of mine are quite a bit older than that. 
They do not have the ability to do this? I think it speaks loudly regarding the 
quality of this system. 

What a mess. 

Original comment by thebbk...@gmail.com on 17 Nov 2011 at 7:43

GoogleCodeExporter commented 9 years ago
I've tracked this issue when it was still #39. Google said it was 'known' and 
then marked three thread as invalid. I'm sorry, but such tactics to silence a 
quickly growing issue is unprofessional. I still can't conduct an in- game 
purchase for Handygames WWII, and Google's help still directs me to the 
powerless developer. I have money that Google's lazy engineers can't help me 
spend!

Original comment by macr0t0...@gmail.com on 6 Dec 2011 at 4:58

GoogleCodeExporter commented 9 years ago
I recently had a customer experience something very close to this (but instead, 
subsequent retries still gave the took too long message).

After about 45 attempts spanning two weeks and trying various different 
settings (MarketEnabler, spoofing etc) on his device, the in-app purchase 
eventually worked.

I'm speculating this could have been because of one of the following:

1. Some timeout on the Market server that lasts two weeks
2. Someone at Android Market manually cancelled the item (the customer had 
previously contacted Market support about this)
3. Some setting the customer changed on his device

If it is the first one, then asking the customer to wait two weeks (while 
certainly not ideal) could be an option...

Original comment by mjc1...@gmail.com on 14 Jan 2012 at 3:24

GoogleCodeExporter commented 9 years ago
I tryed getting a song and it ssid.I couldn't pay it with Tmobile so I tried 
switching the payment method but it just went back to the same message so then 
I when clicked ok it says u already have a pending order for this item now what 
do I do.

Original comment by silverit...@gmail.com on 20 Jan 2014 at 2:17