I have an iOS app, using SwiftUI, and effectively latest version of everything. I am using RevenueCat 5.23.0, minimum deployment iOS 18.1, XCode 16.3. I am facing an error which appears to only happen in production - not the sandbox. It’s extremely frustrating because it results in an RC error, even though the credit card transaction or trial start was successful.
The user will tap my payment button, double click on the iOS native payment sheet to confirm w/ Face ID. The credit card payment or the trial start will succeed, and then iOS shows another prompt with the title “Turn off renewal receipt emails?” with the body “Get fewer emails by turning off renewals receipts for subscriptions. Your receipts will still be available in App Store settings > Purchase Hisotry” with two options to either turn on or off renewal emails.
No matter which option is being selected, RevenueCat is populating the error object in the completion callback! This is happening even though my user is being billed, and RC is showing trial starts or new subscribers in the RC dashboard! What the heck?
In the code “Purchases.shared.purchase(package: proProduct.package) { (transaction, customerInfo, error, userCancelled) in”… The error object is logged as “The operation couldn’t be completed. (RevenueCat.ErrorCode error 1.) - Purchase was cancelled.”
So now my user is presented with an error in the UI (because of course I need to inspect the error object). The customerInfo.entitlements object is NOT being populated with an entitlement to my pro product. However, after the user dismisses the error alert (and goes back to seeing the paywall), they can now tap the Restore Purchases button which finally updates the customer info and the paywall is dismissed and the user has access to my pro features.
I have TWO screen recordings of this happening from friends who let me test with their devices. I cant imagine what my real customers are feeling given the credit card is billed but RevenueCat is complaining due to what is likely a bug in the SDK.
Ok, heres another bug, I cant attach an image to this post… so here’s a link to Imgur where you can see the iOS prompt which is triggering the error.
Can an RC developer PLEASE ADDRESS THIS ISSUE?
