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
We've just upgraded our Chrome extensions to MV3 and are unable to collect analytics in our background script (service worker).
Are there any workarounds for this? I see Partytown mentioned but we're not using this tool and believe there must be a simpler solution.
Currently, the library internally writes the anon id to localStorage. This presumes the environment. Ideally, the AnalyticsBrowser could accept some kind of storage API with a getItem, setItem, removeItem API? This way we could pass it the chrome.storage.local object.
We've just upgraded our Chrome extensions to MV3 and are unable to collect analytics in our background script (service worker).
Are there any workarounds for this? I see Partytown mentioned but we're not using this tool and believe there must be a simpler solution.
Currently, the library internally writes the anon id to
localStorage
. This presumes the environment. Ideally, theAnalyticsBrowser
could accept some kind of storage API with agetItem
,setItem
,removeItem
API? This way we could pass it thechrome.storage.local
object.Something like:
The text was updated successfully, but these errors were encountered: