Problem with Chrome extension in crx file
Reported by
dangngoc...@gmail.com,
Jan 28 2018
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.119 Safari/537.36 Steps to reproduce the problem: 1. Install 2. Open webpage (for example, google.com) 3. Click on program icon (on toolbar) to switch to dark mode. Error: corrupted! What is the expected behavior? This error happens when I install extension from crx file (include: crx from store, crx - offline install). If I extract crx to a folder, and use "load unpacked extension" function, then it works normally. No error! I don't think this caused by my extension, because it works normally, but only with crx file. What went wrong? Problem with crx file. WebStore page: https://chrome.google.com/webstore/detail/super-dark-mode/nlgphodeccebbcnkgmokeegopgpnjfkc Did this work before? No Chrome version: 64.0.3282.119 Channel: stable OS Version: 10.0 Flash Version: It works with unpacked extension (unzip), doesn't work with crx file.
,
Jan 30 2018
Able to reproduce the issue on Mac 10.12.6, Win-10 and Ubuntu 14.04 using chrome reported version #64.0.3282.119 and latest canary #63.0.3226.0. This is a non-regression issue as it is observed from M60 old builds. Note: On OS-Linux, on adding the extension and opening http://google.com/ doesn't show the extension for clicking and the extension gets corrupted instantly. Hence, marking it as untriaged to get more inputs from dev team. Thanks...!!
,
Mar 2 2018
sounds like a content verification issue. proberge@, is this something you could look into?
,
Mar 3 2018
This problem is solved. The reason is the path name is capitalized. In windows, the capitalized path and non-capitalized path are same, but on Linux-based systems, they are different.
,
Mar 3 2018
Thanks for the update, dangngochoangthanh.vn@! This is still an annoying 'gotcha' for developers that we should do a better job of documenting. Unfortunately, on windows-based systems, we have limited ability to do this. Maybe it could be as part of the upload to the webstore validation, though. jawag@, thoughts?
,
Mar 23 2018
>Maybe it could be as part of the upload to the webstore validation That seems reasonable to me. +konsto would that be possible?
,
Mar 23 2018
Yes, I think it is possible to reject such crx if we detect mismatch in file names. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by krajshree@chromium.org
, Jan 28 2018