Hi Everyone, 🚀 GrowthBook 3.5 has landed! In this release, we focused on user experience and productivity improvements. 🛠️ Revamped DevTools Extension: Debug flags and experiments more easily with Archetype integration, Firefox support, dark mode, and event logs. 📊 Power Calculator: Uses your historical data to accurately estimate experiment run times and minimum detectable effects, enabling more precise experiment planning. 🧭 Experiment Decision Framework: Get clear nudges like “Ship now” or “Roll back ASAP”. 🔧 SDK Upgrades: Prerequisite features & sticky bucketing now in 12+ languages, plus Open Feature support. 🎨 Design System Updates: Lots of improvements to experiment and feature flag pages, and especially in dark mode. 🎙️ Join our live demo next Thursday and bring your questions. 📖 Read the full blog post for details

I just noticed and tried the new DevTools Extension for Chrome. The new features are really helpful to understand and debug rules etc. 🙌 But it seems there is a bug 😱. For me the DevTools attributes tab is showing outdated attributes. Even worse: they seem to be cached and always override the actual attributes set within my code on the SDK. I've logged the attributes I set within my code and they are clearly not the ones I see in the dev tools. Only the wrong (and hard cached) attributes seen in the devtools are taken for rule evaluation. When I completely disable the GB devtools it's working as expected and my code is the only source of truth for the attributes. I use the latest Chrome extension 1.0.3 and

"@growthbook/growthbook-react": "^1.4.1"

Chrome Version: 133.0.6943.142 (arm64 mac)

Hi @early-lawyer-87930, would you be able to share more information such as an example page, reproduction steps, or screen recording if easier? Also, to rule it out, do you have more than one SDK loaded on the page at the same time? We're still ironing out the wrinkles in the new DevTools so reports like these are very helpful. Feel free to DM me if you prefer.

Sure! I've sent you a direct message 🙂

We've patched up the bug I believe. It'll probably be a couple of days before Google approves the change.

Great to hear! Happy to test it once landed.

@kind-father-85802 what's the passcode to watch the recorded version

@wonderful-arm-27253, here's the link to the recording: