Hello! We've setup a simple A/B experiment that is...
# ask-questions
l
Hello! We've setup a simple A/B experiment that is being used across our backend and two mobile apps and are seeing some inconsistencies between iOS and the rest (including the Test Feature Rules facility on the web dash). This is leading to attribution mismatches in our analysis. From everything we can tell the attributes are matching across the board and the iOS app has the correct experiment/feature definitions but for some reason its not returning the same experiment/variant assignment values. Any suggestions on what we could dig into here?
1
r
@blue-sundown-32899 has marked the issue as closed. Reopen Issue button
l
Resolved some confusion on the android side and seems like actually both the kotlin and swift SDKs/implementations are returning different feature variant results compared to the javascript and
Test Feature Rules
facility. Any assistance would be greatly appreciated
f
hi Phil
👋 1
l
Also how do we access "Premium Support"
f
we should be more clear, but the test feature rules uses v2 of the hashing algorithm
you can make sure everyone gets the same by switching them all to v1
on the JS ones, which default to v2
l
got it, thanks for the info that certainly sounds like it would explain what we're seeing
Can you point me to where that gets set in the dash?
f
yes
If you edit the experiment
you should see this modal
(or edit the rule, then edit the targeting)
l
Thank you so much!
just to confirm v2 isn't supported on the mobile sdks?
f
correct
1
l
got it - looks like I need to stop the experiment first
f
sorry about that, we’re working on getting those other SDKs updated
yes
l
Appreciate the info - was definitely a confusing experience. We only discovered it was an issue once we enabled an activation metric
otherwise loving GB!
f
thanks
we’re working on our UX and DX, so we appreciate the feedback
👍 1
l
Sure thing!