andreseleq14 / scriptblock

Automatically exported from code.google.com/p/scriptblock
Other
0 stars 0 forks source link

Changing the default password causes "Extension has been corrupted" #17

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Open Extensions page in Chrome and find ScriptBlock, verify everything's fine
2. Change default password in CHANGE__PASSWORD__HERE.js file
3. Reload Extensions page in Chrome and find error about extension being 
corrupted, with option to repair (which basically reinstalls the extension and 
resets to the default password)

What version of the product are you using? On what operating system?

ScriptBlock: 1.0_0
Chrome: Version 39.0.2171.65 (64-bit)
OS: Ubuntu

Original issue reported on code.google.com by john...@gmail.com on 25 Nov 2014 at 6:07

GoogleCodeExporter commented 9 years ago
This also affects the Windows 7 environment.

ScriptBlock: 1.0_0
Chrome: Version 39.0.2171.71 m
OS: Windows 6.1.7601, a.k.a. Windows 7

Original comment by nfo...@gmail.com on 26 Nov 2014 at 3:37

GoogleCodeExporter commented 9 years ago
I am having the same issue. Actually noticed it first with the original 
NotScripts extension and when I couldn't get that working again I moved to 
ScriptBlock. Immediately after changing the PW and restarting I got a 
"extension may be corrupted" warning as well.

ScriptBlock: 1.0_)
Chrome: 39.0.2171.71 m
OS: Win 7 Pro 64 bit

Original comment by chris.bu...@gmail.com on 28 Nov 2014 at 10:28

GoogleCodeExporter commented 9 years ago
I got the same error. Even if I put back the original password, the extension 
is still marked as corrupted.

ScriptBlock: 1.0.0
Chrome: 39.0.2171.95
OS: Ubuntu 14.04

Original comment by ivan.nov...@gmail.com on 14 Dec 2014 at 7:06

GoogleCodeExporter commented 9 years ago
I have the same issue as well as my whitelist not syncing.

ScriptBlock: 1.0.0
Chrome: 39.0.2171.95
OS: Windows 8.1

Original comment by lee.east...@gmail.com on 17 Jan 2015 at 1:39