-
Notifications
You must be signed in to change notification settings - Fork 50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Removed from Chrome Web Store #19
Comments
Hi! I'm working on a new version to fix the issue. |
Appreciate it, man! any ETA? |
@avijit-h fixed version is under review. |
@neeilya - what was the issue? |
@zilehuda something about requesting storage permissions but not using it. Oh and I fixed the bug with notification sound, so you can turn it off finally! P.s. also working on a completely new version with new features, hopefully will release it soon 🤞 |
Hi, I accidentally got the extension removed from my device I tried installing manually but was not able to do so after it was removed from chrome can anyone help me. |
@FerozArshad you can use this archive while Google is reviewing the new version. Just unpack it and install from extensions settings page (extensions -> load unpacked). |
It gives lot of security errors? is it safe and nothing happens to upwork account ? Refused to load the script 'https://assets.static-upwork.com/detect-keyboard-user/1.2.0/setup-iife.min.js' because it violates the following Content Security Policy directive: "script-src 'self' blob: filesystem:". Note that 'script-src-elem' was not explicitly set, so 'script-src' is used as a fallback. |
@FerozArshad yes it is safe. I built it directly from the source code. The errors you see are triggered by Chrome because extension makes a call and loads Upwork webpage to keep your session authorised, otherwise Upwork logs you out or forces you to input captcha. When the webpage loads it automatically tries to load Upwork scripts and this is what triggers the errors, because Chrome rejects loading "3rd party" scripts even though extension doesn't really use them. You can see more details in the source code here. |
Ok, thanks it works perfectly. |
Hey, Google removed this extension, please help!
The text was updated successfully, but these errors were encountered: