-
Notifications
You must be signed in to change notification settings - Fork 84
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Promotional subscription overrides normal subscription in customerInfo.entitlements
#844
Comments
👀 We've just linked this issue to our internal tracker and notified the team. Thank you for reporting, we're checking this out! |
Great question. It is true that entitlements cannot disambiguate this because of their format. You mentioned that "there is no customerInfo.subscriptions field". Would |
Hi @NachoSoto , I use |
With those you can fetch the product and look at their |
I meant a I need this field to make a correct change of subscription for Play Store. I need to know, whether the current subscription is in |
Sorry for the confusion, I see what you were saying now. This is indeed a limitation because that information is only available in the entitlement, and there can only be one entitlement active with an identifier. Is it not giving you the expected type? |
Hi @NachoSoto , no, because entitlement shows me the |
Hi all,
When I have both normal and promotional subscriptions active (and they have the same entitlement), I naturally see only one of them (only promotional) in the
customerInfo.entitlements
, since it is a dictionary with unique keys. But there is no way that I can get information about both subscriptions, because there is nocustomerInfo.subscriptions
field.And for Play Store it's important to know some information about a normal subscription, since it influences the
googleProductChangeInfo
forpurchasePackage
method.The CustomerInfo interface (https://revenuecat.github.io/react-native-purchases-docs/7.15.0/interfaces/CustomerInfo.html).
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: