Extension is disabled with an error - This extension may have been corrupted after upgrade to chrome 64
Reported by
chrome-a...@ironsrc.com,
Jan 25 2018
|
|||||
Issue descriptionChrome Version : 64.0.3282.119 (Official Build) (64-bit) OS Version: 6.1 (Windows 7, Windows Server 2008 R2) What steps will reproduce the problem? 1. Install the extension from the web store (https://chrome.google.com/webstore/detail/search-manager/pilplloabdedfmialnfchjomjmpjcoej) or via registry 2. Update chrome version from v63 to 64 3. Open a NT What is the expected result? The extension would stay enabled What happens instead of that? Extension is disabled with an error "This extension may have been corrupted"
,
Jan 29 2018
Reporter@ Thanks for the issue. Tested this issue on Windows 10 and 7 on the reported version 64.0.3282.119 and unable to reproduce this issue by following the steps mentioned in the original comment. On Installing the Extension - Search manager on M63 build and upgrading Chrome to the latest Stable M64 build - 64.0.3282.119, can observe that the extension is enabled and no error message is seen on the Extension icon. Request you to please retry the issue on a new chrome profile without any flags/extensions and update the thread with the observations. Thanks..
,
Jan 30 2018
Hi, We managed to reproduce it a lot of times with different extension. All of them had a white background in NT in their CSS.
,
Jan 30 2018
Thank you for providing more feedback. Adding requester "susanjunia.boorgula@techmahindra.com" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jan 31 2018
Unable to reproduce the issue on Win-7 and Win-10 using chrome reported version #64.0.3282.119 and latest canary #66.0.3335.0. Following are the steps followed to reproduce the issue. ------------ 1. Installed the extension from the web store (https://chrome.google.com/webstore/detail/search-manager/pilplloabdedfmialnfchjomjmpjcoej) or via registry 2. Updated chrome version from v63 to 64 3. Opened a New tab page. 4. Observed that the extension retained without any issues. reporter@ - Could you please check the issue on latest canary #66.0.3335.0 by creating a new profile without any apps and extensions and please let us know if the issue still persist or not. Thanks...!!
,
May 24 2018
As there is no response from the reporter from so long, closing this issue as Won't fix. @Reporter: Please feel to raise a new issue if issue is still seen. Thanks! |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by krajshree@chromium.org
, Jan 29 2018Labels: Needs-Triage-M64