应用程序错误：此版本的应用程序未配置市场计费
几天后，Android 应用程序中可以使用应用程序内结算。当然非常酷。因此，我开始对我的应用程序进行更新来实现这一点。但现在我遇到了一些问题。这就是我所做的：
- 我首先尝试保留产品 ID 来测试静态应用内 计费响应。这样做没有问题。
- 我将草稿 APK 上传到市场（带有生产签名，没有调试签名），其中包含 com.android.vending.BILLING 权限。
- 当我这样做时，我能够将“应用程序内产品”添加到我在市场上的应用程序并将其状态设置为已发布。
- 我创建了一个测试用户并重置了我的设备，使该测试用户成为我的测试设备上的主帐户。
- 保留的产品 ID 仍然有效。
现在问题来了。当我使用自己的产品 ID（我之前添加的产品 ID，请参见上文）时，会显示一个对话框，其中包含以下文本：
“应用程序错误：此版本的应用程序未配置为市场计费。请检查帮助中心以了解相关信息更多信息。”
我在日志中找不到任何奇怪的东西。有人知道我在这里做错了什么吗？
Since a couple of days it's possible to use in-app-billing in Android apps. Very cool of course. So, I started working on a update for my application to implement this. But now I run into some problems. This is what I did:
- I first tried the reserved product IDs for testing static in-app
billing responses. That works without problems. - I uploaded a draft APK to the market (with production signing, no debug signing), that included the com.android.vending.BILLING permission.
- When I did that I was able to add a 'In-app Products' to my app in the market and set it status to published.
- I created a test user and reseted my device to make that test user the primary account on my test device.
- The reserved product id's still work.
Now comes the problem. When I use my own product ID (the one I added before, see above) a dialog is shown with the following text:
"Application Error : This version of the application is not configured for Market Billing. Check the help center for more information."
There is nothing strange I can find in the log. Anyone knows what I'm doing wrong here?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（10）
我刚刚遇到这个问题，并意识到这是因为我正在运行我的应用程序的调试、未签名版本。在 Eclipse 中，当我导出并签署我的应用程序并将其安装在手机上时，我就能够使用我的应用内产品而不会看到此错误消息。
I just encountered this issue and realized it was because I was running a debug, unsigned version of my app. In Eclipse, when I exported and signed my application and installed it on the phone, then I was able to use my in-app products without seeing this error message.
我发现，一旦我将 APK 的新副本上传到市场，我就会在接下来的一个小时左右遇到“应用程序错误”。至少一小时过去后（有时需要长达两个小时），然后我不再收到该错误，然后我可以毫无问题地购买我的物品。 Google 服务器似乎至少需要一个小时来处理您上传新 APK 的事实（关于 APK 的应用内计费方面）。
因此，我的建议是您上传 APK 后等待 1 到 2 小时，然后看看是否仍然收到“应用程序错误”。
I have found that once I upload a new copy of my APK to the market, then I experience that "application error" during course of the next hour or so. After at least one hour has gone by (sometimes up to two hours need to have gone by), then I no longer get that error anymore and I can then purchase my items without any problems. It seems that the Google servers need at least an hour to process the fact that you have uploaded a new APK (with regards to the InApp Billing aspect of the APK).
So my advice is for you to wait 1 to 2 hours after uploading your APK, and then see if you still get the "application error".
我也遇到了这个问题。我终于意识到我发布的应用程序的 versionCode 为 3，我的草稿（具有计费权限的未发布的 apk）的 versionCode 为 4，而我用来测试应用内计费的签名 apk 仍为 versionCode 3。将 versionCode 更改为 4，我能够访问我请求的购买的实际应用内产品页面。
I also ran into this problem. I finally realized that my published app had a versionCode of 3, my draft (unpublished apk with the Billing permission) had a versionCode of 4, and the signed apk I was using to test in-app billing was still at versionCode 3. Once I changed the versionCode to 4, I was able to get through to the actual in-app product page for the purchase I was requesting.
当作为草稿上传的 apk 与测试模式下在系统上运行的 apk 不匹配时，在已签名的已发布版本上可能会发生这种情况。只要确保您的构建匹配，您在测试模式下应该没问题，并且不会再看到错误。
这里最大的担忧是我们会在生产中看到同样的行为，即我们发布带有应用内计费的 1.0.0-1，然后发布 1.0.0-2，运行 1.0.0-1 的用户将被无法购买或恢复购买并将收到相同的错误（非常糟糕的用户体验）。一直在搜索文档以查找特定于测试模式的行为，但到目前为止还没有运气；我们在此处添加了一个错误：http://code.google.com/p/市场计费/问题/详细信息？id=15#c0
This can happen on signed, released builds when the apk uploaded as a draft does not match the apk running on your system in test mode. Just make sure that your builds match up, you should be alright in test mode and will stop seeing the errors.
The big worry here is that we'll see this same behavior in production, i.e., we release 1.0.0-1 with in-app billing, then we release 1.0.0-2, and users running 1.0.0-1 will be unable to purchase or have their purchases restored and will receive the same error (very bad user experience). Have been scouring the docs for mention of this behavior as specific to test-mode, but no luck so far; we've added a bug here: http://code.google.com/p/marketbilling/issues/detail?id=15#c0
我也遇到了同样的问题...但现在问题已经解决了
我的观察基于一些试验：
希望这有帮助
I also encountered the same issue...but now issue is solved
My observations based on few trials:
Hope this helps
从重复的问题复制： https://stackoverflow.com/a/22469253/1321401
出现此错误的原因可能有多种。
以下是 Google IAB 测试的要求列表。
先决条件：
测试要求：
PS：使用发布证书调试：https://stackoverflow.com/a/15754187/1321401 （感谢 @dipp 提供链接）
PPS：很早就想列出这个列表了。
感谢 @zlgdev 进行更新
Copied from duplicate question: https://stackoverflow.com/a/22469253/1321401
This error may occur for several reasons.
Here is the list of requirements for the Google IAB testing.
Prerequisites:
Testing requirements:
P.S: Debugging with release certificate: https://stackoverflow.com/a/15754187/1321401 (Thnx @dipp for the link)
P.P.S: Wanted to make this list for a long time already.
Thnx @zlgdev for update
我的解决方案是，我需要在市场（作为草稿 APK）和测试中使用相同的密钥来签署 apk。因此，我总是必须在每次更新时导出签名的 APK，而不是仅仅运行应用程序，使用 apk 命令行命令将其卸载并重新安装在设备中。原则上，您也可以使用自己的密钥库作为调试密钥库，但它需要使用特定的硬编码密码和密钥名称。
My solution was that I needed to use the same key to sign apk in Market (as draft APK), and in test. So instead of just Run Application I always have to export signed APK with every update, uninstall and reinstall it in device using apk command-line commands. In principle you can use your own keystore as debug keystore also, but it requires using specific hardcoded passwords and names for keys.
如果您遇到此错误，我想我会分享一种可能的解决方案。我最初将我的 apk 草稿上传到谷歌，并启用了计费权限，因此我能够在应用程序中进行设置。后来我上传了另一个 apk，但 AndroidManifest 中缺少计费权限，这导致了错误。这看起来绝对是一个不可能的案例，但它发生在我身上，所以这是可能的。
编辑：沿着同样的折叠，如果您作为草稿提交给谷歌的版本未签名，也会发生错误。
Thought I'd share one more possible solution if you're getting this error. I originally uploaded to google a draft of my apk with the billing permission enabled, so I was able to set up in app purchasables. Later on I uploaded another apk without the billing permission missing from my AndroidManifest, which resulted in the error. Definitely seems like an unlikely case, but it happened for me so it's possible.
Edit: Along the same fold, if the version you have submitted as draft to google is unsigned, the error will also occur.
为了投入我的两分钱，我能够通过上传到 Beta 版本并使用新版本的应用程序在设置选项卡下创建一个具有测试访问权限的 Gmail 帐户来测试它......
我现在正在将其转移到生产环境。 ..
谢谢！
内森
To throw in my two cents, I was able to test it by uploading to the Beta version and creating a Gmail account with testing access under the settings tab with a new version of my app...
I'm now moving it to production...
Thanks!
Nathan
旧线程，但添加了我的经验...
我安装了一个版本代码 1 高于商店中版本的 apk。在我的 Nexus 7 上用 2 个不同的帐户玩过它并遇到了这个问题。因此，我从商店卸载并重新安装，以确保版本代码匹配。即使等了一夜，错误也没有清除。
结果我需要从与我的 Nexus 7 绑定的所有 3 个谷歌帐户中卸载。当我从 Nexus 7 上的所有三个帐户中明确卸载该应用程序然后从商店重新安装时，它恢复了。
Old thread, but adding my experience...
I installed an apk with a versionCode 1 higher than was in the store. Played it on 2 different accounts on my Nexus 7 and experienced this problem. So I uninstalled and reinstalled from the store to make sure the versionCode matched. Even waiting overnight the error didn't clear.
Turns out I needed to uninstall from all 3 google accounts I have tied to my Nexus 7. It recovered when I uninstalled the app explicitly from all three accounts on my nexus 7 then reinstalled from the store.