-
Notifications
You must be signed in to change notification settings - Fork 7
Look into publishing on Chrome Web Store #14
Comments
Oh wow… thanks for bringing this up. Are you able to manually enable the extension with the switch (might require developer mode) or is it not possible at all? I'm still on Chromium v78 (current stable), where I can freely install (and enable) the extension with and without developer mode enabled. I guess this is a change introduced in later versions, a rather controversial one to put it mildly. One of the reasons I use Chromium and not Chrome is to escape Google lock-in after all. I'll investigate and see what I can do. |
Not possible at all. I though I was doing something wrong so I flipped the switch several times.
Same here.
Thanks a lot! |
@AGlezB I've updated the README with an alternate installation method which should work for you, see Installing via "Load unpacked extension". Additionally I'll list the extension in the Chrome Web Store as soon as the PR for #16 lands. The fact that I use a proxy to circumvent CORS won't help to get through the review process, so that has to come first. As to the root cause of the warning and whether it's something that's been introduced in Chromium 79 or 80, I can't tell. I've skimmed briefly through the source code and found the string itself ( If anybody knows more, I'd love to hear! |
@kkkrist It does work. Thanks. |
Closing. I don't think I'll publish this extension on the Chrome Web Store in the near future. It'll probably draw more attention than I can handle right now. The proxy is already running on the limit of what of the current (free plans) hosting setup allows and I want to concentrate on other projects for now. Anyway, the extension works fine as it is and I guess people really interested are fine with the manual/dev-mode install. |
https://developer.chrome.com/webstore/publish
The text was updated successfully, but these errors were encountered: