Skip to content
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

Open
avijit-h opened this issue Aug 30, 2021 · 10 comments
Open

Removed from Chrome Web Store #19

avijit-h opened this issue Aug 30, 2021 · 10 comments

Comments

@avijit-h
Copy link

Hey, Google removed this extension, please help!

@neeilya
Copy link
Owner

neeilya commented Aug 30, 2021

Hi!

I'm working on a new version to fix the issue.
Stay tuned :)

@avijit-h
Copy link
Author

Appreciate it, man! any ETA?

@neeilya
Copy link
Owner

neeilya commented Sep 4, 2021

@avijit-h fixed version is under review.
As soon as it is approved by Google, it will be available again.

@zilehuda
Copy link

zilehuda commented Sep 7, 2021

@neeilya - what was the issue?

@neeilya
Copy link
Owner

neeilya commented Sep 7, 2021

@zilehuda something about requesting storage permissions but not using it.
Don't know why they decided to enforce this rule after 4 years, but still.. 😄

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 🤞

@FerozArshad
Copy link

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.
I downloaded the files and uploaded them as developer mode in chrome it gives an error for backgroun.js and mainfest.js upload error

@neeilya
Copy link
Owner

neeilya commented Sep 7, 2021

@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).

package.zip

@FerozArshad
Copy link

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.
Refused to load the script 'https://assets.static-upwork.com/components/12.19.1/core.12.19.1.air2.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.
Refused to load the script 'https://assets.static-upwork.com/components/12.19.1/uploading.12.19.1.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.
Refused to load the script 'https://assets.static-upwork.com/ui-packages/@upwork/global-components/1.34.5/ugc.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.
Refused to load the script 'https://assets.static-upwork.com/vue-libs/vue.2.6.10.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.
Refused to load the script 'https://assets.static-upwork.com/vue-libs/vuex.3.1.0.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.
Refused to load the script 'https://assets.static-upwork.com/dash-api/1.2.0/setup-promise.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.
Refused to load the script 'https://assets.static-upwork.com/dash-api/1.2.0/setup-iife.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.
Refused to load the script 'https://assets.static-upwork.com/top-nav-user/2.18.4/top-nav-user.bundle.iife.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.
Refused to load the script 'https://assets.static-upwork.com/assets/FindWorkHome/build/runtime.7996ee2b19b990f29698.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.
Context
_generated_background_page.html
Stack Trace
_generated_background_page.html:0 (anonymous function)
Nothing to see here, move along.
Refused to load the script 'https://assets.static-upwork.com/assets/FindWorkHome/build/vendors.257135c2663800be5e4f.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.
Refused to load the script 'https://assets.static-upwork.com/assets/FindWorkHome/build/profile.0d278843c1add9875694.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.
Refused to load the script 'https://assets.static-upwork.com/assets/FindWorkHome/build/app.c710855bfa5e2aaf7961.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.

@neeilya
Copy link
Owner

neeilya commented Sep 7, 2021

@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.

@FerozArshad
Copy link

Ok, thanks it works perfectly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants