Skip to main content
Solved

Android - isActive is false after renew the subscription


Forum|alt.badge.img+1

Hi RevenueCat,

After renew subscription, the isActive become to false, I got the log:

EntitlementInfo(identifier='Premium', isActive=false, willRenew=true, periodType=NORMAL, latestPurchaseDate=Tue Apr 19 15:22:10 GMT+07:00 2022, originalPurchaseDate=Tue Apr 19 15:22:10 GMT+07:00 2022, expirationDate=Tue Apr 19 15:29:08 GMT+07:00 2022, store=PLAY_STORE, productIdentifier='com.test.nightshade.one.monthly', isSandbox=true, unsubscribeDetectedAt=null, billingIssueDetectedAt=null, ownershipType=UNKNOWN)

I saw somethings:

  • ownershipType is UNKNOWN → it should be PURCHASED
  • isActive = false + willRenew = true → it should be isActive = true + willRenew = true

Do you know why it’s happen and how to fix it?

---------------------------------------

SDK Version: 5.0.0-rc3

Operating System: android 9

 

Best answer by tina

Updating this thread based on our ticket conversation:

 

Sandbox behavior can be finicky since the renewals are accelerated and sometimes renewals in sandbox can be missed due to the fast billing periods. This is also mentioned in our docs here: https://docs.revenuecat.com/docs/google-play-store#working-with-subscriptions The app will usually be a little bit behind due to its built-in caching system. In order to allow users to access their subscriptions offline, the SDK caches the subscription status. Whenever you call getCustomerInfo(), the SDK will update the cache if it's older than five minutes. To help with this, you can enable Google Real-Time notifications to reduce delays.
 
I wouldn't worry about this behavior once the app is in production since a monthly renewal will actually occur every month at the end of the billing cycle, rather than every 5 minutes.

View original
Did this post help you find an answer to your question?
This post has been closed for comments

3 replies

tina
RevenueCat Staff
Forum|alt.badge.img+10
  • RevenueCat Staff
  • 338 replies
  • April 20, 2022

Hi @Huy Nguyen 

I saw that you opened a ticket for this request. I replied in the ticket to gather some more information about app user IDs and debug logs. 


Forum|alt.badge.img+1
  • Author
  • New Member
  • 1 reply
  • April 21, 2022
tina wrote:

Hi @Huy Nguyen 

I saw that you opened a ticket for this request. I replied in the ticket to gather some more information about app user IDs and debug logs. 

Hi tina, 

I have attached the debug logs at this comment and my app user ID is 28e8f250-28f8-4761-873f-c20ba6058664

Could you help me take a look on it?

Thank you,

Huy


tina
RevenueCat Staff
Forum|alt.badge.img+10
  • RevenueCat Staff
  • 338 replies
  • Answer
  • April 29, 2022

Updating this thread based on our ticket conversation:

 

Sandbox behavior can be finicky since the renewals are accelerated and sometimes renewals in sandbox can be missed due to the fast billing periods. This is also mentioned in our docs here: https://docs.revenuecat.com/docs/google-play-store#working-with-subscriptions The app will usually be a little bit behind due to its built-in caching system. In order to allow users to access their subscriptions offline, the SDK caches the subscription status. Whenever you call getCustomerInfo(), the SDK will update the cache if it's older than five minutes. To help with this, you can enable Google Real-Time notifications to reduce delays.
 
I wouldn't worry about this behavior once the app is in production since a monthly renewal will actually occur every month at the end of the billing cycle, rather than every 5 minutes.


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