"The extension may have been corrupted"
See original GitHub issueI use Chrome canary & I have 2 profiles, on the latest version on the time of writing this issue Version 59.0.3067.0 (Official Build) canary (64-bit)
the extension is giving me this error in one of the profiles but not the other. No clue why, everything was working perfectly fine 2 days ago.

Things I tried:
- Clicking repair doesn’t help.
- Reinstalling the extension didn’t help.
- I also tried some other solutions like visiting the extensions page on chrome which will show an enable link at the top. which made it work for a bit, but once I click options it crashes again & also the icon always looks like this after doing this.

Issue Analytics
- State:
- Created 6 years ago
- Reactions:2
- Comments:10
Top Results From Across the Web
Chrome extension disabled "This extension may have been ...
It was working fine until this past weekend when the Chrome update prompted a new "This extension may have been corrupted" error.
Read more >Fix Chrome's Error: 'This extension may have been corrupted ...
Fix Chrome's Error: 'This extension may have been corrupted by malware' ... First things first, this is because of the content verification feature,...
Read more >Nearly all extensions: "This extension may have been corrupted"
The company I work at has developed an extension that takes use of the NativeMessagingHost api, and we've found that users with Chrome...
Read more >Issue, This extension may have been corrupted - Google Groups
I see three possibilities: 1) The extension has changed inadvertently (disk corruption). 2) The extension has been changed on purpose (either by someone ......
Read more >This extension may have been corrupted - Chrome 100.0 ...
Hello, The UiPath chrome extension is showing an error message “This extension may have been corrupted” for a few seconds and repairs it ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I just cloned,
npm install
andnpm run build
and loaded the unpacked extension which seems to behave perfectly fine.I’ve just updated to the latest unstable release and it works