Error downloading the updated version.

[Robbi]

Hello folk,

sometimes I get this kind of error when an extension is updated.

This time it happened live in front of my eyes. I knew the new version was approved, I opened the browser and went to the extensions page.

Without even pressing the "update" button, the extension updated itself and the "Errors" button appeared in red.

I can assure you that I don't have any files inside the package that start with an underscore.

I don't know if that could be of any relevance, but the extension was disabled at the time.

However, the extension has not had any damage and appears to be working correctly.

It only happens with updates from the CWS.

Has anyone had this kind of experience?

[Robbi]

This error message recurs with each update.

Has anyone ever seen this error message?

[Jackie Han]

It could be a browser or Web Store bug. So I suggest reporting it to both Chromium bugs and CWS One Stop Support.

--
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/15f4e24c-13bf-4bae-9987-3e0456d139c3n%40chromium.org.

[Robbi]

thanks, for now I have only contacted the CWS One Stop support.

As soon as I get a reply I will inform the group

[Robbi]

No way. The support team was quick to answer me but more than a response it was a bounce.

I was in fact diverted to this group and S.O.

Amen, we'll get over it.

In the last few days, however, I have noticed that in my manifest.json there is both "options_ui" and "options_page" and the latter would seem deprecated. Perhaps this is the origin of my problem.

[Simeon Vincent]

Are you trying to load an unpacked extension? If not, can you share the ID of the extension?

Simeon - @dotproto

Chrome Extensions DevRel 

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/2f937b7a-4700-4eb0-9df7-8cada068d61fn%40chromium.org.

[Robbi]

Hi Simon,

It does not happen loadind unpacked extension or dragging crx file onto extension page.

It only happens with updates from CWS (and not always).

I made sure you that I don't have any file or folder inside the package that start with an underscore. I also checked for hidden/system files, which are not normally listed in an explorer window.
This happens both with the manual update (by pressing the "update" button) and with the automatic one (dictated by the browser times)

The ID of the extension is:  hifbilohhmckmnkaclpnnmepkogjcfhc

Thank you

[Robbi]

It keeps happening with both these extensions (hifbilohhmckmnkaclpnnmepkogjcfhc  and kffpbnnhonkfnnjcbgeegicphjkoenaj) but the strangest thing is that it happens always with Chrome Dev and Brave browser.

[Deco]

It's likely a caching issue within the browser, updating an extension will only modify files with changed values, remove the extension from the developer panel entirely and try re-adding it again.

Cheers,
Deco

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/5ec87a20-303a-474e-a776-81b2ba3eaaa3n%40chromium.org.

[Robbi]

I will try to reinstall the current version of the extension just before the next update.

Please note that I have Iron, Chrome Dev, Chrome Canary and Brave installed on my PC and the first 3 browsers are in sync with the same account.

On SRWare ron and Chrome Canary I have never had such problems.

[Jackie Han]

I see this error message more than one time.

2022-12-29

2023-02-20

Cannot load extension with file or directory name _metadata. Filenames starting with "_" are reserved for use by the system.

This error message locate at https://source.chromium.org/chromium/chromium/src/+/main:extensions/common/file_util.cc;l=385

I checked the location of extension installation: /Library/Application Support/Google/Chrome/Default/Extensions/

There are only two dictionaries that start with "_", i.e. "_locales" and "_metadata". Of course, "_metadata" is generated by Chrome or CWS, not in my source code.

But I didn't find this error message to have any real effect on the extension.

--

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/6b43ffb7-21fa-433e-a538-9f4cf4abfef6n%40chromium.org.

[Robbi]

ok, now there are at least two of us having the same problem.

Maybe someone will start digging into it.

However, it doesn't always happen to me (let's say it happens once in three)

I think it's impossible, at least for us developers, to use the debugger by inserting breakpoints.

[Oliver Dunk]

Hi Jackie,

I think that's this bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1061292

Definitely one that would be nice to fix, as you say this is a folder generated by Chrome (specifically when using the declarativeNetRequest API), so not something you're doing wrong.

I'll make sure to flag it again with the team.

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

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/CAAgdh1JSAPrPUSNg2Z3cj%2Bjd-%3DA6XHq4vQX%2BZ7aoKz5YU%2Bskew%40mail.gmail.com.

[Robbi]

It would seem this issue never invalidated the service worker though.

[Jackie Han]

Ok. I starred the issue. But I don't use dNR API in my extension.

[Robbi]

@Oliver Dunk
this kind of error message appears only during the updating from CWS (both manual or auto)

[Oliver Dunk]

@Jackie: Interesting. It's possible this folder is also generated by some other things. I don't know any off the top of my head but that's good to know.

@Robbi: I've also seen it for reloads on my side but thanks for the heads up. It's good to know when you're hitting this.

I'm hopeful that despite us all seeing this in slightly different places there will be one fix for all of us! Will keep the bug updated.

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

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/987b1473-d28a-4bc3-b85a-3a7d3488b62fn%40chromium.org.

[Jackie Han]

Yes, it happens when the extension updates from CWS.