Open ronyfadel opened 8 months ago
👀 We've just linked this issue to our internal tracker and notified the team. Thank you for reporting, we're checking this out!
Hey @ronyfadel! Definitely valid feedback. Breaking it down into two components:
storeProblemError
: yeah, this is fairly generic. Jacob told me about the issue you were having, I would have expected those to be translated into RC's paymentNotAllowedError
, which would have been much more informative. Any chance you have logs and sysdiag for them? The expected behavior from StoreKit is that they'd send a paymentNotAllowed
, but ASDErrorDomain
errors are undocumented. We've captured a few manually and do some translation, but they can be hard to track down. If you send me logs, I'm happy to file a radar and get the codes mapped more nicely to paymentNotAllowed
.
Errors that would warrant better localized description: absolutely agree. We've historically relied on returning error codes, and expecting developers to translate the messages into something user-friendly themselves, but, this feels like an outdated assumption at this point. A lot of devs just want an easy way to display an error to a user, and it's something we could do. We've had a tough time with proper localization for paywalls, but I'd like to find a way to do it nicely on behalf of all RevenueCat customers
@aboedo I'll email you, let's dig into it!
RevenueCat's RCPurchasesErrorCode is directly displayed to hundreds of thousands of users daily. It's a shame that the errors aren't localized.
Furthermore, some errors (e.g. storeProblemError) have underlying errors which would warrant a better localized description (such as 'no network connection' or any other storekit error)