Solved Manifest V3 - service worker inactive

klngg

The problem is with the new service worker which replaced background script .
I made multiple tests and workarounds but without success.
The results: service worker is started only when the browser starts. It is working for few seconds and then goes to inactive state .
This is the expected behaviour. Then the bug occurs.
The service worker never wake up again and we cannot start it anymore except with browser restarting.

There is no such an issue on the other browsers.

Tested on Vivaldi 4.2 and older.

klngg

I`m very pleased to tell you that this bug is fixed from Vivaldi (4.3.2439.63) and now the extensions with manifest V3 works normal in Vivaldi.

Thank you for your help @DoctorG

klngg

Again there is no solution for the bug with the extension manifest V3.

The problem is with the new service worker which replaced background script .

Service worker is started only when the browser starts. It is working for few seconds and then goes to inactive state.
This is the expected behaviour. Then the bug occurs.
The service worker never wake up again and we cannot start it anymore except with browser restarting.

There is no such bug on all other major browser.

Do you aware of this problem?

luetage

@klngg You will have to wait this one out. Background scripts won’t be deprecated all too soon.

klngg

Yes, I know, but both version of the manifest are working pretty well on all Chromium based browser. Vivaldi supports Manifest version 3 as well, but there is only one bug in the updating of the state of service worker. They only need to fix this issue.

DoctorG

@klngg Any real testcase for a check?

klngg

@doctorg
I deployed my new extension with MV3. To test the problem you should:

Install the extension.
Open 'google.com'.
Open the extension.

First you will see that at the beginning when the service worker is active, the extension popup works, after few seconds service worker goes to inactive state and the extension stops.

To start again the service worker you should restart the browser and to check again.

Normal behaviour: every time when you click on the extension and the popup appears on the screen, service worker should change its state to active.

Test extension in Chrome Store:
https://chrome.google.com/webstore/detail/visual-debug/kihnobiijiigaopmckagnbabbemopjff

I`m available If you need more information or some testing code.

DoctorG

@klngg Is this VB-78858 "Can't load chrome extension in developer mode - "Service worker registration failed"" - confirmed bug.

klngg

@doctorg Yes, maybe it is the same, but I cannot see any details for VB-78858.
I have submitted a new bug report - VB-83096.

DoctorG

@klngg said in 4.2 will arrive soon – Vivaldi Browser snapshot 2406.21:

VB-83096

VB-83096 is a duplicate of VB-78858.

klngg

@doctorg Is there any chance this bug to be fixed soon, because I have multiple extension on Chrome Store with more than 300 000 users and I cannot upgrade to Manifest V3, because the extensions stop working for Vivaldi users?

DoctorG

@klngg said in 4.2 will arrive soon – Vivaldi Browser snapshot 2406.21:

Is there any chance this bug to be fixed soon

I do not know, but i try to ping a dev, sometimes that helps.

klngg

I`m very pleased to tell you that this bug is fixed from Vivaldi (4.3.2439.63) and now the extensions with manifest V3 works normal in Vivaldi.

Thank you for your help @DoctorG

RickKerobski

@klngg hello, I have a similar problem. Have you managed to run the worker in the background all the time?

This completely breaks the logic of my extension.
Tell me how to keep the worker in the background constantly?

klngg

@rickkerobski persistent background script is not possible anymore. You must change your background logic and to store your data in storage. Then on each call to background script your service worker will start from the beginning and must retrieve your data from that storage. Please check this tutorial.

//MODEDIT: fixed URL