Closed ghost closed 2 years ago
Hi @joaomarcelofm-gyg the stack trace show you are calling some window.appboy
method from within https://cdn.getyourguide.com/tf/assets/compiled/Home-beffc979.js
before initialize
has been called (as described by the error message).
Your script susceptible to a race condition where that Home-beffc979.js
might run prior to Google Tag Manager running.
Also, I would recommend using our official Google Tag Manager templates: https://tagmanager.google.com/gallery/#/?filter=braze
Let me know if you have any additional detail to share, and we can re-open this.
@davidbielik, the error doesn't happen only once. Even after initialization by GTM, the error keeps on happening.
It'd be strange if the error happened on Home-beffc979.js
that it would keep on happening after initialization has been executed.
I sometimes see the following message, would this be related?
Appboy: Could not open indexedDB AppboyServiceWorkerAsyncStorage v5: undefined
@joaomarcelofm-gyg can you please open a support ticket by emailing support@braze.com?
We can dig into this, but will need more information like steps to reproduce, what website it's happening on, etc., and don't want to collect potentially private information in github.
Braze Web SDK Version
2.5
Integration Method
Google Tag Manager
Browser
Chrome, Firefox, Safari
Steps To Reproduce
appboy
GTM Implementation:
Expected Behavior
Braze wouldn't throw an initialization error.
Actual Incorrect Behavior
Error is thrown now only for
openSession
, but anything called on global appboy even after waiting it to be ready. We've also tried to initialize appboy every time the errors had been caught but that didn't solve the issue either.Verbose Logs
Additional Information
The error is happening to few of our customers, which makes it seem it's not an application issue. There's was no changes related to Braze loading or initilization since it started on the 16th at noon.