Search the Community
Showing results for tags 'chromedrive'.
-
I had some issue with attacing to existing chrome. But it was very wired. First of all log: some findings: https://issues.chromium.org/issues/42323720 As you know I know about this: Finally I was able to attach to runing Chrome instances and this usually works fine. Today my situation was like this: I was working on automating a certain portal, to which a client logged in. This portal is something like an email box. To make sure that the page would not log me out, I refreshed the page every few minutes or clicked on some of its elements (inbox, trash, sent, etc.). I wrote 20 lines of code and did tests by connecting to an existing session. another 20 lines.... another 20 lines.... another 20 lines.... After about 2 hours of such work, the error that I mention above appeared. The log comes from the connection creation stage, i.e. the part of the code that I did not change. Simply refreshing the browser F5 did not help - unfortunately I did not check CTRL+F5 (or CTRL+SHIFT+R) that should perform a "hard refresh". Interestingly, the only solution that helped was manually navigating to another page within the same browser tab, and then navigating again to the automated portal, which fortunately did not log me out. Question: Do you have any idea why manually navigating to another portal and navigating back to the desired portal solves this problem? btw. Today I did reasarch on Au3Forum and I saw other related question - quite fresh - I think they may be related to my issue:
-
- webdriver
- webdriver udf
-
(and 2 more)
Tagged with:
-
This morning I started to get some feedback my Chrome scripts (using chromedriver) were not working anymore. I have not determined that on computers with the problem the Chromedriver has the 20-8-2024 19:17 date (august 8, 7:17 PM ๐ Sofar I have done the following things: deleted chromedriver.exe to automatically download a "new" one updated the chromedriver manually to the BETA version and DEV version updated Chrome to the newest via internal Chrome update to v128.0.6613.84 The version of Chrome and the chromdriver are the same version. https://googlechromelabs.github.io/chrome-for-testing/#stable I am glad not everyone seems to have the problem yet. If any one has an idea what might be to problem, please share๐ Meanwhile I keep looking for more information. Thanks.