"This extension violates the Chrome Web Store policy." error after I published a new version.

2,404 views
Skip to first unread message

Logalty Desarrollo

unread,
Jul 10, 2022, 11:01:21 PM7/10/22
to Chromium Extensions
Comming from support thread: https://support.google.com/chrome/thread/168853302?hl=en&authuser=1 

Recently our company's Chrome extension was flagged for Purple Potassium (requesting tabs permission when it wasn't required). We updated the extension, submitted for review, and the new version was approved and published.

However, even after installing the new extension, Chrome will eventually (after a few minutes) disable the extension again with the "This extension violates the Chrome Web Store policy." error. 

Does anyone know how or why this happens?

Lukasz Chojnowski

unread,
Jul 11, 2022, 10:36:31 AM7/11/22
to Chromium Extensions, logaltyde...@gmail.com
After some digging through Chromium source code. I have found the issue. It looks like the Safe Browsing feature is blocking the extension. There is probably a bug in Chrome Web Store that prevents marking an extension as safe after it was taken down.

Test:
Go to  "chrome://settings/security" and set Safe Browsing to: "Enhanced protection".
You will get a warning when installing the extension.

This will cause that the extension won't be disabled any more:
Go to "chrome://settings/security" and set Safe Browsing to: "No protection (not recommended)".

The problem is that there is no form to report an extension as safe:

I have reported the problem on "Chrome Web Store One Stop Support":

There is also a Chromium ticket for this issue:
Issue 1342241: Reinstated extension gets automatically disabled

Logalty Desarrollo

unread,
Jul 11, 2022, 12:17:05 PM7/11/22
to Chromium Extensions, Lukasz Chojnowski
After 10 days the problem has solved itself. The plugin is no longer marked as malicious and the new version is stable.

Lukasz Chojnowski

unread,
Jul 14, 2022, 9:21:41 AM7/14/22
to Chromium Extensions, logaltyde...@gmail.com, Lukasz Chojnowski
In our case the issue has been resolved after we have reported it to Chrome Web Store support: https://support.google.com/chrome_webstore/contact/one_stop_support
It took more than 2 weeks, but now the extension is working fine.

Reply all
Reply to author
Forward
0 new messages