we submit extensions' source code, review it, run "npm run install && npm run build" & publish it
Reported by
wesam.we...@gmail.com,
Oct 31 2017
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.100 Safari/537.36 Steps to reproduce the problem: can't publish a highly obfuscated extension to the chrome store, it will be rejected. "Your item <name of extension> <id> is being taken down as it currently violates the section of the Developer Program Policy relating to Malicious Products as its obfuscating a part of code. Per our policies, where possible, make as much of your code visible in the package as you can. If some of your app's logic is hidden and it appears to be suspicious,we may remove it. To have your item reinstated, please make any necessary changes to ensure: All of the files and code are included in the item’s package. All code inside the package is human readable (no obfuscated or minified code). Avoid requesting or executing remotely hosted code (including by referencing remote javascript files or executing code obtained by XHR requests)." What is the expected behavior? Google should support this, Companies and Developers want to protect their intellectual property, and they'll do as much as they can to make it as much as hard for reverse engineers. this extra step to the review process, is a solution to the trust issue, reviewer can read the same code we the developers wrote, you'll have to have node installed, run "npm install" to download the dependencies, then run the build script that minifies, compresses and bundles the extension to a zip file, you then will publish it. What went wrong? my highly obfuscated extension that I bundled and published was rejected. Did this work before? No Chrome version: 61.0.3163.100 Channel: n/a OS Version: 10.0 Flash Version: please support this publishing process, Companies and Developers, will thank you for it.
,
Nov 1 2017
As the issue is related to chrome web store>>Extension, cc'ing jawag@chromium.org to take a look at this issue
,
Nov 6 2017
jawag@: Could you please take a look at this. Thank you!
,
Nov 7 2017
,
Nov 29 2017
jawag@, I'm looking forward to your feedback and the continuation of the discussion. :)
,
Jan 4 2018
,
May 28 2018
You can close this issue, there are more important features to add and bugs to fix with limited resources. I don't care about it.. actually I don't like it ~anymore~ at all. /s the all knowing Saint RMS has blessed my mind with his infinite wisdom. /s |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by wesam.we...@gmail.com
, Oct 31 2017