Android的应用程序内购买V3的2.3签名版本只有失败 [英] Android in-app purchase v3 fails only with signed build on 2.3

查看:298
本文介绍了Android的应用程序内购买V3的2.3签名版本只有失败的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我们使用新的谷歌IAB V3 API,它已经非常可靠,但一个案例失败:它不与2.3.4(一Droid X的)运行的签名版本工作

We use the new Google IAB v3 API, it has been very reliable but one case fails: it does not work with a signed build running on 2.3.4 (a Droid X).

症状 IInAppBillingService.isBillingSupported()返回3,这意味着 BILLING_RESPONSE_RESULT_BILLING_UNAVAILABLE

Symptom is IInAppBillingService.isBillingSupported() returns 3 which means BILLING_RESPONSE_RESULT_BILLING_UNAVAILABLE.

我很为难,因为所有这些情况下工作:

- 2.3.4与调试版本:OK

- 4.2.1调试或签名版本,有/无ProGuard的:确定

I'm stumped because all these cases work:
- 2.3.4 with debug build: OK
- 4.2.1 with debug OR signed build, with/without proguard: OK

尽管它使用ProGuard制作4.2我想如果这是一个模糊的问题,所以试图保持类 com.android.vending.billing.IInAppBillingService ,则完全变成关闭ProGuard的。没有变化。

Even though it worked with proguard on 4.2 I wondered if it was an obfuscation problem, so tried keep class com.android.vending.billing.IInAppBillingService, then completely turned off proguard. No change.

所以,这似乎是一些关于签署发行,只有在2.3。任何想法?

So it seems to be something about the signed release and only on 2.3. Any ideas?

推荐答案

你有没有APK上传到谷歌Play开发者控制台?你需要的时候要首先开始测试IAB要做到这一点,每一次你碰到你的版本code。

Did you upload an apk to the Google Play Developer Console? You need to do this when you want to first start testing IAB, and every time you bump your version code.

这篇关于Android的应用程序内购买V3的2.3签名版本只有失败的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆