https://www.growthbook.io/ logo
Join SlackCommunities
Powered by
Hello! Do we know what day/time v3.6 was launched?
# ask-questions
c
Hello! Do we know what day/time v3.6 was launched?
We randomly started experiencing strange issues and are trying to rule out that the launch of 3.6 has anything to do with it.
b
are you using cloud?
on clould we release features as we make them so it might not be tied to a release. can i ask what the issue you are having?
c
We are
b
what is the issue you are experiencing?
c
Stand by please...
👍 1
Growthbook is not initializing on some of our pages. This was noticed around 9pm (EDT) last night. We log an error "Failed to load growthbook" We've tested hitting the CDN directly, and that is working. No code changes have been pushed. We've checked Google Tag Manager / GA4 to see if anything has changed and there doesn't appear to be. None of the flags are loading.
b
Looks like in issue with sdk what SDK are you using?
And Version
l
There was a bug in GB's JS code:
Copy code
Uncaught TypeError: Cannot read properties of undefined (reading 'bind')
    at new e (GrowthBook.ts:133:55)
    at auto-wrapper.ts:164:12
    at auto-wrapper.ts:217:3
The support team replied that it's fixed right now:
Yes, this was a bug we discovered a few hours ago and have since fixed.
All you should need to do is hard-refresh any Browser pages that were affected. You do not need to make any code changes or anything.
c
Three sites using two different versions. 1.1.0 and 0.31.0
Running this piece of code still fails. So, not sure if it was actually fixed or not? Or was it only fixed for certain versions?
I invited my devs to the Slack workspace. They may pop on to give more info or answer any questions you might have.
l
@curved-parrot-45865 had the same issue. It's fixed now, as I've mentioned in my previous message. Try to reload your page with cmd/ctrl+shift+r
c
Also, for what it's worth, hard reloading did not fix the problem.
Still experiencing the issue.
We're also loading it with "disable cache" checked and the issue is still happening.
@late-ambulance-66508 do you work for growthbook or are you a user like me?
l
@curved-parrot-45865 I'm just a user and also spent several hours today trying to fix this bug on my side 🙂
👍🏼 1
As I understood correctly, it fails with 1.5.0 version and was fixed in 1.5.1: https://github.com/growthbook/growthbook/pull/4023
c
@brash-kite-51410 are you still available to help?
h
You should be able to hard refresh the page to bring in the latest SDK fix (auto-wrapper)
h
good afternoon friends 🙂
cat wave 1
c
We've tried that. We're still seeing the issue.
h
I work with Jeremy
c
Thanks for hopping on @happy-autumn-40938
h
sorry, I don't know anyone yet, @happy-autumn-40938 I just refreshed my page as of 1 minute ago with Disable cache and hard refresh Ctrl+F5 and still seeing an error, although I'm not sure that it's the one you posted before. I will link you to a live example
h
there is a up-to-7-day CDN cache on that URL which will clear at random times for different users. If you need an immediate fix for everybody, you can update your script to use this url instead: https://cdn.jsdelivr.net/npm/@growthbook/growthbook@1.5.1/dist/bundles/auto.min.js
h
I see I see
I'll try that, thank you
h
please let us know how it goes
our apologies for the bug
(please remember to undo this URL change after a week so that you can get the latest updates and security patches as we release them)
👍🏼 1
👍 1
c
@happy-autumn-40938 is there a way to force a cache refresh for us specifically from your end?
If we sent you our cid?
h
unfortunately no, this is hosted by a third party "jsdelivr.net" which is a common CDN for client side libs
👍🏼 1
h
Unfortunately this is not a compatible update for us. We use a self-controlled delayed GrowthBook initialization, not auto-initialization, and it looks like that broke in this new 1.5 version.
we we try using an earlier version
well, I suppose let me fix that url so it's not the auto version and see if it's still an issue in that version
nope, this is just me using what you provided directly and not paying attention to the difference between auto.min.js and index.min.js. Using the version directly does appear to fix it, thank you
h
ok, excellent. thanks for confirming
🙏 1
3 Views
Open in Slack
PreviousNext
Powered by