The operation couldn't be completed. (superwall_react_native.PurchaseResultError error 1.)

[SuperLLN]

Hello, since a few days every time we try to purchase a product on iOS we got the confirmation message "You're all set" and then the following error.

On RevenueCat I can see the purchases as completed but the users can't access to the premium features and restore purchases. It's becoming critical as this error happens for all the users on the live version.

How could I fix it?

"@superwall/react-native-superwall": "^1.1.3",
"react-native-purchases": "^7.26.1",

[yusuftor]

Hi, this is an error that originates from your purchase controller's purchase function. Please check that you aren't receiving an error from RevenueCat on purchase within your app and that you're returning the correct value on successful purchase in your purchase controller.

[SuperLLN]

Thank you for your reply @yusuftor. I reused exactly the same code for RCPurchaseController as in your example and everything seems ok at this level. For information the payment is working on RevenueCat side. I'm checking this subject because I've received several complaints from users in the last few days, even though everything had been working perfectly for nearly a month.

I was able to obtain a log with MySuperwallDelegate and it's an EventType.transactionFail event that seems to be linked to Superwall that is triggered.

Handling Superwall event:', { event:
{ type: 'transactionFail',
error: 'The operation couldn't be completed (SuperwallKit.TransactionError error 1.)',

What can I do to make it work again?

[yusuftor]

The transactionFail event is just an underlying type when a PurchaseResultFailed is returned from the PurchaseController. Are you able to reproduce this issue every time? A search online shows "The operation couldn't be completed" happening from within RevenueCat's SDK and that's then passing to our SDK. But it's strange that you can see the payment working on RevenueCat's side though. I just released v1.2.0 which shows the error message without PurchaseResultError. But I imagine it will now just show "The operation couldn't be completed" but worth testing just to see if the error is any less generic sounding.