Closed enthusedcoder closed 10 months ago
In your example script, you are calling _WD_Startup() in the wrong place, which is why you see this near the beginning of the log --
_WD_Startup ==> Invalid value [4] : Location for Web Driver not set.
The script ran fine for me once I fixed that and some other minor issues related to paths.
session not created: DevToolsActivePort file doesn't exist
This seems to be a common problem with the Chromium-based browsers. I don't remember the solution off hand, but you may want to check the FAQ on the wiki or search the AutoIt forums.
Take a look at the first line after the json string. I did notice that one of the parameters, the "--user-data-dir" parameter, was set to equal the same value that appeared in the message box when it appeared. Not sure what is going on here.
This is normal webdriver behavior where a new user profile will be created in a temporary directory unless you specify otherwise.
Are you trying to run in Administrator mode? If so, then that's the issue. See https://github.com/MicrosoftEdge/EdgeWebDriver/issues/80
Closing as this appears to be environmental and not a bug in the UDF.
Bug report
Describe the bug
So, I used code that was pretty much copy/pasted from the demo example provided in the repo, which puzzles me all the more why I am encountering this issue. I have a script that I have written that uses the Microsoft Edge web driver to automate some tasks, but when the compiled script attempts to do this, the following message box appears on the screen, and the browser fails to load the web page:
You may have noticed that I specifically say that this issue occurs when the code is run by a compiled script. That is because, when the uncompiled script is run via scite (in scite window, "tools" > "Go" menu), the error does not occur, meaning that it is working at one point. AT least, this used to be the case, as, when I attempted to replicate the issue to post here, the message box just would not appear when it previously had, though the edge web driver still failed to launch and automate Edge. I then checked the driver's log file, which contained the following content:
Take a look at the first line after the json string. I did notice that one of the parameters, the "--user-data-dir" parameter, was set to equal the same value that appeared in the message box when it appeared. Not sure what is going on here.
How to reproduce
Steps to reproduce the behavior (e.g.):
Expected behavior
I would expect the msedge
Screenshots
Additional context
NA
System under test
Please complete the following information.