Skip to main content
Question

Re-Subscribe

  • November 18, 2024
  • 5 replies
  • 154 views

Forum|alt.badge.img+2

We have been using subscriptions on Android and iOS for a while now with only an annual option, and that has been working fine.  We are adding a monthly option, and during Android testing have noticed that if I cancel a yearly subscription, then attempt to purchase another subscription (yearly or monthly), I see the following error: 

PlatformException(6, This product is already active for the user., {code: 6, message: This product is already active for the user., readableErrorCode: ProductAlreadyPurchasedError, readable_error_code: ProductAlreadyPurchasedError, underlyingErrorMessage: Error updating purchases. DebugMessage: . ErrorCode: 7., userCancelled: false}, null). 

Any ideas?  This is a production test scenario, on a physical phone with a valid google play account.  We are only testing Android at this time.

Thanks!

This post has been closed for comments

5 replies

Forum|alt.badge.img+2
  • Author
  • New Member
  • 3 replies
  • November 18, 2024

Maybe I should add...I think the desired behavior here is to be able to cancel a yearly subscription and then purchase a monthly.  Is this not a recommended flow?  

Also thinking...in this case the user has cancelled their subscription via Play, but since it is annual, they still have access to to the entitlements until the end of the year.  In this window (cancelled but still ‘active’) should we not be offering any subscriptions to them at all?

 


Ryan Glanz
RevenueCat Staff
Forum|alt.badge.img+8
  • RevenueCat Staff
  • 383 replies
  • November 25, 2024

There are a few different options for changing a subscription in Google. Are you using a particular proration mode in this case, or just the default?


Forum|alt.badge.img+2
  • Author
  • New Member
  • 3 replies
  • November 28, 2024

Just the default non-prorated for now.  


Ryan Glanz
RevenueCat Staff
Forum|alt.badge.img+8
  • RevenueCat Staff
  • 383 replies
  • December 6, 2024

And are you handling the downgrade logic with that PurchaseParams Builder? If you’re just using purchasePackage, then it won’t perform as a downgrade, and will throw that error because the previous subscription is still active.


Forum|alt.badge.img+2
  • Author
  • New Member
  • 3 replies
  • December 6, 2024

OK, thanks for the reply, ​@Ryan Glanz , I’ll look into this.


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings