“restore purchases”

Note that providing a Restore Purchases button is part of the App Review guidelines and even if rarely to never needed, it's important to have as there are cases the app can't always account for: customer signed in with the wrong App Store Apple ID (possible with shared devices, kids, etc.) or the customer is using the wrong in-app account with your app. But great to hear your app doesn't think its even needed, hopefully it has a robust implementation of the Proactive Restore best practice.

SKReceiptRefreshRequest does require a recent authentication and is nearly identical to restoreCompletedTransactions as that also requires authentication. Receipt only vs receipt + transactions. From your note it appears that is only called IF no app receipt was found, that is perfect. This means SKReceiptRefreshRequest will rarely be called as app installed via the App Store should always be present. So that prompt can happen in production but should be only in rare instances. If SKReceiptRefreshRequest is going to be called, it should only be called once. If the user attempts a purchase or restore purchases, a new receipt will be provided.

Hello,I think i got the same issue with my iMessage app extension.When i use the method :SKPaymentQueue.default().restoreCompletedTransactions()to restore transactions i got an error message telling me there is no information about in-app purchases - Sandbox environnement - 21105.This is probably linked with the receipt created by :let _receiptRequest = SKReceiptRefreshRequest() _receiptRequest.start()The SKReceiptRefreshRequest() never works, i can't have a receipt from apple with it.So, when i want to test the in-app purchases in sandbox environnement, i need to purchase one of the in-app purchases of the iMessage Extension. Purchase an in-app is the only way that worked to get a receipt. And if i delete the app and download it again i need to purchase each time one in-app to restore the purchases.I tested this basic method in sandbox environnement in my developpment device and in testflight environnement. Each time same result, to crea

Restore purchases should meet that criteria but there is no reason a customer ever needs to use that mechanism. Upon app launch your app can use app receipts or original_transaction_ID with our Server API's or use StoreKit2 to get the current status of the signed in user (App Store Apple ID) - from there your app should know if user is new, active, billing retry, grace period or expired.

@PBKThe updatedTransactions has been called correctly and the app called finishTransaction. The problem is that the receipt in the bundle should be updated, but it is NOT be updated.- Restoring Purchases: All the historic transactions be triggered in the updatedTransactions method, but the receipt in bundle did not be updated - But refreshing receipt does get the receipt in bundble be changed. I tracked the change of the receipt using code and manually checked the receipt file size in the bundle. Thanks

The Apple reviewer catched this error, we tested multiple times on our end, but were unable to reproduce. Today we got stable reproduction on one of our test devices, system log states: Error restoring purchases for tech.escape-team.f2c: Error Domain=AMSErrorDomain Code=305 Server Error...AMSServerAllowed=false, AMSServerErrorCode=3539... And user sees 21105 error. I think we need someone from Review Team here))

I’m pretty sure you will get the IAPs in the local receipt on a second device. There may be some odd corner-cases where you don’t, so do have a “restore purchases” button. I also watched that video. It wasn’t very helpful. They didn’t say anything about local receipt validation, when it would clearly be simpler than implementing server infrastructure in many cases. The paranoid half of my brain thinks this is a message to us that that functionality is going away soon.

Thanks for the reply.The pro version IAP purchase happens on the iOS app, but the functionality is for the Apple WAtch. Currently i use updateContext to send the information over to the Apple WAtch (by telling the Apple Watch to set the NSUserDefault to true. This works but dosnt account for a few scenarios. For example if the user deletes the Apple Watch app his Apple Watch NSUserDefaults get deleted with it. So when he reinstalls the app, I can imagine that he would need to restore purchase on iOS to cause the iOS app to resend the context and update the Apple Watch NSUserDefault key.

A local restoring of purchases does not trigger new or resend old server notifications. There a few things to cover here: A one time purchase like a consumable will always have the same OTID (original transaction ID), so that is your persistent identifier to represent a unique purchase. Additionally with StoreKit2 a new transaction ID is not created, same one is returned. You can retrieve a history of received server notifications a few different ways, recommend learning more about the App Store Server API notification history endpoint. You can retrieve a customers purchase history server side, you can retrieve a complete notification history for a customer using our App Store Server API Transaction history endpoint. Recommend looking into implementing the 'Proactive restore' best practice in your app so customers have access to their purchase without the extra step of doing a manual 'restore purchases' and re-authenticating. Upon app lau

As I understand it, if a user installs your app on a new device and hits your purchase button instead of restore purchases, there is a chance they would be double-billed if you have separate subscription groups for the same product. This would result in a terrible customer experience, to say the least. From Apple: creating a single group is the best practice for most apps as it prevents people from accidentally purchasing multiple subscriptions. You can create a subscription offer in App Store Connect to attract legacy users for renewals. See: https://developer.apple.com/help/app-store-connect/manage-subscriptions/set-up-promotional-offers-for-auto-renewable-subscriptions/