“restore purchases”

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.

>I have a free application where you need to create an account or use facebook. A one time in-app purchase allow to unlock the app (remove ads, additional features...). Classic.Actually not classic. An app that does nothing if the user does not log into some remote system may be violating a guideline of requiring personal information in order to function. Apps like that have been rejected and developers have compalined but BigAppCompany (e.g. Uber) got to do that whay can't I? It is best to function at some low level without a log in and provide the 'option' of loging in and an enhanced experience to those who log in. And to answer your question - app review may well have a problem with no 'restore' option. They might argue that the user reinstalling the app may want to do the restore function prior independent of a Facebook log-in. And that makes some sense if they purchased a new device and are going through all their apps doing their restoring - they have no

If a user purchases a non-consumable item that has already been purchased again It's not possible to re-purchase a non-consumable. What will happen is that they will try to re-purchase it, and at some point quite late in the process iOS will pop up an alert saying You've already purchased this. At that point, I think your app will get a StoreKit transaction for the purchase. I am thinking of guiding them to purchase again Yes, this is safe advice if they claim that restore doesn't work. The danger is that they have mis-remembered what they have previously purchased, or that they are using a new Apple ID. In that case, they will be charged.

I am having a similar problem (on iOS 11). I have redeemed a promo code for a non-consumable IAP. That seems to work fine. However when I go to restore the purchase, my paymentQueue:updatedTransactions:methos is never called and thus the code doesn't know the purchase has been restored. My paymentQueueRestoreCompletedTransactionsFinished: method is called so I believe I have my observer set up correctly.This used to work in a different version of the app so I'm mystified why this is no longer working. However, I'm now compiling with the latest Xcode and libraries so maybe something has changed there.I've implemented all the failure notification methods, so I don't think it is failing.Some people seem to imply that you can't restore IPA purchases made with a promo code. That seems unlikely. Anyone know if it's really true?Any thoughts would be appreciated

The first word translates to “re-grant” which I assume is “restore”. The App Store believes the user never purchased the app.

Please refer to the documentation available on accessing transaction history and current entitlements for your app. Additionally, if you’re interested in learning more, check out our Implement proactive in-app purchase restore video. This video demonstrates how you can proactively restore someone’s in-app purchases access when they first open your app, providing instant access to existing subscriptions using StoreKit or StoreKit 2. It also covers best practices for both client and server implementations.

Regarding the Restore, there is a Restore button right underneath the GET button. But even if they don't use the Restore button, we automatically test for a Restore when a use clicks the GET button just to be on the safe side. So restore should be covered.As far as renewal is concerned, a user shouldn't have to think about it a bit. A user signs up, and the App should work until my servers receive a cancel event from Apple's servers, followed by polling to test for expiration confirmation. Once polling confirms expiration, the database sets their active field to false. Once that happens, the app will let the user know that they need to purchase a new subscription to continue using the app and to login to their account to make the purchase.To summarize, the app is not responsible at all for renewal and cancellation events at all, the server is. The app only does Purchase or Restore, and the server handles the status of the subscription aft

But this is again a workaround and a restriction I do not want to enforce. The user's purchase is tied to their iTunes & App Store account, they might even not be logged in to iCloud theoretically when purchasing this item. Apple provides restoration of purchases based on the iTunes account. Attempting to restore them using same iCloud but different iTunes account does not work and I would not want to add custom logic for something that Apple claims to provide out of the box. As I answered to KMT, I want the receipt to be the whole truth for my application. And everything works perfectly if I restore on a new device or reinstall on same device. My only problem is changing iTunes user with the app still installed. How can a different iTunes user access the previous user's receipt? Is this considered normal? Is this only a sandbox issue that I am experiencing?

Even if it is obvious and just for the record I commented out the restore piece of the code and ofc no message and I could actually purchase in Sandbox environment.

You must provide a method whereby a user with a new device can obtain the subscription, purchased in a different device, into that new device - that's called 'restore'. The link you provided indicates that non-renewing subscriptions require the developer to create a 'restore' function but that autorenewable subscriptions support restoreCompletedTransactions. You can also refresh the receipt and obtain the user's autorenewable subscription purchases. But only by exectuting restoreCompletedTransactions can you assure that future autorenewable renewals generate a call to completedTransactions in that new device.

No, that was not the mistake.I have received the following LOG:1.// viewDidLoad [[SKPaymentQueue defaultQueue] transactions].count>> returned 0.2.// requestDidFinish: SKProductsRequest>> The product information has been loaded.3.// restore SKReceiptRefreshRequest *produkt = [[SKReceiptRefreshRequest alloc] init]; [produkt setDelegate:self]; [produkt start];>> Restore button was pressed.4.// requestDidFinish: SKReceiptRefreshRequest>> Got a new receipt...and call:[[SKPaymentQueue defaultQueue] restoreCompletedTransactions];>> paymentQueue:updatedTransactions: was not called!!5.// paymentQueueRestoreCompletedTransactionsFinished: queue.description >> <SKPaymentQueue: 0x1c10029f0> queue.debugDescription >> <SKPaymentQueue: 0x1c10029f0> queue.transactions.description >> () queue.transactions.debugDescription <__NSArray0 0x1c401c060>()>> queue.transactions is emptyPlease further ideas. The user has purchased the item

you need to do two things: ------1) create a system that allows a user to restore their purchase to other devices owned by the same user -----2) inform app review that you are using a consumable IAP to handle the multiple products but the user gets a restore able IAP through your mechanism in #1

You'd probably better move this post to the IAP section of the forum.I read in doc :When you create a new product to be sold in your store, you choose whether that product can be restored or not. See the In-App Purchase Programming Guide for more information.Have you checked you chose can be restored ?