In-app billing has suddenly stopped working (Reason: We could not complete your order in a timely fashion)

[GoogleCodeExporter]

STEPS TO REPRODUCE:
1. User clicks a button in app which calls sendBillingRequest() with a 
REQUEST_PURCHASE and appropriate item ID in the bundle.
2. User attempts to complete the transaction by filling in the payment details.
3. As the app publisher, when I check orders for my app in my merchant billing 
account, I see the following order history for this user:

Order history
Sep 14     5:54 AM  Order cancelled You cancelled this order. 
Reason: Other (describe below) 
Message sent to customer: We could not complete your order in a timely fashion. 
Please verify your payment information in Google Checkout and try again later.
Sep 14     5:52 AM  Order received  You received a new order. Google has sent the 
customer an order confirmation email.

Other details:
I have had 4 orders rejected yesterday.  Prior to yesterdays, orders were 
getting accepted and processed correctly.  The specific example above has an 
order ID of 548217735428824.  My android app is published in the Android Market 
as "com.shiprack.client".  And it has only one in-app purchasable product: 
Remove Banner Ads (in-app product ID: com.shiprack.client.noads).  The only 
change on my part yesterday was the release of a new version to the android 
market, including a one-line bugfix regarding creating pending intents to 
trigger status-bar notifications.  This was completely unrelated to in app 
billing service.

EXPECTED OUTPUT:
Here's the "order history" I expect to see in the google checkout merchant 
account:
Sep 9     7:26 PM   Order shipped   You shipped this order.
Sep 9     7:26 PM   Order charged   The customer's credit card was successfully 
charged for $0.99.

ACTUAL OUTPUT:
Order history
Sep 14     5:54 AM  Order cancelled You cancelled this order. 
Reason: Other (describe below) 
Message sent to customer: We could not complete your order in a timely fashion. 
Please verify your payment information in Google Checkout and try again later.
Sep 14     5:52 AM  Order received  You received a new order. Google has sent the 
customer an order confirmation email.

AFFECTED ORDER IDS (IF RELEVANT):
There's 4 so far:
548217735428824
929372187312989
151796159540092
831663162506844

OS VERSION:
Different, depending upon the customer placing the order.  But ranges from 2.2 
to 2.3.3.

MARKET/MYAPPS VERSION:
Different, depending upon the customer placing the order.

DEVICE:
Different, depending upon the customer placing the order.

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

Can't provide you with one, because I tried buying my own in-app product using 
my Google account (rishi.r.arora@gmail.com), and that transaction failed for a 
different reason, and when I attempted again, I keep getting "you already have 
a pending purchase"

NOTES:
Losing revenue!

Original issue reported on code.google.com by rishi.ar...@ship-rack.com on 14 Sep 2011 at 1:23

[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:40

[GoogleCodeExporter]

There was big flood of this issue on September 14, and as of now, according to 
Google, this issue is fixed.

However, I still see the occasional cancellation with "Reason: Took too long to 
deliver" - even though the issue is reported as fixed and no longer appears on 
the "Known Issues" page.

Two happened just now, Sep 26, 2011 1:50 PM GMT+01:00.

Google, this is not acceptable for a production system. Please put some 
resources behind this and make it a priority.

And while I was typing this, another one came in..... So make that three for 
today (so far).

Some recent order numbers are:

548581651202235
866790510671310
541641961670291
956946040475223

Original comment by kmans...@gmail.com on 26 Sep 2011 at 1:09

[GoogleCodeExporter]

On Nov 14th, 2011
Order history 
Nov 14     4:40 PM Order cancelled You cancelled this order. 
Reason: Other (describe below) 
Message sent to customer: We could not complete your order in a timely fashion. 
Your order has been automatically canceled. Please retry your purchase. 
Nov 14     4:05 PM Order shipped You shipped this order. 
Nov 14     9:31 AM Authorization successful The customer's credit card was 
authorized for $1.75, and passed all risk checks. (Expires Nov 21, 2011 9:31:26 
AM EST) 
Nov 14     9:31 AM Order received You received a new order. Google has sent the 
customer an order confirmation email. 

Original comment by patel.as...@gmail.com on 15 Nov 2011 at 12:25

[GoogleCodeExporter]

Anybody has any new information about that issue? More than half of all In App 
purchases end up with it and we don't even have an idea about what to tell to 
the complaining customers (250 within the last 4 days).

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

[GoogleCodeExporter]

A bunch of our users have experienced this issue on and off since this summer. 
We tell customers that we're confident that Google will get it resolved soon 
and ask them to:

- Send us their order number so that we can add it to our own open ticket with 
Google.

- Report it to Google here: http://checkout.google.com/support/bin/request.py 
We hope that the more users report it, the faster they'll resolve it. 

- Try to re-request purchase status (I.e., if you have a method in your app to 
re-request purchase information, for example myapp://resetpurchases). This 
doesn't usually work for the PENDING issue, but works in cases where, for 
example, the purchase confirmation from Google never makes it back to the 
client.

- Uninstall Market updates (Menu > Settings > Applications > Manage 
Applications > Market > Uninstall Updates. Then, very quickly, re-attempt the 
purchase. This seems to work for most of our affected users (though hasn't 
lately for one or two), but they've got to be quick, as the Market pretty 
quickly updates itself in a lot of cases!

Original comment by jenhar...@gmail.com on 5 Dec 2011 at 3:23

[GoogleCodeExporter]

Thanks for your reply. We also collect the order (many) numbers and will now 
tell all customers to use the link you mentioned. Hopefully, if Google gets 
hundreds of complaints each day, they will eventually react and at least tell 
the developers what to do to work around the problem.

Original comment by garzo...@gmail.com on 5 Dec 2011 at 3:52

[GoogleCodeExporter]

I'm a customer and just ran into this issue today, after verifying with the 
merchant that there was no cancellation and with my credit card company that 
the transaction had been approved.  I've also submitted a report to Google, and 
hope that this gets resolved soon.

Original comment by kf...@juniper-strategy.com on 14 Dec 2011 at 7:40

[GoogleCodeExporter]

I believe this issue is preventing me from even installing this app. Gonna 
switch to my clean ROM environment and try downloading it there. 

Original comment by Darkamst...@gmail.com on 30 Jan 2012 at 8:01

[GoogleCodeExporter]

Seeing this issue and it's also reported here: 

http://code.google.com/p/marketbilling/issues/detail?id=5

Original comment by r...@equazi.com on 31 Aug 2012 at 2:23

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

 I've had a couple of customer reports of in app payment failures which have passed the initial check and then get cancelled by Google, so same issue again I think.
I've asked them to report it to Google, as it started happening on 31/08/2012.
These were order 550573440629318 and 975979891957440

Original comment by shawn.me...@gmail.com on 2 Sep 2012 at 6:05

[GoogleCodeExporter]

Same issue. Most of my customers complain of not being able to buy some items 
from my app using in-app billing. They rank my app on Google Play with ONE 
star! That's bad!

Some orders affected by this issue:
903006937021645
831450785927001
272936678349117
803826257172435
742862564288351
....

Original comment by mob...@3logic.it on 3 Sep 2012 at 2:28

[GoogleCodeExporter]

I'm just now trying to implement in-app billing for the first time and can't 
seem to get past this error. 

My very first test using a test account/device took the payment, but the 
upgrade didn't work. I found a typo in my code for matching the purchased item 
name and fixed it. I refunded myself from the test account. I then uploaded the 
new fixed version. My app isn't published, but the item is. I tried it again 
and now the whole thing keeps getting cancelled.

Sep 5     3:07 PM Order cancelled You cancelled this order. 
Reason: Other (describe below) 
Message sent to customer: We could not complete your order in a timely fashion. 
Please verify your payment information in Google Checkout and try again later. 
Sep 5     3:05 PM Order shipped You shipped this order. 
Sep 5     3:05 PM Authorization successful The customer's credit card was 
authorized for $2.99, and passed all risk checks. (Expires Sep 12, 2012 3:05:19 
PM PDT) 
Sep 5     3:05 PM Order received You received a new order. Google has sent the 
customer an order confirmation email. 

I don't understand how it took the payment on the very first try and now 
nothing.
I know the credit card is fine, I even bought an app to verify.

It doesn't say why exactly it timed out so I don't know where to go next.

Original comment by smka...@gmail.com on 6 Sep 2012 at 2:00

[GoogleCodeExporter]

This solution will not apply to most who are reporting on this issue, since 
many are only reporting a small percentage of the time in-app billing isn't 
working. In my case it was not working 100% of the time and it's my first app. 
I was sending out the purchase request and it kept coming back cancelled. I was 
following the Dungeons example and instructions. The part that tripped me up 
was changing the package name on the billing files. I used Eclipse's 
re-factoring wizard and it botched the Manifest file. It changed to <service> 
tag string's values to nonsense. Since this is my first app I didn't think to 
look in that file and it didn't give any compile errors. I had added the 
required stuff in that file prior to re-factoring. I thought it was all set and 
didn't even know it was changed by the re-factoring tool.

Original comment by smka...@gmail.com on 10 Sep 2012 at 1:20