restore purchases

We're experiencing the same issue also since Monday morning: error 5002 while restoring purchases.

When you use StoreKit 2 with StoreView, there's normally no need for existing customers to manually restore purchases. You can choose to make the restore purchases button visible for rare cases where a customer doesn't have access to an in-app purchase product they believe they should have access to. I think the closest API to what you are requesting is currentEntitlementTask(for:priority:action:), which we also cover in the Meet StoreKit for SwiftUI session around the 16:40 timestamp. The API I shared makes it easy to add a dependency on the current entitlement to any SwiftUI view that depends on someone owning your in-app purchase. You can also check this in imperative code using an API like currentEntitlement on Product. In either case, the API should have accurate information as soon as you call it without requiring your customers to manually use a restore button. If a customer activates the restore purchases button in your store view, and a missing tr

> in response to tapping Restore purchase button, rather than at a random time when the app notices there is no receipt.Both procedures would be in response to tapping the Restore purchase button.It's 6 of one half a dozen of the other which you use - except for subscriptions where the receipt is better. Of course, that assumes you are verifying receipts. If you are not verifying receipts then just do the restoreCompletedTransactions.

I appreciate the feedback, but that's the part I don't understand. Since a refresh request requires the user to login, I'd rather have the login be in response to tapping Restore purchase button, rather than at a random time when the app notices there is no receipt.The chief scenario I am imagining is when a user restores a backup copy of the app from iTunes and has no receipt. In that case, it is perfectly appropriate to expect them to do restore purchase, don't you think?

Thanks for the reply!I'm a little confused your comment about the code having a restore function. Do you mean we should have coded something in the iPhone app to restore purchases?I've inherited this code base so I'm not entirely familiar with everything yet. We have a Rails backend that verifies the receipts with the App Store.The user sent in their receipt for a yearly subscription. There's no mention of a promo code. I can ask the user to sign out of the app and restore purchases and see if that does anything.

Is there an update on this issue? (I have tons of users which have non working renewals, and restoring purchase is not working for them.)

tried to restore purchase Are you calling restoreCompletedTransactions() to restore your purchases? If yes, this method doesn't return in the following situations: All transactions are unfinished. The user did not purchase anything that is restorable. You tried to restore items that are not restorable, such as a non-renewing subscription or a consumable product. Your app’s build version does not meet the guidelines for the CFBundleVersion key.

I've tested the application on a different machine. Again, the restoration process fails. I've tested an existing iOS application. It fails to restore purchases in the same manner.

Why did I have to come here to finally find the seemingly-unnecessary API to restore purchases that app review wants me to call? 😅

Implement proactive in-app purchase restore: continue providing a “Restore Purchases” button within your app. While not used often, it does give customers an opportunity to force an app to restore their Apple ID’s transactions in case of an issue or if the customer uses a different Apple ID.

We have tested inapp purchases on device with 9.2beta, on which we previously had problems, - now it is possible to make and restore purchases. Dowloading hosted content also doesn't break inapps.

Did you notice any more expired certs in production? I'm still seeing some once in a while. It seems that a restore purchases fixes it for some but not all.