Skip to main content

On test subscription phase, Does RevenueCat send events on first subscription expire and then for renewal? I'm worried because is there any time window between expiration and renewal when user will loose premium access temporarily?

I have a subscription plan on Google Play console with auto-renewal on. However, infrequently I see the paywall is prompted on my app (which I’m triggering when isActive is false) and when I try to re-subscribe, it says subscription is already active. I'm suspecting this is due to the expiry (which starts my Paywall fragment) and later renewal event, which restores the subscription.

What could be possibly done to avoid this? I also have grace period enabled, though I’m not handling it anywhere in the code to check subscription status. Is this could be a test subscription quirk? 

Hi ​@kaidul-2a1912,

Are you asking specifically about users who have had a billing error? This is the only scenario in which a grace period would come into play, and you don’t necessarily need to do anything to handle this specifically, beyond listening for events. 

In a typical subscription scenario with auto-renewal enabled, we wouldn’t send an `EXPIRATION` event unless the user has opted out of auto-renewal. Are you able to let me know where you’re grabbing the expiration from, or a bit more about the flow that you’re seeing? 

If you’d like to share specific users that you’re seeing odd behavior with, you can always open up a support ticket with us at app.revenuecat.com/support .

Terms & ConditionsCookie settings