-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Antibots detecting because of poor _hook_remove_cdc_props implementation #986
Comments
Full 100% stable, optimal fix here: #1010 |
Still detectable by discord |
Using clean IP? |
Send your code that triggers detection please. There can be many reasons why you get 'detected' that don't involve ChromeDriver specifically. It can be your browser fingerprint or your behavior. |
Thanks a lot its my bad now it working |
How did you fix it? |
use lukect fork |
Thanks, that worked. |
The antibot scripts are adding fake cdc_props (props which match the regex) and undetected-chromedriver is removing them because of a poor implementation.
Optimal fix, use my fork here here: #1010
Temporary fix until my PR is acceptedAdd this after initializing the
Chrome
instance, but before using it (Chrome.get("url")
).Example
Why does this work?
We are now correctly removing the cdc_props before undetected-chromedriver 3.2.1 detects any cdc_props and triggers a flawed deletion implementation. The flawed deletion implementation runs if there are any cdc_props when you use
Chrome.get(url)
. My quick fix removes the cdc_props beforehand, preventing the flawed deletion implementation from being triggered.The text was updated successfully, but these errors were encountered: