Re: [crx] Chrome Store vs Manually installed

[Oliver Dunk]

Hi Froi,

Generally both installation methods are very similar, but it's possible there is a difference that is causing issues.

One common issue for example is that `declarativeNetRequest.onRuleMatchedDebug` is only available to unpacked extensions.

Are you able to share your extension? And could you elaborate on if the extension fails to load entirely, or if a specific feature is broken?

Oliver Dunk | DevRel, Chrome Extensions | https://developer.chrome.com/ | London, GB

On Fri, Jun 7, 2024 at 10:53 AM 'Froi Mercade' via Chromium Extensions <chromium-...@chromium.org> wrote:

Hi everyone,

We recently uploaded an extension using Manifest V3 to the Chrome Web Store. While the extension works perfectly when installed manually in developer mode, it does not function as expected when installed from the Chrome Web Store. Could the differences in policies and restrictions between these two installation methods be causing this issue? Any insights or guidance on how to address this would be greatly appreciated.

Thank you!

--
You received this message because you are subscribed to the Google Groups "Chromium Extensions" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-extens...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/34a8b2db-bf1e-4ab5-aece-46861ba0e28en%40chromium.org.

[Froi Mercade]

Hi Oliver,

We have a service worker in our extension that goes to sleep every 0.5 min. We run alarm every 0.4 min for keeping it alive. We tested this approach locally with dev build and it works. When we release it to production it seems that is not working... Should this work for keeping it alive or it can be terminated anyway? Do you recommend another approach?

Many thanks for you support.

[Oliver Dunk]

Hi Froi,

Setting the alarm interval to a period of less than 0.5 is only supported in unpacked extensions, and in published extensions there is different behavior: https://developer.chrome.com/docs/extensions/reference/api/alarms#method-create

Generally keeping the service worker alive is undesirable - if you're able to share your use case, we might be able to help find an alternative.

Otherwise there are some options here which might work for you: https://developer.chrome.com/docs/extensions/develop/migrate/to-service-workers#keep-sw-alive

Oliver Dunk | DevRel, Chrome Extensions | https://developer.chrome.com/ | London, GB

[Alexei]

>Setting the alarm interval to a period of less than 0.5 is only supported in unpacked extensions

This is such a strange limit to keep around given that most extension APIs also reset the idle timer in Chrome.

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/CAOsQqBmRgfuoKFcLrxSum66DAxXsy-ef8EzVRROaA9gwKAXx6A%40mail.gmail.com.

[Jackie Han]

@Oliver, this thread reminds me of a suggestion I made earlier to add a document that explains this question. I just filed an issue for Chrome document.

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/CAOcx_p_3AxcdvqUT-anfV%3DstFe_qvUPA07JzrE%2B0ee8LdSA-eA%40mail.gmail.com.

[Froi Mercade]

Many thanks Oliver, your feedback was really useful.

As we had lost many time around this issues and still not uploaded a
stable version to the Chrome Store, we are concerned we are beyond the
MV3 deprecation period. Do you have any last news related to the final
date?

Thanks again.

--

Froi Mercade | Director, Engineering fmer...@usertesting.com UserTesting | Human understanding. Human experiences.

[Froi Mercade]

Many thanks Oliver, your feedback was really helpful. We will 

We will follow your indications and adjust to your provided guidelines. But we had lost time trying to solve this issue, and this is for our MV3 version. Do you have any news related to the final deadline? We are worried about it. 

Thanks again. 

[Oliver Dunk]

This is such a strange limit to keep around given that most extension APIs also reset the idle timer in Chrome.

 We're actually looking at removing it (WECG mention). This is still on my list of things to look at :)

@Oliver, this thread reminds me of a suggestion I made earlier to add a document that explains this question. I just filed an issue for Chrome document.

Thanks Jackie! I think that's a nice idea, appreciate you opening the bug.

As we had lost many time around this issues and still not uploaded a stable version to the Chrome Store, we are concerned we are beyond the MV3 deprecation period. Do you have any last news related to the final date?

I'm not sure if you saw it already but we posted an update on the Chromium blog last week: https://blog.chromium.org/2024/05/manifest-v2-phase-out-begins.html. We have started some experiments in non-stable channels, but you can definitely still upload an MV3 build on the Chrome Web Store when you're ready. I hope that helps but let us know if you have any other concerns.

Oliver Dunk | DevRel, Chrome Extensions | https://developer.chrome.com/ | London, GB

[Froi Mercade]

Hi Oliver,

We had changed our approach and followed your guidelines, we worked around the clock on the development.  We are testing it again, so it will take most of the week, as we have changed core parts of the extension. We are targeting the release next Monday the 17th. We are concerned about the MV2 deprecation deadline. Is it possible to release it next Monday or is the deprecation deadline date before?

Many thanks for your help.

Regards,

Froi.

[Oliver Dunk]

Hi Froi,

We have already started showing warnings to users with MV2 extensions in Canary and Dev, and those will continue to roll out to a larger set of users.

We won't start disabling any extensions until at least Chrome 127, which reaches beta tomorrow (schedule). It won't reach stable until July, so you should be ok there. If you care about other channels there is a risk you may be impacted. I don't expect any disabling will have reached a significantly large set of users by then, but I don't want to make any new promises beyond what we have already stated here.

In any case, you will be able to update your extension for some time yet as we will support that until Manifest V2 is no longer supported for all users.

Oliver Dunk | DevRel, Chrome Extensions | https://developer.chrome.com/ | London, GB

[Froi Mercade]

Many thanks Oliver!