Unexpected Behavior from analytics.reset() in Chrome Extensions

[WeaponXII]

We have been using analytics-next in our Chrome Extension for the last 2 or so months, and recently added an analytics.reset() call on user sign out. For users that sign out of our extension but keep our chrome extension installed this has been creating a new anonymousId for every tab our users visit, it seems to break client persistence and might be a bug unique to chrome extensions.

[zikaari]

What context is the analytics-next loaded in? background, content script, devtools panel?

Is the expected behaviour to NOT create an anonymous ID once they sign out, and keep it null until they sign back in?