Hi,
We recently implemented auto-renewable subscription IAPs and there seem to be problems for some users. During sandbox testing everything works as expected but in production we have been able to replicate following problem:
1) User with no payment method tries to subscribe, is shown that card should be addes. App receives SKError.unknown
2) User fills in the card details, returns to the app. App receives SKError.unknown once again
3) User taps buy again, and new payment is added to queue once again. Payment sheet appears and after user action popup with title "Authentication Required" appears (described here: https://developer.apple.com/support/psd2/)
4) User finishes authentication, return to the app and SKError.unknown is received.
5) This is the step when sometimes SKPaymentTransactionState.purchased is not received right after SKError.unknown. After killing the app and opening it, it's received.
Possible problem we have but which, I believe, should not have an impact on this problem - we are calling add (SKPaymentTransactionObserver) before AppDelegate.didFinishLaunchingWithOptions - it's called inside the initializer of our IAP class which is initialized as instance variable of AppDelegate.
Extra question, what should we do with all the SKError.unknown during interrupted purchase flow? Documentation says "the application can read the transaction’s error property to return a meaningful error to the user." here https://developer.apple.com/documentation/storekit/skpaymenttransactionobserver/1506107-paymentqueue . But how can meaningful error message be shown to user from unknown error code other than "Something went wrong"?
We recently implemented auto-renewable subscription IAPs and there seem to be problems for some users. During sandbox testing everything works as expected but in production we have been able to replicate following problem:
1) User with no payment method tries to subscribe, is shown that card should be addes. App receives SKError.unknown
2) User fills in the card details, returns to the app. App receives SKError.unknown once again
3) User taps buy again, and new payment is added to queue once again. Payment sheet appears and after user action popup with title "Authentication Required" appears (described here: https://developer.apple.com/support/psd2/)
4) User finishes authentication, return to the app and SKError.unknown is received.
5) This is the step when sometimes SKPaymentTransactionState.purchased is not received right after SKError.unknown. After killing the app and opening it, it's received.
Possible problem we have but which, I believe, should not have an impact on this problem - we are calling add (SKPaymentTransactionObserver) before AppDelegate.didFinishLaunchingWithOptions - it's called inside the initializer of our IAP class which is initialized as instance variable of AppDelegate.
Extra question, what should we do with all the SKError.unknown during interrupted purchase flow? Documentation says "the application can read the transaction’s error property to return a meaningful error to the user." here https://developer.apple.com/documentation/storekit/skpaymenttransactionobserver/1506107-paymentqueue . But how can meaningful error message be shown to user from unknown error code other than "Something went wrong"?
-
—
App4G
Add a CommentDid you ever find a solution to this? I, too am not able to replicate the the steps in apple's guideline https://developer.apple.com/documentation/storekit/original_api_for_in-app_purchase/testing_in-app_purchases_with_sandbox/testing_an_interrupted_purchase specifically item #10 does't come up until the app goes to background and then comes back to foreground.
Even if I did utilise the
NotificationCenter.default.addObserver(self, selector:#selector(appActive), name: UIApplication.didBecomeActiveNotification, object: nil)and get it to call the transactionObserver, it still doesn't come out. A physical touch on the home button, and then relaunching the app is the only thing that will trigger the purchase again