Skip to main content
Question

Current Offering Not Updating After Changing Offering Override Twice

  • March 4, 2026
  • 2 replies
  • 18 views
H
Forum|alt.badge.img+4

Hi,

I was testing the offering override feature in the dashboard for my android app.

First, I changed the current offering from the default to “offering_a” for a sandbox user, and it worked as expected.

However, about an hour later, I tried to change the offering back to the default, but the change didn’t take effect. I checked the offerings JSON response on the android sdk. (it might be cached, but i’m not certain).

Is there any caching behavior on either the server-side or sdk-side that could affect updates to the current offering? Or once a non-default offering is assigned to a user, is it possible to change it again?

 

Thanks!

2 replies

matt-heaney
RevenueCat Staff
Forum|alt.badge.img+3
  • matt-heaney
  • RevenueCat Staff
  • March 4, 2026

Hey ​@heejin-lee-cf2117 ,

Thanks for the question! I’m Matt from RevenueCat, and I’d love to help with this!

Offering overrides should be fully reversible, so changing a user from a specific offering back to the default should work as expected. While there is some caching within the SDK, it typically shouldn’t last very long. More details on the cache policies can be found here: https://www.revenuecat.com/docs/test-and-launch/debugging/caching

Can I confirm whether the issue is still happening for this user?

If so, could you please privately message me the user ID of the impacted user and I’ll dive deeper.

Thanks!

Matt, Developer Support Engineer @ RevenueCat
    matt-heaney
    RevenueCat Staff
    Forum|alt.badge.img+3
    • matt-heaney
    • RevenueCat Staff
    • March 7, 2026

    Hey everyone!

     

    ​@heejin-lee-cf2117  and I discussed this further in private messages, but I wanted to give an update here in case anyone else runs into this issue and finds this thread.

     

    ​@heejin-lee-cf2117  managed to resolve this by switching the offering override back to a different offering, and then setting it back to the default again.

     

    I will explore this further on my end and raise any potential caching issues with the engineering team to make sure they are resolved.

     

    I hope this information helps, and I’ll push to make sure any discovered issues are addressed quickly!

     

    Thanks!

    Matt, Developer Support Engineer @ RevenueCat
    Terms & ConditionsCookie settingsAccessibility statement