In billing applications giving me errors

Question

I played with both dungeon samples in the billing code of the application using google and the blundell tutorial in the billing code of the application. Both of these projects are mostly out of the box, in addition to changing the public key, renaming the application and uploading it to google, which I have already done. These two applications worked just fine recently (about 3 days ago). Now I get this error both in LogCat and in the device.

Device:

Error retrieving information from server. [DF-DFERH-01] 

LogCat:

 10-13 02:26:12.449: E/Volley(916): [90] BasicNetwork.performRequest: Unexpected response code 500 for https://android.clients.google.com/fdfe/purchaseStatus 10-13 02:26:12.457: W/Finsky(916): [1] CheckoutPurchase.onErrorResponse: DisplayErrorMessage[Error retrieving information from server. [DF-DFERH-01]] 10-13 02:26:12.457: E/Finsky(916): [1] CheckoutPurchase.setError: type=UNKNOWN, code=-1, message=Error retrieving information from server. [DF-DFERH-01] 

Answer 1

So, after I contacted Android support, I got a response. I have yet to check if the non-static check works. I will let you all know.

Comment No. 190 on issue 35564 byother ... @ gmail.com: error (DF-DFERH-01) http://code.google.com/p/android/issues/detail?id=35564

Hello to all. So I faced the same problem, answers to these last few days. I decided to ignore them and go ahead and check the real products (I was able to do this, since my application was already published live, without In-app courses, of course). Testing real products really worked.

After reading the IAP Testing Guide (Http://developer.android.com/guide/google/play/billing/billing_testing.html#billing-testing-static) I came across a quote:

"Note: Filling in-app billing requests with reserved product identifiers overrides the normal Google Play production system. When you submit an in-app billing request for a reserved product identifier, the quality of the service will not be comparable to the production environment."

So, it seems that something is really wrong with the static response of the service, but this does not reflect the conditions of the real game Store. I can vouch for this because my updated and live application has an IAP that works without problems. Therefore, if you have this problem, check if you can; this will probably work for you.