Skip to main content
Question

Offered Package icon state not updating correctly in Paywall Editor (iOS)

  • November 22, 2025
  • 5 replies
  • 60 views

Forum|alt.badge.img+4
Paywall Editor on the left / iOS Simulator on the right

 

Hi!

I’m seeing a visual/state bug with the Offered Package component in the new Paywall Editor testing on iOS.

What I’m doing
    •    Using the Paywall Editor with the Offered Package component.
    •    I configured the icon states like this:
    •    Default: Circle, color #3D3C41, 24×24
    •    Selected: Filled Circle Check, color #FBEB00, 24×24
    •    In the editor preview everything looks fine.

Issue:

On the iOS simulator, when I open the paywall and tap on a different package than the one selected by default:
    •    The newly tapped product becomes selected
    •    But the icon on the left does not switch to the “Selected” icon for the newly chosen package.
    •    Instead, the originally selected package keeps the “Selected” icon, and only its color changes when I tap on other products.

So effectively, icon state and actual selection go out of sync: the default product keeps the filled check icon, while another product is actually selected.

(See attached screenshots – first image is how it looks in the simulator when switching between “Monthly” and “Yearly”.)

Expected behavior:

When the user taps a different package:
    •    The newly selected package should get the Selected icon (Filled Circle Check, yellow).
    •    The previously selected package should revert to the Default icon (outline circle, grey).

Environment:
    •    Platform: iOS Simulator (iPhone 17 Pro)
    •    Paywall: Using the new Paywall Editor with the Offered Package component
    •    SDK: purchases_flutter & purchases_ui_flutter – ^9.9.8
    •    Tested in debug build

5 replies

Forum|alt.badge.img+4
  • Author
  • New Member
  • November 22, 2025

Same is happening on a TestFlight version on a real device:
 

 


Same is happening for me, is there any resolution to this issue? This will potentially confuse customers.


alejandra-wetsch
RevenueCat Staff
Forum|alt.badge.img+6

Hey ​@sklaboy, ​@daniel-pinson-8beddb,

Thank you for reaching out and for providing such a detailed description of the issue you’re experiencing! 

I was able to reproduce this issue. I’ll share this internally with the Engineering team for them to review. I’ll let you know once I have more information!

Best,


alejandra-wetsch
RevenueCat Staff
Forum|alt.badge.img+6

Hey ​@sklaboy, ​@daniel-pinson-8beddb

I appreciate your patience!

The team has implemented a fix for this issue, which is now available in the latest versions of the SDKs. Upgrading to the latest version of the corresponding SDK you’re using should resolve this for you. Please let me know otherwise!

Best,


Awesome, thank you for the quick turnaround on this! I will upgrade my SDK and test.