receipt-validation

问题 Once I get a receipt from client and validate it by apple server, then I got a transaction id of the new purchase (it's an auto-subscription purchase) in this receipt. After a few days , I get a new receipt from the same client and validate it , strange things happen : the transaction id of that old purchase changes. I compare the data of this purchase in the old receipt with the data in the new receipt , the only thing changes is the transaction_id field ，the original_transaction_id,

问题 Once I get a receipt from client and validate it by apple server, then I got a transaction id of the new purchase (it's an auto-subscription purchase) in this receipt. After a few days , I get a new receipt from the same client and validate it , strange things happen : the transaction id of that old purchase changes. I compare the data of this purchase in the old receipt with the data in the new receipt , the only thing changes is the transaction_id field ，the original_transaction_id,

问题 Once I get a receipt from client and validate it by apple server, then I got a transaction id of the new purchase (it's an auto-subscription purchase) in this receipt. After a few days , I get a new receipt from the same client and validate it , strange things happen : the transaction id of that old purchase changes. I compare the data of this purchase in the old receipt with the data in the new receipt , the only thing changes is the transaction_id field ，the original_transaction_id,

问题 I'm using Receigen (http://receigen.etiemble.com/) to do receipt validation for one of my MacOS apps. This has worked beautifully for several years, but something has changed. I haven't made an update to this app for a year or so and submitted a change but it was rejected because the receipt validation wasn't working. When I try to test the receipts locally, it pops up the App Store login, I enter my email+password, and then I get the "app is damaged" message. I used the Receigen Code

问题 I have been testing In App Purchases for iOS in a sample app. I need to figure out if I can call refreshReceipt API immediately at the launch to check user's eligibility for some trial period subscriptions etc. I have called refreshReceipt in AppDelegate's application:didFinishLaunching:options method but it asks me for AppStore credentials, basically the Sandbox user's password. I was not expecting this behaviour as read from Apple docs. Is it something that is happening because of the

问题 I have an app that I recently updated to work with in app purchases. The previous version (paid but with no in app purchases) was 1.0 and the current version is 1.1. As the in app purchase essentially unlocks all features (which were included in the paid version 1.0), I wanted a way for users that had originally downloaded version 1.0 to be upgraded if they pressed my restore purchases button. To do this, I first try to restore purchases and if the response to: - (void

问题 I have an app that I recently updated to work with in app purchases. The previous version (paid but with no in app purchases) was 1.0 and the current version is 1.1. As the in app purchase essentially unlocks all features (which were included in the paid version 1.0), I wanted a way for users that had originally downloaded version 1.0 to be upgraded if they pressed my restore purchases button. To do this, I first try to restore purchases and if the response to: - (void

问题 i've searched and can't find any way to create a delay of showing message: "Your purchase was successful" to wait until the validation receipt finished. I've tried to quote the line SKPaymentQueue.defaultQueue().finishTransaction(transaction as! SKPaymentTransaction) but the message still fires. func paymentQueue(queue: SKPaymentQueue, updatedTransactions transactions: [SKPaymentTransaction]) { print("Received Payment Transaction Response from Apple"); for transaction:AnyObject in

问题 I'm a bit confused with this. So following this approach I got json which contains bunch of decrypted fields. Among them original_purchase_date. What I need is to track if application was purchased before this new version becomes free and I think I need to use this field for that. But for some reason on sandbox environment it shows date "original_purchase_date" = "2013-08-01 07:00:00 Etc/GMT"; which is couple of years before application was made. So right now I'm not sure Why it shows that

问题 I'm a bit confused with this. So following this approach I got json which contains bunch of decrypted fields. Among them original_purchase_date. What I need is to track if application was purchased before this new version becomes free and I think I need to use this field for that. But for some reason on sandbox environment it shows date "original_purchase_date" = "2013-08-01 07:00:00 Etc/GMT"; which is couple of years before application was made. So right now I'm not sure Why it shows that