You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to integrate Amplitude into background scripts of Chrome Extension manifest V3. Amplitude Init fails with the following trace, upon digging into it, its the following error.
This is expected to fail as the manifest V3 version of Chrome Extension background scripts don't have access to DOM, and they are run as service workers, which explains the issue. I would like to know if there is a way to integrate Amplitude where window/document objects aren't present. Its really critical for us to integrate Amplitude into the background scripts, as most of the important action happens there. The recommendation in the error message to use @amplitude/node wouldn't work in our case too, as its not a node environment. Kindly assist if there is a solution or any workarounds for the problem. Thanks in advance.
The text was updated successfully, but these errors were encountered:
We just released v8.14.0 which includes support for web worker environments. We'd totally appreciate if you can provide any feedback on this new feature.
Summary
I'm trying to integrate Amplitude into background scripts of Chrome Extension manifest V3. Amplitude Init fails with the following trace, upon digging into it, its the following error.
This is expected to fail as the manifest V3 version of Chrome Extension background scripts don't have access to DOM, and they are run as service workers, which explains the issue. I would like to know if there is a way to integrate Amplitude where window/document objects aren't present. Its really critical for us to integrate Amplitude into the background scripts, as most of the important action happens there. The recommendation in the error message to use @amplitude/node wouldn't work in our case too, as its not a node environment. Kindly assist if there is a solution or any workarounds for the problem. Thanks in advance.
The text was updated successfully, but these errors were encountered: