Hey guys, we need your support for an experiment we are running. From what our engineers see it converts the string we put in the targeting condition to an actual Date instance, and comparing that to a string doesn't work

@future-teacher-7046 do you know?

Is this a feature you created in the GrowthBook UI?

Yes

Hmm, do you have a screenshot of that feature rule in GrowthBook? The value you enter in the UI should always be treated as a string, not a date instance, so maybe there's a bug there.

You mean this?

I'm not able to reproduce the bug. When I add a condition like that in the UI and then inspect it within the javascript SDK, I see it as a string

We're logging (part of)

_growthbook.getFeatures()

. We tried re-adding the condition and it's still happening. Interestingly, in the chrome extension it's correctly showing as a string

There's nothing in the GrowthBook SDK that would do that. Is it possible you have some other script that's intercepting network requests and parsing strings that look like dates?

Yup that's seems to be it. Thanks a lot for the fast help! Outstanding support 🙏🏼