Skip to main content

Hello,

iOS users changed subscription plan but it seems the new subscription does not immediately affect their account.

Customer profile shows user successfully changed their renewal preference to higher subscription plan but user’s current Entitlement has not been changed. I think the user's Entitlement will be changed on the next subscription renewal.

What I want is crossgrade, users should upgrade and use new plan immediately.

All of our subscription plans are in the same subscription group and subscription duration are same. It should be Crossgrading with Same Duration but I have no idea what is the problem.

Please help me to solve the problem.

Hi, Rigman.

Check subscription level from App Store Connect. Somehow its order could be mixed up and not working properly. If users are upgrading to higher level subscription (lower number level), user will see the message like ‘Your upgrade will start now’.

Hi, Rigman.

Check subscription level from App Store Connect. Somehow its order could be mixed up and not working properly. If users are upgrading to higher level subscription (lower number level), user will see the message like ‘Your upgrade will start now’.

Thanks! That was the problem. I updated level to correct order. It should work fine. Users who changed their plan before level update I just did, are still in trouble but there will be no more problem.

- I could solve my problem myself. :sob: 
- RevenueCat is really good product. Thank you.

Filed a support ticket but figured I’d chime in here cc ​@cody ​@Jens -- why if a user does a PRODUCT CHANGE to a product_id that is in an entitlement does RevenueCat not respect that? 

Example flow: 

  • user starts trial for gold_sku_01 in sub group 01 (with rev cat entitlement Gold) 
  • user hits feature gate for platinum in sub group 01 (with rev cat entitelement Platinum) 

 

Right now, I see the product changed event in RevenueCat but it does not update the entitlement to Platinum so the user is still stuck. Unless we have something configured incorrectly on our end or are misunderstanding why is that?

​@Seth Miller Looking into it now and replied to the ticket, let’s work out of the support ticket first and then we can update here.

Reply


Terms & ConditionsCookie settings