Re: [crx] Digest for chromium-extensions@chromium.org - 5 updates in 3 topics

[Jo Tremblay]

Le dim. 17 oct. 2021 à 10:02 AM, <chromium-...@chromium.org> a écrit :

chromium-...@chromium.org

Google Groups

Topic digest
View all topics

• Getting "This extension may have been corrupted" error for my extension after updating to new version - 3 Updates
• After updating to the latest version, my extension got this "this extension may have been corrupted" and users are forced to reinstall. How to solve this? - 1 Update
• Use case for persistent background scripts & other concerns - 1 Update

Getting "This extension may have been corrupted" error for my extension after updating to new version

Code Plugin <codeplug...@gmail.com>: Oct 17 12:11AM -0700 Hi folks,   I have a chrome extension https://chrome.google.com/webstore/detail/codeplugin-generic-versio/lbkdbeojajhofdpbkkideaoipoejhedp   Last week i made small changes and updated the version in manifest from 0.0.0.1 to 0.0.0.2   now many of users are complaining about extension getting corrupted error - "This extension may have been corrupted"   I tried to repair it, but it just gets removed from extensions tab if i tried to add it back again, it shows another error "Cannot move extension directory into profile"   Someone please suggest.   Thanks

Artem Harutyunyan <ar...@bardeen.ai>: Oct 17 12:26AM -0700 Try using CRX Viewer ( https://chrome.google.com/webstore/detail/chrome-extension-source-v/jifpbeccnghkjeaalbbjmodiffmgedin?hl=en) to inspect the main.crx of the package in the developer dashboard. I had an issue once where some of the files were missing from my extension due to extra './' that was getting added during the archive generation on my build machine (it was borked, but still got published). Not saying this necessarily is the issue in your case, but after inspecting the .crx file you will at least know whether your users are getting what you think they're getting :).   HTH Artem.   On Sun, 17 Oct 2021 at 00:11, Code Plugin <codeplug...@gmail.com> wrote:

Code Plugin <codeplug...@gmail.com>: Oct 17 12:48AM -0700 I just checked in this CRX Viewer and i cannot able to see any issues as such with my extension.   On Sunday, October 17, 2021 at 12:56:30 PM UTC+5:30 Artem wrote:

Back to top

After updating to the latest version, my extension got this "this extension may have been corrupted" and users are forced to reinstall. How to solve this?

Code Plugin <codeplug...@gmail.com>: Oct 16 11:54PM -0700 Am also facing the same issue. Did you got lucky to find solution to this?   On Saturday, June 27, 2020 at 9:44:28 AM UTC+5:30 HighCode Extension wrote:

Back to top

Use case for persistent background scripts & other concerns

"hrg...@gmail.com" <hrg...@gmail.com>: Oct 16 11:21AM -0700 There's so much stuff that needs to be added to a service worker in order for it to be useful... I can already see that after several years of patching it and extending it, we'll end up back at the beginning... which we should have never left, a persisten background page.   rdevlin said the following at https://crbug.com/1225642#c9 "*I'd also generally say that unless there's a good reason a web API should *not* be exposed to a worker, we should lean towards it being exposed*."   So now they want to solve the SW problems by changing the standard. This is in itself a dubious endeavour, but even if you push it to the limit, there only so much you can do. You won't be able to expose DOM APIs to a worker because that requires access to the main thread. Unless they also plan to turn the service worker into a main-thread-like context, in which case it becomes a background page.   This whole idea of getting rid of the background page is just sad.   On Saturday, October 16, 2021 at 8:32:33 AM UTC-3 Carlos wrote:

Back to top

You received this digest because you're subscribed to updates for this group. You can change your settings on the group membership page. To unsubscribe from this group and stop receiving emails from it send an email to chromium-extens...@chromium.org.