“restore purchases”

It is essential because there are a massive amount of users out there trying to purchase IAPs with invalid receipts. So this is not a theoretical issue, it is a real problem. For example **** broken devices are often already modified to automatically send a, let's call it a recycled iTunes receipt. In practice, many users of **** broken devices are not even aware that their devices are doing this by default. So even when they try to restore IAPs that they really bought before, their device would often use a bogus receipt instead by default.Also this is not solely about piracy, you are talking about subscriptions. And when you decode a receipt it also contains the information for which time frame the user purchased the subscription, and also whether the subscription has already been terminated by the user via Apple's iTunes support (think about restoring purchases for instance).And no, these issues are not soley limited to **** broken devices. There are also tools out there

rich, 43462062 is the most recent one. The original report's incident tracking number is 34278255. Delighted to see that 43462062 has been reopened. The problem occurs with every user, to the best of my knowledge. Once someone gets a new device and needs to restore purchases, there seems no chance it will work. Signing in and out, rebooting, resetting, reinstalling... gone through all that with many customers. One hint I found is that the bug may come from the transition to Swift. My app is still Objective-C only. This Githup repository exhibits a similar bug that one developer claims could be solved by transitioning to Swift 3: https://github.com/bizz84/SwiftyStoreKit/issues/175Yes, Receipt Validation via RMStore + OpenSSL is probably a solution to restore purchases. However, the use of cryptography, especially OpenSSL, comes with excessive risk exposure to hefty fines and penalties, as Apple warns us resource-constrained developers in iTunes Connect. As a bootstrapped one-man operation I l

The Finder is presenting this message after a macOS StoreKit app calls exit (173) a second time. The macOS StoreKit app is being run in the sandbox. The app on launch detects that the appStoreReceiptURL is nil and calls exit (173). The Finder detects this exit result and issue a request to the App Store to write a receipt to the app. This causes the app to present an authentication dialog in which you enter the test user account and password. Normally, the appStoreReceipt is refreshed in the app, but not in this failure case - such that the Finder presents the alert to the effect that the app is damaged. For the longest time it was recommended that on launch, the macOS StoreKit app check for the presence of the appStoreReceipt. If not present the app calls exist (173). This is no longer recommended as it rises the Authentication dialog which can be confusing to a user. Instead the advise now is to have the app continue along with the assumption that the user has no access to first time in-app purchase

Roger,It's difficult to debug an issue given only a user level description of the problem. However, I can make some guesses. You indicated thatWith appleID-A i am on a iPad and buy the in-app purchase 'full-version'. Done, the app unlocks the full version as expected. With the same appleID-A I am also on an iPhone. I press the restore purchases but does not workThe likely reason why this happens is that the finishTransaction call was not made to complete the transaction in the iPad purchase. If the finishTransaction call is not made, the transaction remains incomplete and will not be restored when the restoreCompletedTransaction call is made. Another question - on the iPhone, was appleID-A defined as the iTunes/App Store user setting when the restoreCompletedTransaction call was made, or did you enter the id. My reason for asking is that if the addTransactionObserver call was initiated, it should have found the incompleteTransaction and processed it. The observer can only p

You can handle 'restore' any way you want but you must provide a method whereby a user can recover their purchases on a new device that they purchase or on their current device after they delete (or restore from backup) any device that has your app.The normal way of restoring is to implement restoreCompletedTransactions and handle the restore exactly the same way you handled the original purchase except with a state 'restored' rather than 'purchased'.

If a purchase is available to restore then StoreKit calls updatedTransactions with a case of .restored. Whether or not there is a purchase to restore StoreKit calls paymentQueueRestoreCompletedTransactionsFinished to signal it is completed.Move your code that grants the purchase from paymentQueueRestoreCompletedTransactionsFinished to updatedTransactions.

Meanwhile I had to add this workaround for broken product purchase/restore on the watch: do the purchase or restore on the iPhone that syncs up the purchases to iCloud and later on the restore on the watch also fetches the purchases from the iCloud and uses those I cannot migrate to StoreKit 2, as I have WatchOS 7 and iOS 14 as a baseline.

Hi,Thanks, I think we are closing on to a solution. Some related clarifcations:So if I store the purchases in the localStorage in one device with iCloud enabled on two or more devices, the purchases will reflect on all the devices, right?In case the user reinstalls the app on one or more devices the purchase data (NRS or cosumable) will be lost if the person has not logged in earlier to copy the rights, as our server will not have details of the purchase (could this happen if the user after a NRS or consumable purchase, immediately does an app reinstall?). For example a user has 2 devices A and B and has bought one Pass which got copied to both devices through localStorage and iCloud. Now the user does a reinstall on device B. So device A has a record of Pass purchase, and device B has no Passes after reinstall. So how will the sync happen between the 2 devices, will contents of A be copied to B automatically after reinstall? If 2 is an issue will it be sa

Seeking for the same infos, and one more :My two apps use one freemium IAP to unlock full features and renewable subscriptions for some contents.Merging subscriptions IAPsThe two freemium IAP are different, and the Mac version cost more. They will stay distincts in a possible merge scenario.But the subscriptions are the same and shared between Mac and iOS. At the time being, I had to have two products for each subscription, one for each Store with different product ID. Its currently up to our licence server processing to do the merging and allow content access for both versions whenever one environment does a purchase.It's completely unclear to me how and when to merge the two subscription products. If the Mac version vanishes by using the iOS bundle, what will happen to current purchases, both one time freemium and subscription. How will the users get the licences they paid for in the former (current) Mac version ? Specifically, will a merged app doing a restore purchase get all the purchases

Hi everyone! I've got the same error (SKError.Code.unknown, i.e. 0) and underlying message. It appears when a client tries to purchase the same product second time. It looks like this case shouldn't happen, because if all set correct, client shouldn't generate purchase second time. But I guess, it is easy to reproduce it having second device for the same appleId and initiating second purchase. Ways to reproduce: Client chooses product item AppStore shows message that such product has been purchased and is still active SKPaymentTransactionObserver gets error: SKError.Code.unknown with underlying message (as noticed in initial message of this thread) So, client knows what happened and transaction observer too. It is helpful for transaction observer as we can disable spinner on product items screen (for example), but what about other cases when we get such .unknown error code and other underlying messages? Should we show Unknown message happened to a client or just react on it