M63 change breaking non-CWS extensions

[Gustavo Sacomoto]

Hi, 

It seems something changed on M63 causing Chrome to consider some non-CWS as corrupted (chrome://extensions show the "This extension may have been corrupted." message). 

There are more cases here:

https://productforums.google.com/forum/?hl=en#!topic/chrome/kGgLwnrDKpQ;context-place=forum/chrome

I can confirm this problem was really introduced in M63, and adding the "update_url" to the extension manifest fixes the problem. 

This doesn't seem to affect CWS extensions. My guess here is that CWS adds / overwrites the "update_url" field in the manifest when packaging the extension.

Can somebody confirm that Chrome is more stringent with the extension manifests on M63? Or is it a bug?

Cheers,

Gustavo

[Michael Giuffrida]

+proberge for content verification work that happened in M63

--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
---
You received this message because you are subscribed to the Google Groups "Chromium-dev" group.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/CANjVpsoKS%3DHbg8Vk6N6HLrbksE_wx%3D0cYU9FZWbxMrA-OV%2BLqA%40mail.gmail.com.

[prob...@chromium.org]

Hi Gustavo,

Thanks for helping bring this to our attention. 

I filed https://bugs.chromium.org/p/chromium/issues/detail?id=794219 to track the issue.

[prob...@chromium.org]

I'm looking for steps to reproduce the issue. If this is happening for your extension, please add repro steps to the bug.

Please, also provide the following information:

1. Is your extension uploaded to the Chrome web store? For example, does https://chrome.google.com/webstore/detail/extension-name/<extension-id> return a valid page?

2. The id of the extension, if possible.

3. The full manifest of the extension, with the sensitive values replaced with %VALUE%.