https://www.growthbook.io/ logo
Join Slack
Powered by
Hey everyone! Has anyone had issues with feature f...
# ask-questions
j
Hey everyone! Has anyone had issues with feature flag values not being the same when accessed in a Flutter environment vs. a NodeJS environment? The feature is being assigned based on the 
userId
property and both the front and back-end are assigning the attribute to the same value.
✅ 1
r
@blue-sundown-32899 has marked the issue as closed. Reopen Issue button
f
Hi Connor - did you set the hashing version?
to version 1?
j
Let me check!
How exactly do I check that?
f
are you launching the experiment via the feature flag?
j
Yes
f
if you edit the experiment rule
j
Ahhh I see we are using V2
f
ah, yes, that can do it
j
Gotcha, it was in the fine print! I see Flutter does not support V2
f
yes, we’re fixing this
j
No worries! I have to destroy and recreate the feature flag to change the hashing version correct?
So after looking around for a little bit, I can't seem to figure out how to set the hashing version when creating an experiment. Is this not possible at the moment?
f
it is possible
but I believe we hide it on initial creation, and expose it on editing
but I know that part of the product is changing a lot
j
You are correct sir. Thank you we found it.
I will test right now to see if that solves our issue!
There unfortunately still seems to be a mismatch even when reverting back to V1 hashing. Any other ideas as to what the cause could be?
f
can you make sure the SDK payload for the NodeJS SDK says v1?
@future-teacher-7046 thoughts?
j
Never mind! We had to create a new experiement entirely to get it functioning properly. Even after updating to have it use V1, there was a mismatch. Luckily we caught this early though and creating a new experiment was no issue for us.
Thank you for the quick help!
f
okay cool
68 Views
Open in Slack
PreviousNext
Powered by