Chromedriver issues August 2024

[RDE]

On 8/23/2024 at 5:13 PM, Danp2 said:

Unsure if this is intended, but as some of you noticed chromedriver now tries to use a random port on opening. You can override that by supplying the desired port number as a parameter --

_WD_Option('DriverParams', '--port=9515 --verbose --log-path="' & @ScriptDir & '\chrome.log"')

 

Hugh thanks for this, I had to reinstall after an "upgrade" to Windows 11 and I could not work out what was going on

[mLipok]

https://github.com/Danp2/au3WebDriver/pull/519/files

[Jemboy]

I understand the theory behind webdriver/selenium.
However, it has become the bane of my existence.

Many Autoit IE scripts from more than 10 years ago, still work (even on Windows 11).

It would be nice if webdriver would always be backards compatible,
so that existing scripts always continue to work (if they work now).

Then you would only have to update for bugs that apply to your script/ for new features or the conscious desire to update the stack (webdriver and/or UDF).

Since I switched to webdriver/chromedriver, I have had to modify my scripts 3 times (including this port update).

[Danp2]

[Humanzee]

16 hours ago, mLipok said:

https://github.com/Danp2/au3WebDriver/pull/519/files

FYI, this port thing fixes what appears to be the same problem in MS Edge browser.   The wd_demo.au3 file in the 1.3.1 zip file will fail with settings:

Browser:MSEdge
Debug:Full
Update:Current
Headless:No
ConsoleOut:ConsoleWrite

Giving error message:
> wd_demo.au3: _WD_CreateSession
! Error = 10 occurred on: Demo

Even though the web driver will start on port 52534 the session doesn't get created, and the edge browser does not open.

Downloading the Pull 519 version of the wd_demo.au3 and running on port 9515 it works fine.   I'd suggest updating the release asap, because my first stop was to update my core files from the latest release, which still didn't work, Then I found this thread..

 

[Danp2]

There are some things that need to be addressed before that PR can be merged. Also, you will still need to update your own scripts because nothing is being changed in the core files (only the demo script is updated).

[Humanzee]

18 hours ago, Danp2 said:

Also, you will still need to update your own scripts because nothing is being changed in the core files (only the demo script is updated).

I did, and got my users working again.  Thanks to all who maintain this function set.

[abs]

@Danp2 For some reason edge driver on my end still opening on Port 0. If I downgrade the driver version things return to normal. I have used following as advised in this thread to no avail.

 

_WD_Option('Driver', 'msedgedriver.exe')
    _WD_Option('Port', 9515)
    _WD_Option('DriverParams', '--port=9515 --verbose --log-path="' & @ScriptDir & '\msedge.log"')
    RunAs($TargetUsername, $TargetDomain, $TargetPassword, 2, $DriverPath, "", @SW_SHOW)
    _WD_Option('driverdetect', true)

 

[Danp2]

3 hours ago, abs said:

    RunAs($TargetUsername, $TargetDomain, $TargetPassword, 2, $DriverPath, "", @SW_SHOW)

This is the likely source of your issues. If you are going to launch the webdriver like this instead of letting _WD_Startup do it, then you need to adjust the parameter that you are passing to RunAs to include the additional options that are part of DriverParams.

[abs]

Thanks @Danp2, It does make sense what you're saying. I looked at the web driver wrappers and realized the same. However, the webdriver session must run under a particular user to allow windows/ kerberos auth to work. Would you be able to suggest on how do I pass the port number 9515 while using RunAs capability ?

 

 

[Danp2]

This is a derivative of what _WD_Startup does --

Local $sParams = '--port=9515 --verbose --log-path="' & @ScriptDir & '\msedge.log"'
    Local $sCommand = StringFormat('"%s" %s ', $DriverPath, $sParams)

    RunAs($TargetUsername, $TargetDomain, $TargetPassword, 2, $sCommand, "", @SW_SHOW)

Untested, but I assume something like this should work ok.

[abs]

Thanks for responding @Danp2. If I use the following Stringformat the driver runs on port 0 and the browser never opens. If I use '"%s" %s' then driver doesn't open at all.

Func SetupEdge()
    
    Local $sParams = '--port=9515 --verbose --log-path="' & @ScriptDir & '\msedge.log"'
    Local $sDriver = "D:\EdgeDriver\msedgedriver.exe"
    Local $sCommand = StringFormat("%s", $sDriver, $sParams)
    RunAs($TargetUsername, $TargetDomain, $TargetPassword, 2, $sCommand, "", @SW_SHOW)
    _WD_Option('driverdetect', true)
    
    ; Run the website in application mode
    Local $sURL = "https://" & $TargetAddress
    Local $sDesiredCapabilities = '{"capabilities": {"alwaysMatch": {"ms:edgeOptions": {"args": [ "start-maximized" , "--app=' & $sURL & '"], "binary": "' & StringReplace (@ProgramFilesDir, "\", "/") & '/Microsoft/Edge/Application/msedge.exe", "excludeSwitches": [ "enable-automation"]}}}}'
    
    $sSession = _WD_CreateSession($sDesiredCapabilities)
    Return $sSession
    
 EndFunc

 

[Danp2]

@abs You should check the value of $sCommand in both scenarios.

[abs]

This is resolved now. Thanks @Danp2. You're a champion. Here is the final code.

Func SetupEdge()
    
    _WD_Option('Driver', 'msedgedriver.exe')
    _WD_Option('Port', 9515)
    Local $sParams = '--port=9515 --verbose --log-path="' & @UserProfileDir & '\msedge.log"'
    Local $sDriver = "D:\Program Files (x86)\CyberArk\PSM\Components\msedgedriver.exe"
    Local $sCommand = StringFormat('"%s", %s', $sDriver, $sParams)
    RunAs($TargetUsername, $TargetDomain, $TargetPassword, 2, $sCommand, "", @SW_HIDE)
    _WD_Option('driverdetect', true)
    
    ; Run the website in application mode
    Local $sURL = "https://" & $TargetAddress
    Local $sDesiredCapabilities = '{"capabilities": {"alwaysMatch": {"ms:edgeOptions": {"args": [ "start-maximized" , "--app=' & $sURL & '"], "binary": "' & StringReplace (@ProgramFilesDir, "\", "/") & '/Microsoft/Edge/Application/msedge.exe", "excludeSwitches": [ "enable-automation"]}}}}'
    _WD_Startup()
    $sSession = _WD_CreateSession($sDesiredCapabilities)
    Return $sSession
    
 EndFunc