lemon-airline-30634
06/04/2025, 9:10 AMclean-city-48510
06/04/2025, 10:09 AMorange-jordan-21834
06/04/2025, 10:43 AM{ "type": "none" }
• Free delivery enabled: { "type": "delivery", "charge": 0 }
• Express delivery enabled: { "type": "express-delivery", "charge": 0 }
In production, we’re manually forcing a specific type for certain users by targeting their IDs. However, some users are still receiving the default value unexpectedly.
Technical Context
• Customer attributes are populated from DynamoDB on app initialization.
• If the app is not killed and relaunched, these attributes are not updated again.
• We use the following logic to set attributes:
js
const user = useSelector(selectUser);
const attributes = useAttributes(user); // React 19 Suspense-ready async logic
useEffect(() => {
const current = gbInstance.getAttributes();
const incomingID = attributes?.id || attributes?.adid;
if (current?.id === incomingID || current?.adid === incomingID) {
return;
}
gbInstance.setAttributes(attributes);
}, [gbInstance, attributes?.id, attributes?.idfa]);
C*urrent Problem*
• Attribute updates are not happening frequently enough, so customers are getting targeted more than once, which violates the experiment goal.
• The forced values via targeting seem to be ignored, and the default is applied in some cases.
Desired State
We’d like GrowthBook to be updated immediately after DynamoDB is updated with new customer attributes — so that customers can be accurately targeted only once.
Questions
1. What is the best practice for syncing updated user attributes mid-session or mid-app lifecycle?
2. Is there a way to "re-evaluate" the experiment exposure after updating attributes manually?
3. Have you observed any recent issues or lag in attribute sync or targeting logic?
4. Would using a unique session identifier help isolate and limit targeting to a single exposure?
This is a time-sensitive issue, so your guidance will be very much appreciated.worried-mechanic-74282
06/04/2025, 12:59 PMstale-tailor-47769
06/05/2025, 5:09 AM{
"id": "123",
" platform": "ios",
"version": "2.0.2"
}
and i added a force rule = true, with filter
{
"version": "2.0.2"
}
but when i tried to check from the backend if the feature is enable, it returns false.
const userContext = {
attributes: {
id: "123",
},
};
const isEnabled = gbClient.isOn(
"feature1",
userContext
);
any idea what's wrong? thank youbrainy-lock-72167
06/05/2025, 6:46 AMhappy-intern-85510
06/05/2025, 6:45 PMcareful-evening-52531
06/05/2025, 10:23 PMType error: Cannot find module '@growthbook/growthbook/plugins' or its corresponding type declarations.
any tips? i'm doing:
import { autoAttributesPlugin } from '@growthbook/growthbook/plugins';
...
plugins: [autoAttributesPlugin()],
...
and i'm on:
├─ @growthbook/growthbook-react@1.5.1
└─ @growthbook/growthbook@1.5.1
important-scientist-36322
06/06/2025, 4:03 PMgreen-fall-98011
06/09/2025, 8:20 AMWebhook requests sent to your endpoint include 3 headers:
•- The unique id for this eventwebhook-id
•- The unix integer timestamp of the eventwebhook-timestamp
•is it possible to add support for standardwebhook for Event Webhook too?- The signature (format described below)webhook-signature
happy-camera-75490
06/09/2025, 10:06 AMflat-night-63859
06/09/2025, 11:48 PMfresh-dawn-30305
06/10/2025, 2:23 AMnutritious-garden-91325
06/11/2025, 2:58 PM{
"name": "GrowthBook API",
"production": true,
"api_host": "<https://xyz:3100>",
"app_origin": "https:/xyz:3000",
"config_source": "db",
"email_enabled": false,
"build": {
"sha": "...",
"date": "2025-06-09T17:15:40Z",
"lastVersion": "3.6.0"
}
}
Does anyone know possible reasons behind it?little-pager-49474
06/12/2025, 12:22 PMlittle-pager-49474
06/12/2025, 1:15 PMbetter-barista-18500
06/13/2025, 6:51 AMadamant-bear-5707
06/13/2025, 9:25 AMlively-electrician-90916
06/14/2025, 3:42 PMGrowthBookProvider
- when running my tests I randomly get multiple Warning: An update to GrowthBookProvider inside a test was not wrapped in act(...).
warnings. Has anyone else had this issue? Does anyone know how to get these messages to disappear?ambitious-noon-34894
06/16/2025, 5:05 AMcreamy-magazine-78898
06/16/2025, 12:17 PMhigh-football-34214
06/17/2025, 8:16 AMelegant-solstice-68604
06/17/2025, 5:48 PMpurple-breakfast-88896
06/18/2025, 2:13 PMflaky-rain-76756
06/18/2025, 3:30 PMbetter-businessperson-31777
06/19/2025, 3:08 AMbetter-businessperson-31777
06/19/2025, 4:04 AMrapid-salesclerk-86901
06/19/2025, 2:12 PMcurved-battery-91390
06/19/2025, 4:29 PMinit
or call refreshFeatures
to "reactivate" the streaming?
Thanks!calm-balloon-91650
06/20/2025, 10:32 AMb
Will now every single user get b
? Or will only users who were part of the test get b
?