CC @freezing-postman-69602 as this is for one of our large strategic customers

Hi @calm-dog-24239, the customer responded that they can't update because "cannot since we havent use that version of flutter and dart"

Could you please ask the client what version of dart and flutter they are using? It will really helps us.

Hi @flaky-noon-11399. We have prepared alpha release for this client here. Hope it will help and looking forward for your feedback.

In this release he could use SDK on the lower version of Dart and Flutter.

The

refreshHandler

is expected to be called whenever the GrowthBook SDK fetches or refreshes features. • This happens during SDK initialization (when features are first loaded from the API or cache). • It also happens whenever the SDK pulls new data (for example, after flags are updated on the dashboard). The reason you are currently seeing it fire multiple times is that: 1. On app startup, the SDK may trigger multiple UI re-renders depending on how

feature()

calls are used in your app. Each of those may cause the refreshHandler to run. 2. If you are using background sync (via Server-Sent Events or polling), then each incoming update from the server will also trigger the refreshHandler. 3. With Remote Eval, background sync is not supported — features are only fetched when you explicitly call

fetchFeatures()

. In a typical setup, you should expect: • One refreshHandler call at initialization, when features are loaded. • One refreshHandler call per update (e.g. when you change a flag in the dashboard and the SDK receives the update). If you are seeing 10+ calls on initialization, that usually indicates the app is rebuilding the UI several times on startup and calling

feature()

during build. That can be optimized so the handler is only fired once per actual data refresh.

Hi @calm-dog-24239 the customer had the attached follow up:

Are there any solutions for this?

Hi @flaky-noon-11399. Here is a pull request with a solution. Looking forward for your feedback.

Hey @calm-dog-24239 the customer asked is there an ETA when this may go live? Looks like Madhu reviewed it yesterday and there's a few edits

Hey @calm-dog-24239 the customer said they experienced this on the alpha release, is this expected?

Does this solution accommodate this?

We assume that we will include those versions in the main repository, not only in the alpha branch, because it would be difficult to maintain two separate branches with all the fixes.

The fix was related to the refresh handler being triggered multiple times instead of once, so it addressed only that specific handler. As for the issue with the

refresh

/

refreshForRemoteEval

methods — according to the conversation, they’re using the remote eval functionality, and the API call isn’t happening. A possible reason might be that

remoteEval: true

wasn’t passed in the Growthbook Builder configuration, which would prevent the requests from being made. Could you please recheck if we’re passing it?

Hi @quiet-activity-40974. Could you please try this solution and let us know if it works for you? We’re looking forward to your feedback.

Could you please try this command? flutter pub run build_runner build --delete-conflicting-outputs

Sorry, we’d be happy to do it on our side, but we can’t because we don’t push generated files to GitHub. We’re looking forward to your feedback on this.

any update? @calm-dog-24239

thanks its shown that the api has called now @calm-dog-24239. and the value in the response already expected. but right now after i refresh, and trigger the sdk.feature, it will return this as source

// CyclicPrerequisite Value for the Feature is being processed
cyclicPrerequisite("cyclicPrerequisite"),

what can cause this ya? this resulting the value always null

ah its solved by using evalFeature. is there any cons using this one instead of .feature ?

Hi @quiet-activity-40974 . The issue is now fixed in the same PR. The problem was that feature() wasn't clearing the internal evaluation stack, causing false cyclicPrerequisite errors. It now works correctly. Both feature() and evalFeature() work the same way now, but feature() is the recommended method because: It's the standard API across all GrowthBook SDKsIt automatically fetches fresh features from the network if the cache has expired (background refresh)evalFeature() doesn't trigger background refreshes, so you might get stale feature values. Looking forward for your feedback.