in-app-purchase

问题 A question regarding in-app purchase auto-renewing subscriptions: I'm unclear how to handle the case where a user purchases multiple subscriptions of differing durations. It seems that Apple will recognize if the user has already purchased a given SKU (based on product-id) and prevent re-purchasing (my app gets a failed-transaction event in this case), but if I offer the same content using different product-ids having different durations, then the user can potentially purchase twice or more.

问题 A question regarding in-app purchase auto-renewing subscriptions: I'm unclear how to handle the case where a user purchases multiple subscriptions of differing durations. It seems that Apple will recognize if the user has already purchased a given SKU (based on product-id) and prevent re-purchasing (my app gets a failed-transaction event in this case), but if I offer the same content using different product-ids having different durations, then the user can potentially purchase twice or more.

问题 I Am trying to include in app purchase and i have successfully through in showing up SKUs available.Now I want to make a fake purchase.So I used appId = "android.test.purchased". For the first time it worked flawlessly, but from next it is throwing exception as below. Attempt to invoke virtual method 'android.content.IntentSender android.app.PendingIntent.getIntentSender()' on a null object reference Has anybody come across such situation? package com.inappbilling.poc; import java.util

问题 According to the Apple In App Purchase Programming Guide: The App Store creates a separate transaction each time it renews a subscription. When your application restores previous purchases, Store Kit delivers each transaction to your application. Let's imagine my app subscription is client-side-only (no server component). The simplest way to verify that subsequent renewals have been billed seems to be restoring previous purchases every month. However , this pops up the user's iTunes password

问题 I'm trying to use Unity's excellent new CrossPlatformValidator (Such as seen ... http://docs.unity3d.com/Manual/UnityIAPValidatingReceipts.html or https://docs.google.com/document/d/1dJzeoGPeUIUetvFCulsvRz1TwRNOcJzwTDVf23gk8Rg) But it can't be found! Naturally I am ... using UnityEngine; using UnityEngine.Purchasing; I also tried different stripping and .Net levels. Nothing. Anyone have a clue about this? The type or namespace name `CrossPlatformValidator' could not be found. Are you missing

问题 As many of us know, there's been a recent situation with Apple where hackers are able to get any In-App Purchase for free. Apple recently released this document describing how to patch it, but I'm a bit confused on step #4 and would appreciate any help. The first steps are to download their patch .h and .m, include it in your project, and link it against the Security framework. Okay, good, got it. Then Apple says: 4. Provide a base64 encoder, a base64 decoder, and the action to perform when

问题 I am implementing IAP in an iPhone app and am working in the sandbox environment. I have my code setup to process SKProducts returned by an SKProductsRequest to get pricing information. I would like to test retrieving price values in different locales (e.g. Euros or Yen) to test my formatting code. How can I get SKProductsRequest to return different locales? 回答1: Answering my own question here. You can test this by creating IAP test users in different stores on iTunes connect. 回答2: We get the

问题 My Project is in Plyatore beta. The project contains subscription as monthly and yearly. So I added a Sandbox settings with 8 Gmail id's for testing the subscription.Then I configure each Gmail id in device account settings, only two Id is getting purchase dialog. Remaining 6 Gmail id's are getting one error message as "the item you requested is not available for purchase". Is anyone has the same problem occurred, or anyone has the solution please help me to fix the issue. The mail id is

问题 Testing In-App Billing Version 3 has been made unpredictable by the fact that the Google Play app buffers data from the Google Play servers, and the buffering process is not well-documented. In particular, if a purchase is made on one of a user's devices, it may not be immediately visible on a different device owned by that same user. Recommended practice is for an app to check the inventory of all purchased products when it is started. But sometimes this check uses buffered data that is

问题 Case: Our iOS app offers selling of custom made recipe packages that would be created for each user specifically. For example - user buys package of recipes, but for each user this package would be created individually, based on users preferences and needs, by someone from the app team. This package should be created in 5 days for example. If app team fails to create this package and deliver to end user in 5 days, automatic refund should be triggered and end user should receive money back