Hey folks, I have a question regarding a problem I have faced using Swift SDK. During our experimentation, we realized that some of our users are included in the treatment group using our Java and Kotlin SDKs, but the very same users were NOT assigned to the treatment group on our Swift SDK. During debugging, we realized that our Java and Kotlin SDKs were on latest version but our Swift SDK was on 1.0.42 which is from August 2023. After updating it ot 1.0.62 which is from Sept 2024, we realized that FF values has changed to ‘true’ !! Is this a normal issue? Has there been something changes in between 0.42 to 0.62 ? If so which version exactly? Now, we are sort of afraid to update the SDK because we have other experiements and we don’t want users to lose the feature they have. Anyone faced similar issue? Thanks in advance 😌

Hi, @fancy-winter-56560. Let us check that and we will get back to you.

Hey @calm-dog-24239 , I’m suspicious of this PR that came with 1.0.43. Seems like new hashing versions are inteoduced.

Hi, @fancy-winter-56560. The feature flag value is completely parsed from the Growthbook server response, so it’s impossible for the SDK to change the value to the opposite. Could you please check if there are any restrictions for iOS users in the configurations?

Somehow GrowthBook put one of our experiments under hashing version 2 even though our swift sdk is still at 1.0.42 ( which doesnt suppor hashing version 2).So basically our all the other SDKs (Java and Kotlin) are using hashing version 2 and swift is using version 1 hence the situation occurs. We don’t know why GrowthBook assigned hashing version 2 for out experiement. Can you give me some details how hashing version is assigned ti certain experiments? @calm-dog-24239

Hi, @fancy-winter-56560. Yes, you were right. We reproduced that bug and tomorrow we will merge pull request with that fix. Thank you for your information. We will write asap after we will do that.

Hi @calm-dog-24239 , thans for the response and confirming it! Is this fix going to be in Swift SDK or in your services? Asking because I want to understand if it will effect our running experiements. Trying t understand if assigned hashing versions (of any SDK) will change or not.

This fix will be in Swift SDK. We will write as soon as it will be available.

any news about this @calm-dog-24239 ?

@calm-dog-24239 One concern we have even if this was fixed on swift sdk side is that when we update the sdk from 1.0.42 to a newer version, those users' test group might change because we always have running experiments with v2 hashing version and swift sdk will start assigning with v2 instead of v1 after the update. Is is possible to do a fix on the server side so that 1.0.42 is correctly considered as not supporting v2 and all new experiments are created with v1?

Hi, @fancy-winter-56560 and @rich-apple-1028 let me check it with team. I will write asap.

@calm-dog-24239 New experiment I just created defaulted to v2