Skip to main content
Question

Why doesn't customer information get updated after repurchase via web checkout following an expired subscription?

  • August 6, 2025
  • 5 replies
  • 163 views
T
Forum|alt.badge.img

I'm running into an edge case with RevenueCat when handling purchases via a Web Purchase Link after a user's subscription has expired.

 

Problem

When a user makes a first-time purchase via a web purchase link, the customer info updates correctly and addCustomerInfoUpdateListener fires as expected.

However, if the user’s subscription has previously expired, and they make a new purchase via web checkout, the customer info:

  • Does not show the new active subscription

  • Does not trigger addCustomerInfoUpdateListener

This causes the app to remain in a non-subscribed state.

 

What I’m already doing

  • After the user completes the web checkout and returns to the app, I:

    • Call Purchases.invalidateCustomerInfoCache()

    • Then call Purchases.getCustomerInfo()

I’ve verified that the purchase does go through successfully, since in the RevenueCat Dashboard I can see both the expired entitlement and the new active entitlement.

Environment

  • Testing in a Sandbox environment where monthly subscriptions renew every 5 minutes

  • React Native SDK 0.79.4

  • Expo 53.0.12

  • react-native-purchases ~8.11.3

  • Issue reproduces on iOS

Expected Behavior

After a successful web purchase (even after a prior expiration):

  • addCustomerInfoUpdateListener should trigger

  • Purchases.getCustomerInfo() should return an active subscription

 

Is this a known limitation when repurchasing via web checkout after an expiration? If not, what’s the best way to ensure the app recognizes the updated subscription state in this scenario?

Any suggestions, workarounds, or clarifications are appreciated!

moritz-cooks
This post has been closed for comments

5 replies

guilherme
RevenueCat Staff
Forum|alt.badge.img+6
  • guilherme
  • RevenueCat Staff
  • August 8, 2025

Hey ​@ttmjima,

This isn’t a known limitation, and the forced refresh should update CustomerInfo as expected. To help narrow it down, could you confirm:

  • if the same flow works on Android? Or is this a Apple specific run?

  • after returning to the app, is the addCustomerInfoUpdateListener still registered (not nil) in logs?

  • even if you wait out our caching window before checking again, does the entitlement become active?

Also, could you share a sample App User ID and logs from the return-to-app moment? We can check whether the new purchase is linked to the correct user and processed on our side.

Feel free to do so here, or if you prefer to send via a private message (or even open a support ticket , mentioning this ticket) so I can have a better look!

Best,

Gui, Developer Support Engineer @ RevenueCat
T
Forum|alt.badge.img
  • ttmjima
  • Author
  • New Member
  • August 12, 2025

Hey ​@ttmjima,

This isn’t a known limitation, and the forced refresh should update CustomerInfo as expected. To help narrow it down, could you confirm:

  • if the same flow works on Android? Or is this a Apple specific run?

  • after returning to the app, is the addCustomerInfoUpdateListener still registered (not nil) in logs?

  • even if you wait out our caching window before checking again, does the entitlement become active?

Also, could you share a sample App User ID and logs from the return-to-app moment? We can check whether the new purchase is linked to the correct user and processed on our side.

Feel free to do so here, or if you prefer to send via a private message (or even open a support ticket , mentioning this ticket) so I can have a better look!

Best,

Hi ​@guilherme,

  • I’m experiencing the same issue on both Android and iOS

  • Yes, the addCustomerInfoUpdateListener is still registered after coming back to the app

  • The entitlement is still not active after having the app in the foreground for 5 minutes and retrieving the customer info again

I’ll send some logs via a support ticket. Thank you!

moritz-cooks
Forum|alt.badge.img
  • moritz-cooks
  • New Member
  • August 21, 2025

I’m facing exactly the same issue as well.

I have a consumable product which I bought via Web Purchase Link. The first purchase three days ago is still present in the customerInfo.entitlements.all object but there is no new entitlement in the customerInfo.entitlements.active object. In the RevenueCat dashboard I can see the correct entitlement on the user, if I activate Sandbox data. 

guilherme
RevenueCat Staff
Forum|alt.badge.img+6
  • guilherme
  • RevenueCat Staff
  • August 21, 2025

Hey ​@moritz-cooks ,

Thanks for adding to this! 

Could I ask you to share some more informations about your project/app, example customer ids and SDK that you are using via our https://app.revenuecat.com/settings/support?tab=contact ?

If you could also reference this thread too please, for extra context, so we can link back to it and update it.

Thanks,

Gui, Developer Support Engineer @ RevenueCat
moritz-cooks
Forum|alt.badge.img
  • moritz-cooks
  • New Member
  • August 21, 2025

Hey ​@moritz-cooks ,

Thanks for adding to this! 

Could I ask you to share some more informations about your project/app, example customer ids and SDK that you are using via our https://app.revenuecat.com/settings/support?tab=contact ?

If you could also reference this thread too please, for extra context, so we can link back to it and update it.

Thanks,

Hi ​@guilherme,

I just sent you a support request with the requested information!

 

Best,

Moritz

guilherme
Terms & ConditionsCookie settingsAccessibility statement