“restore purchases”

I'm seeing the same: 100% packet loss when pinging sandbox.itunes.apple.com and yet the developer system status shows everything all green. Retrieving products seems fine, but doing anything substantive—like purchasing products or restoring purchases—is very hit & miss. Mostly miss.

I'm using an older billing library called SwiftyStoreKit, and over the past couple of weeks I've received reports from two users that restore purchases is failing. I'm currently working on a fix, and plan to migrate the restore functionality to the newer version of StoreKit.

>I guess Apple's documentation is not accurate at this point?I believe elsewhere Apple tells developers not to call SKReceiptRefreshRequest without the user knowing that they will be asked to log in to the App Store.> So I'd still need some kind of prompt at startup to allow previous customers to trigger the refresh... Somewhere you tell users about how they can upgrade the app to include the IAP features. Just add to that something like 'If you have purchased an early version of the app or if you have purchased the IAP on another device that you own, then tap 'restore purchases' below'or...On first launch of the app (you only need to do this once), if there is no receipt, show an alert message like 'If you purchased an earlier version of this app you may be entitled to the fancy features - tap Restore Purchases below'

Thanks for your ansewr CartoonSmart.com,Yes what you described is exactly what happened, and if it happens the same in production environnement there is really a issue for the user experience.If someone have a solution about how to restore purchase in a iMessage extension app it would be helpfull.

>My problem is that Apple Id in phone is still same. So when different user logged in he could restore purchases even that he didn't buy them.A user can only restore purchases that they purchased through their iTunes Account. They must know their password for their account. The system requires a password for any restoreCompletedTransactions request or a receipt refresh. If two users share an iTunes account then they share all of their purchases. There is no way to distinquish them. If two people share their phone then they both get to use the apps and IAPs on that phone. Very few people share their phone. iPad sharing is a different matter.Regarding 'restore'...an autorenewable subscription can do a restore through iTunes and the comments above apply. A non-renewing subscription cannot. You must implement your own restore function for a non-renewing subscription. Because of my concerns, similar to yours, that a company might purchase o

You are correct with your translation.The reason for this error message is, that the user(s) was signed in with a different Apple ID at the time of downloading your App via the Appstore, from the time at which they tried to restore their subscription.The user must uninstall the app and then make sure he/she is signed into his itunes account with which he purchased a subscription within your app. Redownload the app, restore purchases -> No more errors.

Thanks for writing it again after your draft disappeared. The existence of this forum software is one of the mysteries of the universe to me.Point #2 seems a bit tricky because a user could be legitamately restoring purchases or installing on a second device.

We were able to pass review after I replied that this issue comes from appstored, added part of system log (with a failure line from appstored). App was released and it was working fine. Yes, this issue comes out for users who never had any purchases in sandbox. Workaround can be not restoring purchases automatically which requires persisting purchases... But it's not goos. We should not break functionality like auto-restore in production just to pass review on sandbox =(

I only program in Objective C so I can't identify all of your errors. You have identified a specific problem. You asked: How can I recognize that the user had already bought one purchase over another?In the method which Swift calls func paymentQueue(_ queue: SKPaymentQueue, updatedTransactions transactions: [SKPaymentTransaction]) you have case .purchased: where you handle a new purchase. In that method you are able to tell which product the user purchased. In that same method you can add a case .restored that can handle a restored transaction the same as a purchased transaction. You do not want to handle the restored purchase in the method that Swift calls func paymentQueueRestoreCompletedTransactionsFinished(_ queue: SKPaymentQueue)

I've also noticed that if you cancel a download, you then get a download notification that correctly reports the state as cancelled but also reports the progress as 1.0 - I would not have expected that. You then can't use that same transaction to re-start a download, so the only way I can see to unblock that error state is to restore purchases. This seems to be specific to iOS 14.1 as best I can tell. I'm able to cancel and re-start downloads on iOS 13.7 just fine - no need to restore purchases and you can (re-)use the same transaction. Whether that's the correct thing to do or not, I'm happy to be educated on that point. I see this behaviour in the sandbox and production environments.

We are seeing the same issue as well. The sandbox very slow to return product prices, make purchases, and restore purchases. It also repeatedly asks us to verify our Apple ID in the Settings app, even though it is just a sandbox user. We have been working with IAPs for years and have never run into these kinds of issues.

> I work the same way.Remember that none of the apps in the store are any promise that your app will be accepted. No one here can say what App Review will or won't accept/review.As you said before, I know that Apple ask that applicaiton with in-app purchase must have a Restore purchase - best to use that as your goal, I think.

Can you not treat the two things (purchase, and account) separately? The user can delete the account and their data if they want to (therefore fulfilling the requirements for account deletion), but there's still a purchase that you can access via Restore Purchases, so if they happen to create a new account in future (before the membership expires), then they can still re-attach that purchase/membership to their new account?

I am having the similar problem. Restore purchase with sandbox account fails in TestFlight beta app on iOS 15.1.1 On ios14.8 it's fine. On ios15.1.1, when I use a sandbox account for in-app purchase on a beta app installed from TestFlight, the purchase succeeds, but restore fails. When I try to restore it, every time I get a dialog to enter apple id and password, I enter the sandbox account I purchased, but it fails with 'unknown error'. I checked the device logs and found the same situation as written by gmarcus. Is this a specification of IOS15 or a bug? Have you found a solution to this problem? Any information or suggestions? Thank you.