Open arundhatid opened 2 years ago
I don't think it has anything to do with v103. Correlation is not causation.
You're playing the headless-cat-n-mouse game and now you've lost. I don't think it's a game worth playing : Since neither the mouse nor the cat have any incentives to open-source their efforts, you're on your own especially if you don't give a minimum working example.
Selenium-stealth implement basic known evasions but it's 2 years old and does one thing wrong :
It deletes navigator.webdriver
, that's a red flag ... At least UC does it properly but you're overriding it.
btw I'm quite sure spoofing a Windows user agent on a Linux system is easily detected too.
We are running automated test deployed as a k8s cron job in GCP cluster. Our application has IAP enabled. We have used undetected-chromedriver and applied all the fixes which we could find to make sure that we avoid bot detection. So far we have been successful. But since chrome driver version is upgraded to 103 , test is getting detected as bot and captch is displayed as soon as we enter email id .
Please note that we use headless chrome( yes, I read the readme file and I know its WIP but I am testing my luck here :) ). We use the same python+selenium script to run in our CI/CD pipeline and there it runs fine.
Following is the snippet of my docker file which is used to deploy test as k8s cron job in GCP cluster.
Following is python + selenium script to launch application and the code used to lanuch chrome driver:
Is there anything I can try other than this to