“restore purchases”

Sounds like Nonconsumable's behaviour purchase once restore as many times. Just double-check your product setup in AppStore Connect for Type Consumable

now im seeing it should work fine because of the corresponding apple id used to make the purchase, but i would need to have a restore function for people who delete the app

THANK YOU!func paymentQueue(queue: SKPaymentQueue, updatedTransactions transactions: [SKPaymentTransaction]) { for transaction in transactions { switch transaction.transactionState { case SKPaymentTransactionState.Purchased: print(Transaction Approved) print(Product Identifier: (transaction.payment.productIdentifier)) self.deliverProduct(transaction) SKPaymentQueue.defaultQueue().finishTransaction(transaction) case SKPaymentTransactionState.Failed: print(Transaction Failed) SKPaymentQueue.defaultQueue().finishTransaction(transaction) case SKPaymentTransactionState.Restored: print(Transaction Restored) SKPaymentQueue.defaultQueue().finishTransaction(transaction) case SKPaymentTransactionState.Deferred: print(Transaction Deferred) case SKPaymentTransactionState.Purchasing: print(Transaction Purchasing) } } }I wasn't doing the finishTransaction() call for .Restored - I only had it for .PurchasedDidn't realize that even though restore comes from SKPaymentQueue.defaultQueue().re

Can confirm I am also experiencing this. Same issue across:Different sandbox accountsDifferent devicesDifferent WiFiIPAs in which purchase used to work no longer workNewly created IPAs exhibit same issueHappening for both Consumables and NonConsumables.Note that restoring all nonconsumable purchases for a sandbox account works fine.

It is possible that the app was 'purchased' from the App Store under the Apple ID of user 1 (in the sandbox that would be determined at the time of installation through TestFlight or Xcode) and when you restore the receipt you choose to restore it under the Apple ID of user 2. Therefore, when the app is closed and reopened you might get the receipt in the account of user 1. So the question is - do you know who might have made the purchases that show up in the original receipt - could that be the TestFlight user?>Is there a way to completely remove the receipt for the sandbox environment so I could start from scratch?Sure - delete the app and reinstall it.

Does your app tell your server when it is doing a restoreComplrtedTransactions? I believe these are receipts received by a user’s second device after they purchase on the first and do a restore on the second. Is that possible. If so, what are you trying to verify?

The short answer to basing the restore process on the use of validating the appStoreReceipt is that it will fail in App Review. The issue here stems from the fact that in the sandbox, when the app is installed by Xcode, TestFlight or in App Review, there is never an appStoreReceipt until a purchase is made, or transactions are restored using the restoreCompletedTransactions method. If your app behaves as described, then when the reviewer presses the Restore button, the appStoreReceiptURL will be nil and the app will make use of the SKReceiptRefreshRequest. When the Authentication dialog is presented, the App Reviewer always cancels the request because it requires a password which the reviewer doesn't have. If the reviewer cannot verify that an in-app purchase can be restored, I'm told that the app will be rejected. If the app uses restoreCompletedTransactions, prior transactions will be restored.In the production environment, this is not normally an issue

That looks correct, if you can reproduce and provide a sysdiagnose, please file a Feedback assistant ticket. http://feedbackassistant.apple.com You also can consider reviewing our Proactive Restore best practice to minimize the need for a customer to need to manually restore their past transactions. https://developer.apple.com/videos/play/wwdc2022/110404/ Lastly if customers are reporting past purchases not being provided, you can also verify their purchases using the customers email receipt using our App Store Server API - https://developer.apple.com/documentation/appstoreserverapi/look_up_order_id

You can't remove it from the store because previous purchasers need to be able to restore it to their device.You can uncheck 'cleared for sale' and that will prevent anyone from accessing using any means other than restoreCompletedTransactions

A user just reported that same error message while attempting to restore an in-app purchase.MZCommerceInAppBuy.AppBuyInfoDataAccessFailure_messageOur app has had in-app purchases in place for 5 years; this type of error is new.

I added my info to FB11788741 (StoreKit 1 seems broken on WatchOS 9 & 9.1 - all purchase restores fail with StoreKit error 0) I sent previously.

When I hit option-click Restore iPhone, it tries to locate an old backup. I have a backup through iTunes (on the computer, not through iCloud), how would I go about the restore? I am restoring iPhone 5 backup and purchased an iPhone 6+ (I already disabled Find my iPhone and had the pop-up update as your described and am updated to iOS 8.4.1). My only suspicion is that I was on the latest developer update on my iPhone 5 (iOS 9)? Do I just need to update to iOS 9 in order to restore my iPhone or is there something else I'm missing here?