Being detected with send keys but not with manual input #1074
Replies: 5 comments 21 replies
-
Subscribed to this as I'm facing the same problem. One work around I found is to use the Anyways, keen to see what comes of this. I also noticed the page console-logging |
Beta Was this translation helpful? Give feedback.
-
Super helpful! Right after the update it broke the send_keys(). Thanks again for the input, this should be an issue. |
Beta Was this translation helpful? Give feedback.
-
Just got detected by google using the previous version, anyone else? |
Beta Was this translation helpful? Give feedback.
-
Got detected too even without headless mode. Tried settings from the post above and downgrade undetected-chrome version but it didn’t help. Hope anyone can help or suggest something. Did not try downgrade chrome version though |
Beta Was this translation helpful? Give feedback.
-
same issue, detected after click, click_safe() and send_keys(), on akamai protected site, after registration getting 403 response |
Beta Was this translation helpful? Give feedback.
-
So my work makes me do this tedious process of checking my schedule so I automated it. Worked for months but for some reason, my code isn't functioning anymore.
It detected when it automatically inputted the data, but NOT when I manually inputted it thru the same UC selenium browser. What could I do to make it undetectable?
I have a bajillion flags for headless mode (before GChrome updated headless mode to be nearly undetectable) but with or without them still does not function properly.
EDIT: forgot to mention. I even tested something with a command like
actions.pause(4).move_to_element.pause(1).click().perform()
to select the username and password boxes and even slowly streaming in my username and password but still getting detected.Thoughts?
EDIT:! I FIXED IT. But I do think I should maybe make an issue. For some reason, Downgrading from the newest version to 3.2.1 fixed it. Idk why or what changed but my employer's website likes me again. what an odd issue.
For some reason, versions 3.4.0 -> 3.4.2 break my code and don't run at all. But then in 3.4.4 (3.4.3 doesn't exist lol) I get detected.
But downgrading to version 3.2.0 / 3.2.1 works perfectly!
downgrading didn't work perfectly but it is fixable! If you're not using headless then it SHOULD work on the newest version but if you are using headless your code will NOT work. In addition to downgrading UC you should also downgrade chrome from 110 -> 109
Beta Was this translation helpful? Give feedback.
All reactions