如果你发布的版本与你在手机上测试的版本不一样，也会发生同样的情况。

例如，上传的版本是android:versionCode="1"，而你在你的手机上测试的版本是android:versionCode="2"

在旧的开发控制台:

设置->帐户详细信息->许可证测试-> Gmail具有测试访问权限的帐户，并在这里键入您的帐户

在新的开发控制台:

输入您的Gmail帐户，点击“Enter”，然后点击“Save”。

如果所有的设置都是OK的，你仍然得到错误的应用程序的这个版本没有配置通过谷歌播放计费。查看帮助中心获取更多信息。

在Play Store中编辑您的应用内产品定价或停用并激活应用内产品。这将解决问题。

如果你想集成另一个没有发布的应用程序，但与已部署的应用程序具有相同的id、版本代码和版本名，那么不要忘记编辑appname。iml文件版本在扑动应用程序，因为我坚持它与相同的错误。

啊，经过几个小时的尝试，终于找到了解决方案。

谷歌需要一段时间来处理应用程序并将它们更新到服务器，对我来说大约需要半天。因此，在谷歌Play上以草稿形式保存apk后，你必须等待几个小时，应用内产品才能正常响应，并允许定期购买。 导出并签署APK。未签名的APK试图进行购买将得到错误。

与SO和其他网站上的许多答案和评论相反，你不需要使用从谷歌Play下载到测试设备上的产品alpha/beta版本进行初步测试(alpha/beta发布过程通常要花半天时间)。你也不需要从你的开发工作室加载和重新加载一个签名的apk到你的测试设备。

You CAN debug preliminary Google Play in app billing services using the debug app as loaded from your developer studio directly to your test device via ADB. If you are experiencing errors that prevent this, likely you have done something wrong in your code. Pay especially close attention to the CASE of your SKU's (product ids) and their format (for example, if you load your APK as com.mydomain.my_product_id, be sure your try to purchase it this way - providing the same case and domain). Also, pay especially close attention to your itemType - this should be either "inapp" or "subs" for managed/unmanaged in app purchases or subscriptions, respectively.

As suggested by Chirag Patel, provided you have your billing code properly established, perform all testing using the android.test.purchased Sku (product ID) during your preliminary tests. Check for this ID throughout your billing operations to pass it through signature, token and payload checks, since this data is not provided by the Google test system. Additionally, give one of your test products this ID to test its purchase, unlock/load and presentation all the way through your schema. To CLEAR the purchase, simply consume it, passing the same Sku AND a token string formatted this way - no other fields are relevant :

    "inapp:"+appContext.getAppContext().getPackageName()+":android.test.purchased";

Once you have completed this phase of testing, move to semi-live testing with your alpha/beta product. Create a Google group (essentially a mailing list), add your test users emails to it, and add/invite this group to test your device in this phase (performed at the "APK" portion of your app's Google developer listing). Purchases will be simulated but not actually charged - however to clear and re-test the purchases, Google indicates that you must refund them from your Google wallet. THIS is the only phase of testing that requires the time-consuming process of using alpha/beta loads and test users.