这里是openkava 的blog,关注程序开发的一切技术。 ZZ 表示转载的文章,如涉及版权,请和我联系删除。 在这里你可以看到关于以下技术的文章: 移动开发技术,ANDROID ,IOS,WINDOWS PHONE平台开发,企业ERP开发,动态脚本PYTHON ,OPENGL ES 3D技术,游戏开发技术,HTML5 ,JAVASCRIPT ,MYSQL,AMAZON EC2 ,GOOGLE GAE ,GOOGLE CLOUD SQL 等 。 本站发展历程: 2010年,正式把所有的blog移到这里,租用godaddy的空间,记录生活和工作上的一些心得。 下面是关于我的个人介绍,写在这里权当凑字数啦。 职业:软件开发,开发经验6年,管理经验3年; 工作上使用的技术:C#, SQL SERVER 个人使用的技术:PYTHON,PHP, CSS, JAVA ,ANDROID ,object-c 等等 联系我请发邮件:<a href=""><img class="alignnone size-full wp-image-96" title="邮箱" src="" alt="" width="174" height="24" /></a>

Key Points of In-App Purchasing Technology for Android

1 Currently using version 3.0, supporting managed and subscription.

2 Managed products support consumption, can be repurchased after consumption, and can also be used for one-time purchases. Handle the logic in your own code. Subscriptions are used for monthly or yearly subscriptions.

3 First, upload the signed APK to Google, create managed products and subscriptions, set prices, descriptions, and other information.

4 In the publishing console, set up test accounts. The test account cannot be the same as the published account, otherwise it cannot be purchased.

5 Obtain the public key of this APK from the APK publishing console and paste it into in the APK.

6 Rebuild and upload the signed APK to the publishing console, and run the APK that has been signed with the same publishing certificate to test successfully. Otherwise, an error will occur: "this version of the application is not enabled for in-app billing."

7 Security recommendation: Do not display your public key in plaintext in the APK. At least encrypt it or obtain it from your server. Use payload to verify the responses during the purchase process to avoid man-in-the-middle attacks.

Ownership of this post data is guaranteed by blockchain and smart contracts to the creator alone.