“restore purchases”

I filed a bug report as well. I strongly feel non-renewing in-app purchases belong in the receipt. However, if they want to stop doing this, we will need the purchases restored in the receipt temporarily to move them to a separate server. Otherwise our users' purchases are gone forever, and they will be forced to ask for a refund from Apple.

HI :1) Abandoned BatchWe found that while you have submitted In App Purchase products for your app, the In App Purchase functionality is not present in your binary.this assume that you don't have an article in ITC for IAP ? you can't use IAP if you don't create articles on ITC2) Missing restore mechanismYou have to implement a restore Mechanism, but if i refer to 1) you don't even have IAP configured for your app...??i just assuming, i don't know your project... ^^

Yes, I suspected it, so I did the integration in the (I suppose) right way. Here following you'll find the code, but this didn't solve the problem...func paymentQueue(queue: SKPaymentQueue, updatedTransactions transactions: [SKPaymentTransaction]) { print(Received Payment Transaction Response from Apple); for transaction:AnyObject in transactions { if let trans:SKPaymentTransaction = transaction as? SKPaymentTransaction{ switch trans.transactionState { case .Purchased: print(Product Purchased); queue.finishTransaction(transaction as! SKPaymentTransaction) defaults.setBool(true , forKey: admob_footer_purchased) break; case .Failed: print(Purchased Failed); queue.finishTransaction(transaction as! SKPaymentTransaction) break; case .Restored: print(Already Purchased Restored); queue.finishTransaction(transaction as! SKPaymentTransaction) default: print(Default); break; } } } }Thank you!

Pretty sure it's recommended you check for the latest receipt when the app opens, but Restore is a way to manually make that happen. The same thing is true with Non-consumables of course where you can silently check for a previous purchase. And again Restore is like the peace-of-mind button for the consumer to be able to restore at will if your initial check failed for some reason.

You might have to label it Restore / Review Purchases so your reviewer can check off their list that you've included that. Maybe someone else can chime in on whether or not your app actually has to include the Restore Transactions code, if you've coded something alternate to that.

Actually it is not. When the user wishes to restore their previous purchases all they do is cause the code to execute a restoreCompletedTransactions and all of their non-consumable IAPs and autorenewable subscriptions are transmitted to them as transactions in a call to updatedTransactions. No need to specify specific products to restore.

Unfortunately on macOS sandbox environment the receipt is the first thing that has to be there to be able to launch and start the app.Every time the app starts without a receipt it exits with code 173 and that triggers a Mac App Store login to download the receipt again.I can save a copy of the app with only the original receipt in it, proceed to purchase on another copy of the app and then try the restore on the first copy that has the receipt without the purchased product id inside.The result is the same, the restore passes with no problem but the receipt is not updated with the product id of the purchased product.

If I don't call finishTransaction on each transaction at the time of purchase, where else do I do it? Every example I've seen of how to setup IAP has a switch statement which finishes the transaction in each case of purchased, restored, and failed.

I would be curious how In App Purchases play into this. I think the tv forces persistent storage using the Cloud, but most apps have restore buttons.

The credits are consumables. You may need to create some way in which the purchased content is restoreable to other devices owned by the same user. Even though restoring is not required for consumables, the content that the credits purchase is not really a consumable and should be restoreable.Your app needs to follow 3.1.1 - if you are unlocking code distributed by Apple in the app itself you must use IAP. You may be able to operate under 3.1.3 and not use IAP.

You test to see if there is a receipt and if there is a receipt you determine what has been purchased. If there is no receipt you wait. If the user requests something that requires an IAP then you tell the user they must first restore their purchases. The same is true for a subscription that might be expired.

Purchases are tied to one ID (or family if set up). The user will need to use the same AppleID for a restore feature to work.