Open source feature flagging and experimentation platform for stress free deployments, measured impact, and smarter decisions.

GrowthBook Users

VID_20230831163418.mp4

Hi Hasan,  have you seen this: <https://docs.growthbook.io/lib/react#waiting-for-features-to-load>

Try calling `const enabled = useFeatureIsOn("new-pricing")` from within the PricingPage itself, instead of passing it in as a prop.  As you have it now the enabled variable is loading from outside the FeaturesReady logic.

I have tried calling useFeatureIsOn in the PricingPage component but the issue persists

and you changed the code to use it and got rid of the prop?

You can set `gb.debug=true` on your growthbook object to see console logs of how gb evaluates your feature.  That might help you in understanding what is going on.

It could be caused by a delay when loading the attributes…

one would be to initially not load a price at all, then load in the price based on which variation is loaded - it will flicker, but may just look like loading

it looks like it is assigning a variation, then switching variations (instead of loading the spinner) - which can happen if the attributes change

Is there any way to load variations on the server and serve the pricing page with variations?

It will help improve user experience

ok thanks, <@U01T6HCHD0A> for your support, I am working on rendering variations server-side

thanks <@U055BV0MH88> for sorting your support

you just have to log that exposure event, doesn’t have to happen client side or server side - but has to happen somewhere