I've been using the 1.0.7 relatively consistently with ChromiumV112 but have recently updated Chromium to be the latest version and have come across more failures from timing out trying to sign in to Google. The odd thing is that when I remote into the agent (win64 interactive session) running the test (not headless), UndetectedChromeDriver is able to sign in without issue.
I've tested 1.0.7, latest and latest alpha versions with the same results and outside of potentially running a task scheduler to spin up remoting into the agent each time, what other options or configurations in UCD should I attempt in having it be more stable? Likely the issue is still that this project is somewhat old and not keeping up with the latest bot detection but I'm still curious what work arounds people are using with this to get it to work. Thanks!
I've been using the 1.0.7 relatively consistently with ChromiumV112 but have recently updated Chromium to be the latest version and have come across more failures from timing out trying to sign in to Google. The odd thing is that when I remote into the agent (win64 interactive session) running the test (not headless), UndetectedChromeDriver is able to sign in without issue.
I've tested 1.0.7, latest and latest alpha versions with the same results and outside of potentially running a task scheduler to spin up remoting into the agent each time, what other options or configurations in UCD should I attempt in having it be more stable? Likely the issue is still that this project is somewhat old and not keeping up with the latest bot detection but I'm still curious what work arounds people are using with this to get it to work. Thanks!