在应用内计费误差 [英] In-app Billing Error

问题描述

我的[UNMANAGED]在应用程序内购买将无法正常工作，之前，它完美的作品，我可以使用测试帐户成功购买。但它突然不工作，我记得我做了什么，以商家帐户只能增加更多的2-4测试帐户。然后加入后，我在应用程序内购买将无法正常工作。所以，我更新了公共密钥和上传的.apk为草稿。但仍然无法工作。

My [UNMANAGED] in-app purchase won't work, Before it works perfectly which I can purchase successfully using Test Accounts. But it suddenly won't work, as I remember what I did to Merchant Account is only add more 2-4 Test Accounts. Then after adding, my in-app purchase won't work. So I updated the public key and upload an Apk as draft. But still won't work.

当应用程序是在谷歌播放页面，我收到了LogCat中的错误：

When the app is in 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!

然后当我点击了购买和放大器;接受按钮我只收到了这些LogCats：

Then when I click the Buy & Accept button I only received 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

我期待着为安全验证的日志和 onPurchaseStateChange（...）来调用，但我不吨得到任何onPurchaseStateChange。

I am expecting for Security Verification's Logs and onPurchaseStateChange(...) to called, but I don't get any onPurchaseStateChange.

请帮我解决这个问题。

此外，当我测试的 android.test.purchased 的静态测试应用内计费回应，但仍然得到了同样的日志保留产品ID /响应。

Also when I test android.test.purchased the reserved product IDs for testing static in-app billing responses but still got the same Logs/Responses.

更新-----------------------

我删除了一些测试帐户，但只留下两（所建议的 @Tigger 以下）。而现在我没有收到任何错误从谷歌页。但还是在 onPurchaseStateChange（）功能不火。而我并没有收到任何日志 Security.java

I removed some Test Accounts but leaving only two (as suggested by @Tigger below). And now I'm not getting any error from Google page. But still the onPurchaseStateChange() function didn't fire. And I didn't receive any Logs from Security.java.

我收到的最后一个记录是：购买成功发送到服务器

The last Log I received is: "purchase was successfully sent to server"

推荐答案

这可能不是一个正确的答案，但是从我个人的测试和笔记采取所有的地方：

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

• 的草案的应用程序，你上传的必须具有相同的版本code和版本名称为已任，你正在测试。
• 如果您上传一个新的版本（使用新的版本code或版本名称）可能需要4到24小时之前，在新版本将正常工作测试。
• 双击检查设备上使用的帐户实际上是在测试帐户之一。
• 您认为您上传的APK草案必须与将在最终版本中使用相同的密钥进行签名。
• 对于一个设备（仿真器将无法与Play商店的工作）的测试，只要版本code和版本名称相匹配的APK草案Play商店，测试和调试的工作原理

• The draft app you upload must have the same "version code" and "version name" as any that you are testing.
• If you upload a new version (with a new "version code" or "version name") it can take 4 to 24 hours before the new version will work correctly for testing.
• Double check that the account used on the device is in fact one of the test accounts.
• Your draft APK that you upload must be signed with the same key that will be used on the final version.
• For testing on a device (the emulator will not work with the Play Store), so long as the "version code" and "version name" match the the draft APK in the Play Store, testing and debugging works.

希望有所帮助一点。

修改的：有些变化澄清几点

Edit: Some changes to clarify a few points.

这篇关于在应用内计费误差的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！