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

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

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

这里没有提到的另一个原因是，您需要在真正的设备上进行测试。 随着模拟器变得越来越好，这是一个很容易犯的错误。

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

这个错误可能是由几个原因引起的。

以下是谷歌IAB测试的要求列表。

先决条件:

AndroidManifest must include "com.android.vending.BILLING" permission. APK is built in release mode. APK is signed with the release certificate(s). (Important: with "App Signing by Google Play" it only works if you download directly from GooglePlayStore!) APK is uploaded to alpha/beta distribution channel (previously - as a draft) to the developer console at least once. (takes some time ~2h-24h). IAB products are published and their status set to active. Test account(s) is added in developer console.

测试要求:

测试APK的versionCode与上传到开发人员控制台的版本相同。 测试APK使用与上传到dev.console的证书相同的证书进行签名。 测试帐户(不是开发人员)-是设备上的主要帐户。(根据@MinosL的评论，主账号可能不需要) 测试帐户被选择为测试人员，并与有效的支付方式相链接。(@Kyone)

p.s.:发布证书调试:https://stackoverflow.com/a/15754187/1321401(链接为Thnx @dipp)

p.p.s.:很久以前就想列这个清单了。

@zlgdev， @Kyone， @MinosL更新

2021年结论

对于所有关心调试的人，您可以在调试模式下运行、调试和测试代码

下面是你如何测试这个过程:

(当然，这取决于您已经添加并激活了您的产品，并且您的代码已经准备好与这些产品集成)

将com.android. selling . billing添加到清单中 上传签名apk到内部测试 添加许可证测试员(播放控制台->设置->许可证测试)-如果你在你的设备上使用多个帐户，你不确定使用哪一个，只需将它们都添加为测试员。 像往常一样，从Android Studio运行应用程序(*应用程序应该具有与您刚刚上载到内部测试的应用程序相同的版本代码)

我做了上面的事情，它工作得很好。