Error message "You already have a pending order for this item" with Market V 3.0.27

[GoogleCodeExporter]

STEPS TO REPRODUCE:
1. Purchase an In-App item, and receive the message back "Order cancelled -- 
Google cancelled this order. Reason: Took too long to deliver"
2. Try to order item again. Market app displays error "You already have a  
pending order for this item"

EXPECTED OUTPUT:
Ability to order item again after Google cancelled order.

ACTUAL OUTPUT:
"You already have a  pending order for this item", even though order is 
cancelled.

AFFECTED ORDER IDS (IF RELEVANT):
411886211332573, 411886211332573
OS VERSION:
2.3.4

MARKET/MYAPPS VERSION:
3.0.27

DEVICE:
Samsung Galaxy Tab 7"

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

NOTES:
Uninstall updates for Market app back to version 2.3.6 doesn't get error 
anymore.

Original issue reported on code.google.com by sdk...@gmail.com on 5 Aug 2011 at 8:27

[GoogleCodeExporter]

a bundle with RESTORE_TRANSACTIONS just kicks back with a response 
RESULT_SERVICE_UNAVAILABLE. So if i make the purchase, it can go through if i 
store it on purchase state changed, if i uninstall/reinstall, i cant retrieve 
it.

If it fails on purchase state changed and i launch the app on a pre 3.0.27 
market on dif device, i can restore transactions. Always going back to device 
with 3.0.27 fails to restore though.

Original comment by dasac...@gmail.com on 7 Aug 2011 at 6:27

[GoogleCodeExporter]

ok this is pretty whack. Basically i found a way to make this work on 3.0.27 
and it has to do with the length of the package name.

First off, i tried an in-app purchase with a random product out there already 
(tank wars) and the package name is com.rainbow.Wowo2

For privacy, ill list the number of characters in two test drafts that were 
experiencing the issue
[3].[6].[11] and
[3].[10].[11]

I then went to spike an answer on a dev account and gave the package name 
something quick and short for no particular reason
[3].[4].[4]
and did not experience a single issue. I found it curious so i shortened the 
name of the original package considerably
[3].[6].[3]
and it works. I still experience some sort of error on the response code that 
does not happen pre-3.0.27 even though the response code comes back OK, 
nevertheless, the purchase state updates correctly and restore transactions 
works correctly as well.

Any ideas whats up with this?

Original comment by dasac...@gmail.com on 7 Aug 2011 at 7:31

[GoogleCodeExporter]

I just got stuck with this issue. I attempted to purchase the app using a test 
account over a spotty connection. The order was cancelled (order number 
168059133148286) but my app still says I have a pending order.

Unlike comment #1 above, my RESTORE_TRANSACTIONS calls return RESULT_OK

D/Finsky  (17490): [1] MarketBillingService.sendResponseCode: Sending response 
RESULT_OK for request 4226517045960613403 to com.choiceofgames.dragon.
V/com.choiceofgames.dragon.ChoiceOfTheDragon(17906): 
onRestoreTransactionsResponse 
com.choiceofgames.choicescript.billing.BillingService$RestoreTransactions@44d799
78, RESULT_OK

But when it comes time to launch the IabActivity, my app gets a 500 error from 
the https://android.clients.google.com/fdfe/purchase service.

I/ActivityManager( 1294): Starting activity: Intent { 
act=android.intent.action.VIEW 
cmp=com.android.vending/com.google.android.finsky.activities.IabActivity (has 
extras) }
D/Finsky  (17490): [1] SelfUpdateScheduler.checkForSelfUpdate: Skipping 
self-update. Local Version [8006027] >= Server Version [0]
I/ActivityManager( 1294): Displayed activity 
com.android.vending/com.google.android.finsky.activities.IabActivity: 350 ms 
(total 350 ms)
D/Finsky  (17490): [1] CarrierProvisioningAction.run: No need to fetch 
provisioning from carrier.
D/Finsky  (17490): [1] GetBillingCountriesAction.run: Skip getting fresh list 
of billing countries.
D/GoogleLoginService( 1499): onBind: Intent { 
act=android.accounts.AccountAuthenticator 
cmp=com.google.android.gsf/.loginservice.GoogleLoginService }
D/Finsky  (17490): [1] DfeRequest.deliverResponse: Not delivering second 
response for request=[[ ] 
https://android.clients.google.com/fdfe/details?doc=inapp:com.choiceofgames.drag
on:adfree NORMAL 41]
E/Volley  (17490): [11] BasicNetwork.performRequest: Unexpected response code 
500 for https://android.clients.google.com/fdfe/purchase
W/Finsky  (17490): [1] CheckoutPurchase.onErrorResponse: SERVER: You already 
have a pending order for this item.
E/Finsky  (17490): [1] CheckoutPurchase.setError: type=NETWORK_OR_SERVER, 
code=-1, message=You already have a pending order for this item.
D/Finsky  (17490): [1] MarketBillingService.sendResponseCode: Sending response 
RESULT_SERVICE_UNAVAILABLE for request 8714980511491476573 to 
com.choiceofgames.dragon.
V/com.choiceofgames.dragon.ChoiceOfTheDragon(17906): onRequestPurchaseResponse 
com.choiceofgames.choicescript.billing.BillingService$RequestPurchase@44d7c048, 
RESULT_SERVICE_UNAVAILABLE

Original comment by choiceog...@gmail.com on 8 Aug 2011 at 5:48

[GoogleCodeExporter]

I just got another 500 error from 
https://android.clients.google.com/fdfe/purchase in a different app, order 
number 844994873371129. In this case, the phone/logcat says:

E/Volley  (17490): [10] BasicNetwork.performRequest: Unexpected response code 
500 for https://android.clients.google.com/fdfe/purchase
W/Finsky  (17490): [1] CheckoutPurchase.onErrorResponse: SERVER: Your order is 
processing, your item will be available in a few minutes.

But Checkout says the order was cancelled, "We could not complete your order in 
a timely fashion."

In both cases, reinstalling the app doesn't help, and RESTORE_TRANSACTIONS 
returns RESULT_OK.

Original comment by choiceog...@gmail.com on 8 Aug 2011 at 6:31

[GoogleCodeExporter]

basically, im finding its all about when you create the draft apk. Pick the 
wrong time of day and software with the new app market installed will 503. 
Simply deleting the apk and recreating it with the exact same everything and 
there's no issue anymore.

Original comment by dasac...@gmail.com on 8 Aug 2011 at 9:22

[GoogleCodeExporter]

This is a serious bug. Some users are already starting to contact me - they 
tried to buy the in-app product, the order was cancelled (took too long) and 
they can't buy it again.

Original comment by daniel....@gmail.com on 9 Aug 2011 at 12:36

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Contrary to comment #5, deleting the APK and recreating it did not fix my 
problem.

Original comment by choiceog...@gmail.com on 12 Aug 2011 at 4:06

[GoogleCodeExporter]

Comment #5 is irrelevant IMO. This happens with shipping apps which didn't have 
this problem until recently.

Google folks, please answer the following:

- What's the root cause?
- What can developers do to prevent this?
- What can developers do to remedy this?
- What can users do to get unstuck?

Original comment by virajm...@gmail.com on 13 Aug 2011 at 9:29

[GoogleCodeExporter]

You can try the following, rolling back the market update.

* Get off of wifi to provide a longer delay before market reupdates itself
* Prep the area in the game to make in-app purchase
* Go to Settings -> Applications -> Manage, select the market app from All tab
* Choose the option to uninstall updates
* Open market app to re-accept terms of service
* Long press home and go back to game to make purchase before 3.0.27 update 
comes down and installs

Alternatively, if you're phone is rooted, you could set the market apk to read 
only to prevent the update from installing.

Original comment by dasac...@gmail.com on 13 Aug 2011 at 9:36

[GoogleCodeExporter]

Any updates to this issue? I have a game where I can buy some items in game, 
but other items give me this error message. I've tried uninstalling the market 
updates and that didn't help. 

ANy suggestions for workarounds? When will this be fixed?

Original comment by thebb...@gmail.com on 14 Aug 2011 at 1:49

[GoogleCodeExporter]

Related forum thread: 
http://www.google.com/support/forum/p/Android+Market/thread?tid=0a4dfde89848e59a
&hl=en&fid=0a4dfde89848e59a0004aa6dd56e18c3

Original comment by virajm...@gmail.com on 14 Aug 2011 at 2:24

[GoogleCodeExporter]

Rolling back the market update as described in comment #11 worked for me, 
though I had to try it several times to get the timing right.

In my case, the problem isn't with a production user, but with the test account 
for my app. So when I tried cancelling the order in the course of testing, the 
problem came back. But at least now I think I can work around it reasonably 
well.

Original comment by choiceog...@gmail.com on 16 Aug 2011 at 7:42

[GoogleCodeExporter]

I tried the steps outlined in comment 11. Didn't work for me. I'm trying to 
purchase 2 different items in 9-innings baseball. I can buy other items, just 
not the two that I want. I still get the same old error in market. When I look 
at my transaction history, the two items I am trying to purchase showed up as 
canceled and when I look at the details - the "took too long" message is in 
there. I've called google and opened a ticket with them, but have not heard 
anything back, despite attempts to get an update on what's happening. As far as 
I know, Google has been completely silent in regards to this issue. Not very 
good. 

Original comment by thebb...@gmail.com on 17 Aug 2011 at 1:14

[GoogleCodeExporter]

My users have been reporting this to me as well. Now that the new market is no 
longer optional, rolling back the updates doesn't help.

Original comment by Adam.Sch...@gmail.com on 18 Aug 2011 at 12:05

[GoogleCodeExporter]

As a consumer, I called android market, had a case opened up and was told I 
should hear something back within 24 hours. After two days, I called again - 
and still no word at all. To my knowledge Google has been completely silent on 
this issue. I couldn't even get an ETA or even the most general idea of what 
the problem is. As brilliant as most of these folks are, seems like they really 
dropped the ball on this one. 

Original comment by thebb...@gmail.com on 18 Aug 2011 at 4:00

[GoogleCodeExporter]

Hi everyone,
If you're experiencing this, please contact Android Market support:

https://www.google.com/support/androidmarket/developer/bin/answer.py?answer=1366
01&hl=en

You can tell them to reference bug 5126349, which is our internal tracking 
number for this.

As has been mentioned before, this is *not* the place to report service issues. 
We use this issue tracker to hold the open-source sample code for in-app 
billing. This tracker is for that.  It isn't monitored frequently, so it is not 
appropriate for any time-sensitive issues.

I'll add that we're aware of this issue, but there's no useful information that 
I can give out at this time. (But again, please contact Android Market support 
if you're experiencing this. We use the volume of support tickets to determine 
how many people are impacted by a bug.)

I'm closing this issue as invalid. This isn't because this isn't a valid bug, 
but because it's not a valid bug for *this* issue tracker. The Market team has 
a bug open for this, and will continue to track it there until this is resolved.

Original comment by trevorjohns@google.com on 24 Aug 2011 at 1:45

• Changed state: Invalid
• Added labels: Google-5126349

[GoogleCodeExporter]

Google... I've reported this to Android Market support several times, but not 
had any response. Now every order is failing on a consistent basis, losing me 
approx $20 for every day this is broken. 

Worst of all, when my customers contact you for support, you are telling them 
to "Contact the developer". I CAN'T DO ANYTHING FOR THEM... it's YOUR bug, 
affecting MY revenue and reputation. FIX IT!!!

Original comment by mar...@longhome.co.uk on 14 Sep 2011 at 3:40

[GoogleCodeExporter]

Same problem here. Starting today getting this status for every single 
purchases. Contacted Google, but haven't get an answer from them yet.

Original comment by michael....@gmail.com on 14 Sep 2011 at 4:22

[GoogleCodeExporter]

Same as!

We only released the app yesterday as well.

Original comment by a...@full-fat.com on 14 Sep 2011 at 5:17

[GoogleCodeExporter]

Something else is going on today - we are seeing what Comment 20 describes. We 
typically receive 1-5 reports a day where users end up in permanent 
purchase-pending limbo. Checkout Support is unresponsive to us, and 
consistently run our customers in circles when they report the issue as well 
(we ask them to do this to hopefully accelerate a fix on Google's side).

However, today - ALL of our orders are in a Cancelled state with "We could not 
complete your order in a timely fashion." Not good. Have attempted to report 
it, but checkout support provides no way to report the issue description and it 
typically takes 48-72 hours to get an auto-reply to respond to. They aren't 
responding to our running ticket over bug 5126349, either.

I know this is the bug reporting system for the market billing API, not Google 
Checkout, but not quite sure what to do at this point.

Original comment by jenhar...@gmail.com on 14 Sep 2011 at 5:46

[GoogleCodeExporter]

same problem here. 

Original comment by alexpch...@gmail.com on 14 Sep 2011 at 5:52

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Ditto for me as well, and my cancelled purchases are showing "Message sent to 
customer: Order canceled due to internal error in Market."

Original comment by mport...@gmail.com on 14 Sep 2011 at 6:03

[GoogleCodeExporter]

I received this error this morning as well.  Google cancelled my order and I 
can't repurchase the product because it says it's pending.

Original comment by rscho...@gmail.com on 14 Sep 2011 at 6:09

[GoogleCodeExporter]

I'm still having this issue as well -- I got some response from Google in the 
beginning, but they seemed determined to blame the problem on everything EXCEPT 
the market app.  They told me to check with everyone from my bank to the 
application's developer. (Neither of which was the problem)  As of Sept 2nd I 
have had no responses from the Android Developer side. 

Original comment by ange...@googlemail.com on 14 Sep 2011 at 6:40

[GoogleCodeExporter]

This is a critical bug. I have hundreds of users complaining of the issue, and 
they are all being told it's a "developer problem" by the Android market user 
support.

It'll be a developer problem when I have anything to do with billing in any 
way, shape or form, Google.

Original comment by whaleson...@gmail.com on 15 Sep 2011 at 3:45

[GoogleCodeExporter]

I was able to bypass this issue by clearing out the cache for the Market 
application, uninstalling, reinstalling and quickly purchasing the update to 
the puzzle game I was desired.

Original comment by eccho...@gmail.com on 15 Sep 2011 at 3:55

[GoogleCodeExporter]

I am also seeing this issue.

Error message displayed: "You already have a pending order for this item".

Notes:
  - 2 items give this error as far as I know.
  - Items were cancelled, email was sent to me indicating cancellation
  - I have uninstalled Market App updates, cleared cache, force closed, etc. without any luck.

Original comment by mitchcha...@gmail.com on 16 Sep 2011 at 5:38

[GoogleCodeExporter]

Google…so you have given me the runabout long enough!!! When are you going to 
fix this stupid problem of "you already have a pending order".  Seems like 
maybe I should be changing my business to another APP DOWNLOAD SITE!!!!  I feel 
bad for the developers on your crappy market that can't get this shit 
straightened out BY YOU!!!
Man UP…and spend some time to fix this crap!!!
I'e already sent in my information about my order to you….after which you 
sent a response that its the develpers fault and I need to talk to them.  So 
f@#*ing look up my information yourself and let me know when you have your head 
out of your ass and have solutions!!!  Have a great day!

Original comment by rscott.n...@gmail.com on 2 Oct 2011 at 2:14

[GoogleCodeExporter]

This bug is still affecting us. 20% of purchases are being declined because of 
this.

Original comment by adylitic...@gmail.com on 10 Oct 2011 at 4:13

[GoogleCodeExporter]

This is not a developer issue Google. Did Osama Bedier develop this mess for 
you and hide the code? 

The only way I got past this problem was to wipe the phone - so I could sign 
into android market under a new account. I reloaded the software and was able 
to buy in-app items again, that is until the timeouts returned within a day. 

Incredibly, this is still not on the known issues page.

Original comment by thebbk...@gmail.com on 10 Oct 2011 at 3:42

[GoogleCodeExporter]

same the problem,any update?

Original comment by fyiu...@gmail.com on 12 Oct 2011 at 6:53

[GoogleCodeExporter]

Same problem here. Market Version 3.1.5

Original comment by solo...@gmail.com on 12 Oct 2011 at 7:26

[GoogleCodeExporter]

Same problem. I can't add to the information, but I have several customers that 
can't order now. 

Original comment by critter...@crittermap.com on 18 Oct 2011 at 4:16

[GoogleCodeExporter]

I get this problem if I try to send a payload with my billing request. Sending 
null, it works fine

Original comment by steven.e...@gmail.com on 19 Oct 2011 at 3:42

[GoogleCodeExporter]

**** Since Issue 39 has been closed by Google, I opened another case (case 50), 
which is open at this time. I included screen shots of one example of this 
error. 

If Google would like us to open the tickets in the appropriate areas, perhaps 
they ought to address THIS ISSUE instead of ignoring it completely. Both 
developers and consumers have been COMPLETELY IGNORED on the issue of "You 
Already Have a Pending Order For This Item" when reporting this through the 
appropriate channels. 

Original comment by thebb...@gmail.com on 20 Oct 2011 at 4:36

[GoogleCodeExporter]

We are waiting for this issue to be resolved before releasing any new 
applications with in-app purchases.

Putting our efforts to release iOS applications instead.

Original comment by mis.andr...@gmail.com on 28 Oct 2011 at 9:11

[GoogleCodeExporter]

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:05

[GoogleCodeExporter]

During the last 4 days, I received more than 250 emails reporting that issue - 
unfortunately none of them was from Google and providing any hints about how to 
prevent it. Anybody else got any further?

Original comment by garzo...@gmail.com on 5 Dec 2011 at 8:31

[GoogleCodeExporter]

55% of purchases are being declined because of this!

Original comment by mobiwolf...@gmail.com on 15 Dec 2011 at 3:12

[GoogleCodeExporter]

This is actually in the Known Issues now:
https://support.google.com/androidmarket/developer/bin/static.py?hl=en&page=know
n_issues.cs
------------------------------------------
Pending app and in-app orders
We're aware that some users are experiencing error messages surrounding pending 
app or in-app orders and that this prevents our users from purchasing these 
items again, and we're currently investigating. Thanks in advance for your 
patience.
------------------------------------------
patience....patience....patience....patience

Original comment by sdk...@gmail.com on 15 Dec 2011 at 3:16

[GoogleCodeExporter]

Well, it doesn't seem to help much even if it is in Known Issues. People are 
loosing on this. Google can you please be more polite to the developers 
supporting your platform? We need answers. WHEN will this be fixed? People have 
been waiting for a fix for this for almost a year now.

Original comment by inkognit...@gmail.com on 6 Mar 2012 at 4:01

[GoogleCodeExporter]

This issue has been going on for too long, it is even within the list of known 
errors for months now.  This is an unacceptable loss of money for people 
supporting the platform! Let some heads roll!

Original comment by juan.rod...@intermedianetwork.com on 9 Mar 2012 at 11:12

[GoogleCodeExporter]

Folks, this is a BLOCKER. Wow.  This is keeping me from installing flash 
player, and most other key apps.  Pretty much a show stopper for android 
platform.    

Original comment by rathomas...@gmail.com on 23 Mar 2012 at 3:15

[GoogleCodeExporter]

Since Google does not seem to show any interest in solving this problem, which 
is highly annoying for customers and seriously falling back on the developers 
(who cannot do anything about it), I now recommend all customers who ask me to 
switch to an iPhone. Apple is able to make that work. Of course, most customers 
have no interest in switching, but indeed it would be best for them.

Original comment by garzo...@gmail.com on 23 Mar 2012 at 6:13

[GoogleCodeExporter]

I'm experience this issue too, it seems like this bug was left unfixed for more 
than a year!

Original comment by Oren.Bengigi on 1 May 2012 at 7:48

[GoogleCodeExporter]

Wow... swore I'd never use an apple product "I really dislike the company" but 
if I can't buy apps, or books anymore with Google wallet I don't have much 
choice (and for the last week and a half I can't - even after multiple emails 
to support). I can't believe people have been having THIS problem for THIS 
f*Inc long. Way to go Google.

Original comment by twode...@gmail.com on 5 Jul 2012 at 5:35

[GoogleCodeExporter]

Had the same issue for several days. Customers try to buy items and received an 
email.

We could not complete your order in a timely fashion. Please verify your 
payment information in Google Checkout and try again later.

Now whenever they try to re-purchase an item that they received this message 
on, it says "You already own this item". But they don't and doing a restore 
transactions only sends receipts for the items they actually own. HELP!

Original comment by JamesHay...@gmail.com on 29 Aug 2012 at 3:04