Application Billing Error

Question

My purchase of [UNMANAGED] in the application will not work before it works perfectly, which I can successfully buy with test accounts. But this does not work suddenly, since I remember what I did with the Merchant Account, add another 2-4 test accounts. Then after adding my in-app purchase will not work. So I updated the public key and downloaded Apk as a draft. But it won’t work anyway.

When the application is on the Google Play page, I received a LogCat error:

11-20 17:00:18.840: E/Finsky(2182): [187] FileBasedKeyValueStore.delete: Attempt to delete 'paramsqE9ZgJf5Z6GeZu1wwGPosw' failed! 

Then, when I click the Buy and Accept button, I received only these LogCats:

 11-20 17:00:39.520: I/BillingService(2408): handleCommand() action: com.android.vending.billing.RESPONSE_CODE 11-20 17:00:39.520: I/LoginActivity(2408): purchase was successfully sent to server 

I expect for Security Verification Logs and onPurchaseStateChange(...) be called, but I am not getting any onPurchaseStateChange.

Please help me with this problem.

Also, when I test android.test.purchased the reserved product IDs for testing static in-app billing responses , but still get the same logs / responses.

UPDATE -----------------------

I deleted some test accounts , but left only two (as @Tigger suggested ). And now I am not getting any errors from the Google page . But the onPurchaseStateChange () function did not work. And I have not received any logs from Security.java .

Last log I received: "the purchase was sent successfully to the server"

Answer 1

This may not be the correct answer, but from my personal testing and notes taken from around the place:

• In the application project you are downloading, you must have the same “version code” and “version name” as the ones you are testing.
• If you download a new version (with a new “version code” or “version name”), it may take 4 to 24 hours before the new version works correctly for testing.
• Double check that the account used on the device is actually one of the test accounts.
• Your APK project that you download must be signed with the same key that will be used in the final version.
• For testing on the device (the emulator will not work with the Play Store), while the "version code" and "version name" correspond to the APK project in the Play Store, testing and debugging work.

Hope this helps.

Edit: some changes to clarify a few points.

Answer 2

I had this error, but my error was that the loading behavior changed.

It used to be that you uploaded the APK as a draft to the Production tab of the Play Store toolbar. Now you need to upload the toolbar to the Alpha tab and publish your application ( http://developer.android.com/google/play/billing/billing_testing.html#draft_apps ).

Do not worry if you are still in pre-production in your application; if you don’t have an APK on the work tab when publishing, nothing will appear on the Play Store.