“restore purchases”

We would find that transaction in the receipt, verify that the purchase is valid, and enable whatever functionality/content is provided by that purchase (if not already enabled). The usual IAP stuff. If it worked the same as a restored purchase or a 'repurchase for free' I'd just handle it the way we handle those, and be totally happy, but it doesn't. I'm still unclear why you think it should be any different from those cases.And yes, I know we can just walk the whole receipt and make sure that everything in there is handled and call it a day, but the whole point of these updatedTransaction notifications is to be told when a change (or previously unhandled purchase) happens so it can be processed and not have to keep and compare the state of the receipt constantly. And it works just fine in every other situation, except this 'you are already subscribed' case.

I have a couple of users reporting the same problem as of late. They're neither able to make purchases nor restore purchases. The error they're getting is SKErrorDomain error 0. In one case the user has two devices, on one everything works fine but not on the other, both devices are on iOS 8.4 and the same version of my app. I'm wondering if it's related to iOS 8.4 since this problem never showed up until now.My app has been out for a couple of years. I haven't changed the IAP code for several months, so I don't think it's a bug in my IAP code. Also we have thousands of users who've made purchases with no issues within this same time frame.

func paymentQueueRestoreCompletedTransactionsFinished(_ queue: SKPaymentQueue) { if success == true{ let alert = UIAlertController(title: Completed, message:All your previous purchases have been restored, preferredStyle: .alert) alert.addAction(UIAlertAction(title: OK, style: .default) { _ in }) let rootVC = UIApplication.shared.keyWindow?.rootViewController rootVC?.present(alert, animated: true){} } } func paymentQueue(_ queue: SKPaymentQueue, updatedTransactions transactions: [SKPaymentTransaction]) { print(great, I got here) for transaction: AnyObject in transactions { let trans = transaction as! SKPaymentTransaction switch trans.transactionState { case .purchased, .restored: let prodID = p.productIdentifier switch prodID { case com.Carawind.FlipFlop.RemoveAds: success = true print(got here, too) AdBtn = true UserDefaults.standard.set(true, forKey: RemovedAds) RemoveAdsBtn.removeFromParent() self.viewController.HideAds() default: break } queue.finishTransaction(trans) ca

Initially when user purchase a subscription we will save subscription details in the BE.1.Let say user 1 purchased 1 month plan with his apple id and his original transaction is 1234, we save that in BE DB.2.User 2 purchased 6 months plan in device 2 his original transaction is 9876, will save that in BE DB.3.Now user1 logged in to app with user1 app credentials in Device 2 which have Appstore credentials of user 2.4.Now if i restore purchases in device 2 will get 6 months plan transaction id 9876, In application user1 will have transaction id 1234, when user tries to purchase another plan, we will . check both transaction ids,if they are not same will restrict the purchase, untill device 2 have user 1 appstore credentials.

One of my users is now getting this message for a recently renewed auto-renewable subscription:PurchaseOperation: [A3AD40F5] Purchase finished with error: Error Domain=SSErrorDomain Code=16 Cannot connect to iTunes Store UserInfo={NSLocalizedDescription=Cannot connect to iTunes Store}Something appears to have broken with auto-renewable subscriptions. When tapping to purchase a subscription the correct information appears showing the user is subscribed with the correct expiration date. However, the actual renewal is not confirmed and the user cannot progress past the purchase screen. This behavior does not appear in the sandbox... only in production. Restore purchases doesn't work as well.It would make sense that the verifyReceipt server is broken... but I can't think of a way to determine this with the production version of my app.

In the Application Receipt, the in_app array contain a history of all in app purchase receipts for all purchase, except those of type Consumable. However those receipt do not track the locale that the purchase was made from. There is the transaction_id field which could be associated with the orginal purchase information, but there is no API to use to access additional information about the transaction. You can submit an enhancement request that such API be implemented by using the Apple Developer Bug Report web page - http://bugreport.apple.com.If this information is needed, the app can know the current locale for the purchase by reviewing the response to the SKProductsRequest - product.priceLocale. If the purchase is made and is successful, the application can associate the purchase with the priceLocale information. I think this is what you referred to in find the currency of the user's Apple ID, using IAP APIs. Unfortunately, this information i

Great info giilby. I'll try filling up a test device too, and report back.In my case, yes, most of our IAPs are downloadable, hosted by Apple.Update:I filled up a device to the point where I was getting failed write attempts when I tried to write files to disk (using a separate test app). I then tried an IAP purchase in an App Store version of my app. I couldn't replicate the error, everything worked fine (other than the download failing because of low disk space - but that's an expected error). The device is on iOS 8.4.1.*sigh* I was hoping to get closer to an answer. I have about 20 users now who can't restore purchases and can't buy new purchases.