Skip to content

OfferingsManager: expose underlying error when ProductsManager returns an error#1792

Merged
NachoSoto merged 1 commit into
mainfrom
offerings-manager-product-manager-error
Aug 2, 2022
Merged

OfferingsManager: expose underlying error when ProductsManager returns an error#1792
NachoSoto merged 1 commit into
mainfrom
offerings-manager-product-manager-error

Conversation

@NachoSoto

@NachoSoto NachoSoto commented Aug 2, 2022

Copy link
Copy Markdown
Contributor

This will help figure out the reason behind #1765.
We were currently ignoring the error returned by ProductsManager.

In the example below, we can see the underlying issue is SKErrorDomain code 5.

Before:

Error fetching offerings - The operation couldn’t be completed. (RevenueCat.OfferingsManager.Error error 1.)

After:

Error fetching offerings - The operation couldn’t be completed. (RevenueCat.OfferingsManager.Error error 1.)
Underlying error: The operation couldn’t be completed. (SKErrorDomain error 5.)
ERROR: 😿‼️ There is an issue with your configuration. Check the underlying error for more details. There's a problem with your configuration. None of the products registered in the RevenueCat dashboard could be fetched from App Store Connect (or the StoreKit Configuration file if one is being used).
More information: https://rev.cat/why-are-offerings-empty

…turns an error

This will help figure out the reason behind #1765.
We were currently ignoring the error returned by `ProductsManager`.

@taquitos taquitos left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yesss, this is awesome. 🎈🐐

@NachoSoto NachoSoto merged commit 233e3a3 into main Aug 2, 2022
@NachoSoto NachoSoto deleted the offerings-manager-product-manager-error branch August 2, 2022 18:19
This was referenced Aug 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants