Skip to content

[🐛 Bug]: webview seems not to be detected in 4.33 #15797

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
tiramba opened this issue May 26, 2025 · 1 comment
Open

[🐛 Bug]: webview seems not to be detected in 4.33 #15797

tiramba opened this issue May 26, 2025 · 1 comment
Labels
A-needs-triaging A Selenium member will evaluate this soon! C-dotnet .NET Bindings I-defect Something is not working as intended I-regression Something was working but we "fixed" it OS-windows

Comments

@tiramba
Copy link

tiramba commented May 26, 2025

Description

For our test automation we want to attach to an existing instance of the edge webview (embedded).
With selenium 4.32 it worked as alwys with the following debug outputs:

DEBUG Sending stats to Plausible: Props { browser: "webview2", browser_version: "", os: "windows", arch: "amd64", lang: "csharp", selenium_version: "4.32" }
DEBUG msedgedriver not found in PATH
DEBUG webview2 detected at C:\Program Files (x86)\Microsoft\EdgeWebView\Application
DEBUG Running command: wmic datafile where name='C:\Program Files (x86)\Microsoft\EdgeWebView\Application' get Version /value
DEBUG Output: "\r\r\n\r\r\n\r"
DEBUG Running command: REG QUERY HKLM\SOFTWARE\WOW6432Node\Microsoft\EdgeUpdate\Clients{F3017226-FE2A-4295-8BDF-00C3A9A7E4C5} /v pv
DEBUG Output: "\r\nHKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\EdgeUpdate\Clients\{F3017226-FE2A-4295-8BDF-00C3A9A7E4C5}\r\n pv REG_SZ 136.0.3240.92\r\n"
DEBUG Detected browser: webview2 136.0.3240.92
DEBUG Reading msedgedriver version from https://msedgedriver.azureedge.net/LATEST_RELEASE_136_WINDOWS
DEBUG Required driver: msedgedriver 136.0.3240.92
DEBUG Acquiring lock: C:\Users\taadmin.cache\selenium\msedgedriver\win64\136.0.3240.92\sm.lock
DEBUG Downloading msedgedriver 136.0.3240.92 from https://msedgedriver.azureedge.net/136.0.3240.92/edgedriver_win64.zip
INFO Driver path: C:\Users\taadmin.cache\selenium\msedgedriver\win64\136.0.3240.92\msedgedriver.exe
INFO Browser path: C:\Program Files (x86)\Microsoft\EdgeWebView\Application\136.0.3240.92\msedge.exe
Driver path: C:\Users\taadmin.cache\selenium\msedgedriver\win64\136.0.3240.92\msedgedriver.exe
Browser path: C:\Program Files (x86)\Microsoft\EdgeWebView\Application\136.0.3240.92\msedge.exe

After the update to selenium 4.33 we have now the following error message

error in HandleBrowserException|OpenQA.Selenium.NoSuchDriverException: The browser path is not a valid file: C:\Program Files (x86)\Microsoft\EdgeWebView\Application; For documentation on this error, please visit: https://www.selenium.dev/documentation/webdriver/troubleshooting/errors/driver_location
bei OpenQA.Selenium.DriverFinder.BinaryPaths()
bei OpenQA.Selenium.DriverFinder.GetDriverPath()
bei OpenQA.Selenium.Chromium.ChromiumDriver.GenerateDriverServiceCommandExecutor(DriverService service, DriverOptions options, TimeSpan commandTimeout)
bei OpenQA.Selenium.Chromium.ChromiumDriver..ctor(ChromiumDriverService service, ChromiumOptions options, TimeSpan commandTimeout)

with the debug logs

DEBUG Sending stats to Plausible: Props { browser: "webview2", browser_version: "", os: "windows", arch: "amd64", lang: "csharp", selenium_version: "4.33" }
DEBUG msedgedriver not found in PATH
DEBUG webview2 detected at C:\Program Files (x86)\Microsoft\EdgeWebView\Application
DEBUG webview2 not found in the system
DEBUG Reading msedgedriver latest version from https://msedgedriver.azureedge.net/LATEST_STABLE
DEBUG Latest msedgedriver major version is 136
DEBUG Reading msedgedriver version from https://msedgedriver.azureedge.net/LATEST_RELEASE_136_WINDOWS
DEBUG Required driver: msedgedriver 136.0.3240.92
DEBUG Acquiring lock: C:\Users\taadmin.cache\selenium\msedgedriver\win64\136.0.3240.92\sm.lock
DEBUG Downloading msedgedriver 136.0.3240.92 from https://msedgedriver.azureedge.net/136.0.3240.92/edgedriver_win64.zip
INFO Driver path: C:\Users\taadmin.cache\selenium\msedgedriver\win64\136.0.3240.92\msedgedriver.exe
INFO Browser path: C:\Program Files (x86)\Microsoft\EdgeWebView\Application
Driver path: C:\Users\taadmin.cache\selenium\msedgedriver\win64\136.0.3240.92\msedgedriver.exe
Browser path: C:\Program Files (x86)\Microsoft\EdgeWebView\Application

both runs were performed on different but identical machines (created by the same template).
You can see on the last line of the debug logs, that the filename and the folder with the version is missing.

It seems to me, that this is a bug in the new version 4.33! Can you please have a look on it?

Reproducible Code

var eo = new EdgeOptions { UseWebView = true, DebuggerAddress = $"localhost:{Port}" };
Driver = new EdgeDriver(EdgeDriverService.CreateDefaultService(), eo, TimeSpan.FromMinutes(3));

ℹ️ Last known working version: 4.32

@tiramba tiramba added I-defect Something is not working as intended A-needs-triaging A Selenium member will evaluate this soon! labels May 26, 2025
@selenium-ci
Copy link
Member

@tiramba, thank you for creating this issue. We will troubleshoot it as soon as we can.

Selenium Triage Team: remember to follow the Triage Guide

@github-actions github-actions bot added C-dotnet .NET Bindings I-regression Something was working but we "fixed" it OS-windows labels May 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-needs-triaging A Selenium member will evaluate this soon! C-dotnet .NET Bindings I-defect Something is not working as intended I-regression Something was working but we "fixed" it OS-windows
Projects
None yet
Development

No branches or pull requests

2 participants