Skip to main content
Solved

Paywall features not updating

H
Forum|alt.badge.img+4

For some reason the old setup I had months ago still persists and nothing I do gets rid of it. I can’t see the latest version only of the features.

For some reason, these ones update immediately:

  1. The main content
  2. Packages
  3. Call to action
  4. Footer links
  5. Close button

However, the features do not update no matter what.

This is what I’ve tried:

  1. Getting the latest flutter sdk, current version in pubspect.yaml is `^3.7.0`
  2. Getting the latest versions of purchases_flutter and purchases_ui_flutter
  3. Cleaning the build folder and running the app again
  4. Clearing the apps cache, storage and uninstalling the app.
  5. Publishing a release build to the internal test track and installing it on google play console.

I’ve attached screenshots of the device and the preview in the dashboard for side by side comparisons.

 

I don’t know what else to do and it’s been frustrating me for months.

 

Minor nitpick: It is such a pain to scroll down on the Paywall editor to see the entire preview on the right.

Best answer by henry-adu

guilherme wrote:

Hey ​@henry-adu ,

We’ve recently made some updates to the Flutter SDK that may help with issues like this. If you haven’t already, please make sure you're on the latest release of purchases_flutter and purchases_ui_flutter

Your paywall should be updating as you save and publish changes, so there might be something else happening if that’s not the case (e.g linked offering on the paywall from an inactive one).

Feel free to open a support ticket with more detail, we’d be happy to take a closer look!

 

Best,

I did contact support and the issue has been resolved. I assumed all locals used the same strings and I was updated en-gb when I was using en-us. I deleted en-us and defaulted to en-gb and the issue resolved.

View original
Did this post help you find an answer to your question?

3 replies

guilherme
RevenueCat Staff
Forum|alt.badge.img+3
  • guilherme
  • RevenueCat Staff
  • 54 replies
  • June 4, 2025

Hey ​@henry-adu ,

We’ve recently made some updates to the Flutter SDK that may help with issues like this. If you haven’t already, please make sure you're on the latest release of purchases_flutter and purchases_ui_flutter

Your paywall should be updating as you save and publish changes, so there might be something else happening if that’s not the case (e.g linked offering on the paywall from an inactive one).

Feel free to open a support ticket with more detail, we’d be happy to take a closer look!

 

Best,

Gui, Developer Support Engineer @ RevenueCat
L
Forum|alt.badge.img
  • Laters
  • New Member
  • 1 reply
  • June 4, 2025

I updated both packages to 8.10.0 and have same issues, possibly even worse because I cannot change the pricing. My offering had 1 price and I added a second price option (I verified all is working on both ends) yet the paywall doesn't show it , even 5 hours later. Not only does my app not update, the RevenueCat Dashbaord doesn't even update the preview, that in of itself indicates a major issue.

 

I've tried everything the poster did to no avail, and its disappointing to see there is no proper cache clearing in the SDK.

On the left is the the updated text when clicking specifically on on the input in the Paywall edit screen. On the right is my app AND the paywall edit screen if you click off this box (basically default view) . 

Additionally I deleted the paywall, and when I crate a new paywall, this second new package is not available. 

 

 

H
Forum|alt.badge.img+4
  • henry-adu
  • Author
  • Helper
  • 1 reply
  • Answer
  • June 5, 2025
guilherme wrote:

Hey ​@henry-adu ,

We’ve recently made some updates to the Flutter SDK that may help with issues like this. If you haven’t already, please make sure you're on the latest release of purchases_flutter and purchases_ui_flutter

Your paywall should be updating as you save and publish changes, so there might be something else happening if that’s not the case (e.g linked offering on the paywall from an inactive one).

Feel free to open a support ticket with more detail, we’d be happy to take a closer look!

 

Best,

I did contact support and the issue has been resolved. I assumed all locals used the same strings and I was updated en-gb when I was using en-us. I deleted en-us and defaulted to en-gb and the issue resolved.

guilherme
1 person likes this
  • guilherme
    guilherme

Reply


Most helpful members this week

Terms & ConditionsCookie settings

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