你需要用你的实际证书签署APK。然后将其安装到测试设备上。然后您可以测试InAppBilling。如果您正在通过eclipse直接运行到设备(在调试模式下)来测试应用程序，那么您将得到这个错误。

如果你使用android.test. bought作为SKU，它会一直工作，但是在你的最终响应中不会有developerPayload。

如果你使用的是你自己的应用项目草稿，你可以一直测试，但你会被收费，所以之后你必须自己退款。

您不能使用用于谷歌游戏开发控制台的相同gmail帐户购买物品。

最近谷歌对他们的系统进行了更改，因为你已经上传了至少一个APK到你的控制台，你可以用你的应用程序测试你的应用内请求，使用任何版本代码/号码。

交叉参考LINK

配置gradle为调试版本签名。

android {
    ...
    defaultConfig { ... }
    signingConfigs {
        release {
            storeFile file("my-release-key.jks")
            storePassword "password"
            keyAlias "my-alias"
            keyPassword "password"
        }
    }
    buildTypes {
        debug {
            signingConfig signingConfigs.release
            ...
        }
    }
}

在我的情况下，由于安装的apk和上传到市场的apk的签名不同，我看到了相同的消息。

当你在上传apk后添加了应用内购买，但你还没有在play store中发布应用(alpha, beta和产品)时，也会出现这个问题。

这基本上意味着，在你将apk发布到Play商店后(alpha, beta和成品)，你必须添加应用内购买。否则你将无法购买或查询应用内购买。

我也遇到了同样的问题，在我读到DZDomi的帖子之前，问题没有解决。突然发现在谷歌开发人员控制台中有一个设置需要启用。在“In app purchases”部分，你的产品有一行，最右边是它的状态。它应该是活跃的!

与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.