Closed Niwilai closed 2 years ago
Hey @Niwilai, could it be that you edited the feature flag for one environment, but are evaluating them for a different environment?
Another less common culprit could be that you changed the defaults to both evaluate to the same value
Based on the logs I saw that you were editing the production environment. There is a dropdown at the top of the page. You can use it to switch between different environments. Let me know if that was the issue :)
Based on the logs I saw that you were editing the production environment. There is a dropdown at the top of the page. You can use it to switch between different environments. Let me know if that was the issue :)
![]()
This was it. Such a rookie mistake, thank you for clarifying.
Of course! I wonder if I can make the distinction clearer somehow. Feel free to point anything out that might have helped you realize it sooner!
Of course! I wonder if I can make the distinction clearer somehow. Feel free to point anything out that might have helped you realize it sooner!
Maybe something along those lines would have been more obvious to me. But I wouldn't worry too much about it unless this happens at least once more.
Hi Dominik,
Thanks for this awesome package and the hosted service. I gave this a try on our end and I noticed that for some reason, although the boolean was set to active it would always return false as the value.
Is there a setting I have oversighted? Thanks