In the context of the introduction of action metrics for MV3, an e2e test was implemented on this PR.
When building the app through yarn start:mv3, adding a new account, and immediately terminating the service worker manually, the service worker restarts as expected. Upon later inspection of the console, "Metamask initialization complete" was visible, but we can't, unfortunately, survey network requests for segment retroactively because the console is closed.
When building the app through yarn build:test:mv3 and running that test, the service worker does not restart after being terminated. The app eventually crashes, and the test fails after it times out.
However, if the console is opened shortly after the service worker is terminated in the test, the service worker does restart.
In the context of the introduction of action metrics for MV3, an e2e test was implemented on this PR.
When building the app through
yarn start:mv3, adding a new account, and immediately terminating the service worker manually, the service worker restarts as expected. Upon later inspection of the console, "Metamask initialization complete" was visible, but we can't, unfortunately, survey network requests for segment retroactively because the console is closed.When building the app through
yarn build:test:mv3and running that test, the service worker does not restart after being terminated. The app eventually crashes, and the test fails after it times out.However, if the console is opened shortly after the service worker is terminated in the test, the service worker does restart.