Hi, @brief-honey-45610 we’ve addressed the issue of calling the trackingCallback twice, and now it’s functioning properly, only being invoked once. This change is currently under review, and we’ll proceed with merging it after the pull request changes are approved.

Thank you, Maxim 🙂 Can you link me to the PR please?

Hi, @brief-honey-45610 here is link to the pull request: https://github.com/growthbook/growthbook-swift/pull/46

We have also released the latest version 1.0.45, which fixes this issue.

Thank you!

I am running into an issue using the latest Swift SDK (1.0.46). If I don't have

backgroundSync

set to

true

when configuring the

GrowthBookSDK

no features are returned. Dropping back to version 1.0.44 (after changing my setup code) everything works as expected.

Hi, @bright-pharmacist-73946 we will check that and write update about that.

Hi @bright-pharmacist-73946, could you please provide additional information about this issue? We've conducted multiple tests, and each time we received features whether background sync was set to true or false. Additionally, in this version, we have fixed the issue with the tracking callback, which now runs only once per experiment.

Hi, @bright-pharmacist-73946, we also checked these two versions with the team, and we found features in 1.0.44 and in 1.0.46. However, we also identified one thing that could explain why this occurred. In the new version of the iOS GrowthBook SDK, we changed its initializer. Please pay attention to the new way to initialize the SDK. Now you have to add the API key and client key separately, without including “api/features” or “/sub/“. Just input your API host, for example: “https://cdn.growthbook.io”, and your client key, which should resemble this format: “sdk-YUtMizl6frtpEyL”.

Hey Maxim, thanks for the follow up. I will check this again today, but had the

1.0.46

code updated to use the

apiHost

and then include the

clientKey

separately. As I said, it worked briefly when I had

backgroundSync

enabled. In terms of the new initializer, that change came as a bit of a surprise and broke our builds when we did the swift package update since the initializer version used in

1.0.44

was completely removed.

Hi All, Was just exploring the swift sdk. Does the SDK support real time updates without manual fetch?

Hi, @quaint-lion-98240, yes, the Swift SDK supports real-time updates without manual fetching.

Thank you for the confirmation @calm-dog-24239.

Hi @most-spoon-61816, would you be able to take a look at this issue soon? cc @brash-summer-91570 https://github.com/growthbook/growthbook-swift/issues/50

Hi @brief-honey-45610 Sure, we will take a look

Hi, @brash-summer-91570. In which version of the SDK did you encounter that issue, and which platform are you using (iPhone, iPad, Mac, Apple Vision)?

Hello everyone Is there a way to implement a realtime feature listener? i want to be able to toggle a feature on/off for all users at once, currently iam using the

refreshHandler

call back in the GrowthBookBuilder initialiser to listen on changes, whenever it is called i use the

isOn

function on all my feature keys that i want, but after some minutes in a session, it stops sending call backs in refreshHandler, why is that and is there a way to implement what i need?

Hey Team, a customer is encountering iOS SDK crashes when starting an experiment, they can't decode the response because the "isActive" parameter has no value (screenshot below). They are using remoteEvaluation. How do they debug these crashes?

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 everyone. I've implemented GrowthBook into my tvOS Swift application, and feature flags work perfectly, but I'm having trouble getting experimentation to work. Whenever I create an experiment and do attribute targeting, the

trackingCallback

is never called, and the experiment doesn't work. The only way I can get it to work is by using the

user_uuid

attribute. Then the callback is called and the experiment works fine. I've tried creating many attribute types and seeing if they will match, but none work. Does anyone have any suggestions on what to do?

if let growthBook = growthBook {
            self.growthBook = growthBook
        } else {
            let builder = GrowthBookBuilder(
                apiHost: apiHost,
                clientKey: clientKey,
                attributes: [
                    // None of these work
                    "platform": "tvos", // enum attribute type
                    "platform_is_tv_tvos": true, // boolean type
                    "is_tvos": "true" // string type
                    // If I use the user_uuid experimentation works
//               "user_uuid": "3A662C6E-0A43-4BFB-B691-B25D685CD409"
                ],
                trackingCallback: { experiment, result in
                    print("[Debug] Experiment \(experiment.key) assigned variation \(result.variationId) with result \(result.value)")
                }
            )
            let sdk = builder.initializer()
            self.growthBook = GrowthBookSDKWrapper(sdk: sdk)
        }

Hi Fernando. Awesome that you got feature flags up and running on your tvOS app! For the experimentation part, I think things are working as intended. Experiment assignment, which variation a user sees, depends on the assignment attribute (the

user_uuid

). If that's not present, then the experiment can't run and the CB won't fire. You can change what the assignment attribute is (but it should be something unique).

Hi Team, a customer has asked why dont we add "features: Data?" to initialiser with API key, in that case SDK will start with cached data for the Swift SDK? Attached is their usecase for this feature.

Hi there, I noticed that the SDK sends the request to the

/sub/sdk-*

endpoint and the server returns a 401 error:

{
  "status": 401,
  "message": "No authorization token was found"
}

The SDK was initialized with

backgroundSync: true

setting. Now we can do a release without this option, but can you help sort out the problem please? SDK: 1.0.62

apiHost: apiHost, // we use CloudFlare CDN, but see the same error with GB's CDN
clientKey: clientKey,
encryptionKey: nil,
attributes: attributes,
trackingCallback: { experiment, result in
    trackingCallback?(experiment.key, result.variationId)
},
refreshHandler: nil,
backgroundSync: true,
remoteEval: false

Hi, can anyone tell me ,if when u use

setForcedVariation

function, the trackingCallback is called after getting the results of the experimento via forcing the variation?

Hi Team, 2 of our biggest Enterprise customers are requesting error handling and retry logic in the Swift SDK related to this GitHub issue. The customers use case is in the screenshot. Is there a workaround solution that we can provide or is this on the roadmap?

Hi Team 👋🏻 We received an issue related to the Swift SDK tht we could use your help looking into. Summary Inconsistent behavior in the iOS (Swift) SDK when evaluating a client-side feature flag with Force Rules. Setup: • Two feature flags: a backend and a client one. • Both had identical Force Rules: a. Force default value for holdout Q2 control group b. Force default value for holdout Q2 test group c. Force test value for specific iOS user ID d. Force test value for specific Android user ID These test user IDs are confirmed to not be in the holdout group, and simulating their assignments using Python and iOS SDKs always returned "General Population." In the iOS app, the backend variation appeared as expected, but the client-side variation did not — it returned the control (False) value: • Backend flag returned expected test value in all cases (Python SDK, Swift SDK, Android app). • Client flag: ◦ ✅ Python SDK: value =

True

, source =

Force

◦ ✅ Android app (Java SDK): value =

True

◦ ❌ iOS (Swift SDK): value =

False

, source =

cyclicPrerequisite

The

cyclicPrerequisite

source in GrowthBook means a cycle was detected in feature prerequisites (i.e., a feature depending on itself). Evaluation is halted to avoid infinite loops. However, no prerequisites were defined in this setup. This source value was unexpected and only appeared in the Swift SDK. Can you investigate why the Swift SDK is returning

cyclicPrerequisite

for a client feature flag that: • Has no prerequisites • Is correctly forced to a test value via Force Rules • Returns the correct result in other SDKs (Python, Java)? Thanks!

Hi Team, for the bucketing issue that is mentioned here for Android, is the same also happening for iOS?

Hi Team, good morning. A customer has queried when this PR will go live? Is there an update that I can provide for them?

Hi Team, a customer is facing an issue where users are not being served the forced rule but the experiment rule. They have confirmed that in their workflow "init must be done with empty/dummy parameters, but we are updating them later when we know user's details" which would lead to the user not matching the force rule’s targeting at evaluation time. To debug this I thought loggingGrowthBook.getAttributes() immediately before evaluating the feature to confirm the attributes satisfy the force rule condition and if not setting them earlier would resolve this, but just found that getAttributes() does not exist on this SDK, is that true? Is there are alternate solution in swift equivalent to getAttributes() ? Also are there any methods for them to force re-evaluation once the attributes are set?

Hi team. We are mid evaluation of growthbook and we have encountered an issue in the swift SDK for feature flags. The

backgroundSync

setting does seem to trigger the refreshHandler, however subsequent checks of the feature flag show that the flag hasnt been updated. Details have been logged here. Any help you can give us would be greatly appreciated Thread in Slack Conversation