Selenium: Logs stopped working in ChromeDriver (c#)

Created on 15 Jul 2019  路  14Comments  路  Source: SeleniumHQ/selenium

馃悰 Bug Report

driver.Manage().Logs.GetLog(LogType.Browser) throws this exception now.

System.NotImplementedException: unknown command: unknown command: session/f3cbd0a8ba58e1fe3e1e6d36dbdaf28e/se/logs

OS: Windows 10
Browser: Chrome
Browser version: 75.0.3770.100
Browser Driver version: ChromeDriver 75.0.3770.140
Selenium.WebDriver: 4.0.0-alpha02

C-dotnet D-chrome

Most helpful comment

It鈥檚 a mistake, y鈥檃ll. I鈥檝e been on holiday, and I鈥檓 very sick right now. Patience would be appreciated.

All 14 comments

As per changelog I tried

setting the UseSpecCompliantProtocol property of ChromeOptions to false

but it throws OpenQA.Selenium.WebDriverException: invalid session id.

Even tho driver is ISupportsLogs returns true (see changelog) and driver.Manage().Logs.AvailableLogTypes returns both browser and driver, driver.Manage().Logs.GetLog(logKind) throws the mentioned System.NotImplementedException for both listed available types.

OS: Windows 10
Browser: Chrome
Browser version: 75.0.3770.142
Browser Driver version: ChromeDriver 75.0.3770.140
Selenium.WebDriver: 4.0.0-alpha02

Please try this again with chromedriver 76

@lmtierney
Got same issue

System.NotImplementedException: 'unknown command: unknown command: session/35a408e6da14ce20d92c8ccb05e1d948/se/logs'

with
WebDriver.Manage().Logs.GetLog(LogType.Browser);

OS: Windows 10
Browser: Chrome
Browser version: 76.0.3809.87
Browser Driver version: ChromeDriver 76.0.3809.68
Selenium.WebDriver: 4.0.0-alpha02

@lmtierney me too, getting the same issue.

Chrome 76.0.3809.87
Chromedriver: 76.0.3809.68-beta

System.NotImplementedException: unknown command: unknown command: session/a80253d342e550f398b1537cfafe9702/se/logs

@lmtierney
Got them issue too
unknown command: unknown command: session/186a2f952d2c2e104136cee2f61bd0c7/se/logs

The chrome driver settings are

var chromeOptions = new ChromeOptions
{
    PageLoadStrategy = PageLoadStrategy.Normal,
};
chromeOptions.AddArgument("no-sandbox");

var perfLogPrefs = new ChromiumPerformanceLoggingPreferences();
perfLogPrefs.AddTracingCategories("devtools.network");

chromeOptions.PerformanceLoggingPreferences = perfLogPrefs;
chromeOptions.AddAdditionalOption(CapabilityType.EnableProfiling, true);
chromeOptions.SetLoggingPreference("performance", LogLevel.Info);

Are any of you going through the selenium-standalone or grid? I'm no C# expert so I may need some help from @jimevans

I believe the issue is that the GetLog command should be a PostCommand but is currently a GetCommand

https://github.com/SeleniumHQ/selenium/blob/master/dotnet/src/webdriver/Remote/RemoteWebDriver.cs#L175

I believe the issue is that the GetLog command should be a PostCommand but is currently a GetCommand

https://github.com/SeleniumHQ/selenium/blob/master/dotnet/src/webdriver/Remote/RemoteWebDriver.cs#L175

Hi,

Is this being fixed please?

Thanks!

I believe the issue is that the GetLog command should be a PostCommand but is currently a GetCommand

https://github.com/SeleniumHQ/selenium/blob/master/dotnet/src/webdriver/Remote/RemoteWebDriver.cs#L175

Also the URL of the command is different from what ChromeDriver expects. The expected URL is "/session/{sessionId}/se/log" (without the trailing s). (Note that the Java binding at https://github.com/SeleniumHQ/selenium/blob/master/java/client/src/org/openqa/selenium/remote/codec/w3c/W3CHttpCommandCodec.java#L158 uses the URL expected by ChromeDriver, so it would be easier to fix the discrepancy in the .NET binding instead of modifying ChromeDriver.)

It鈥檚 a mistake, y鈥檃ll. I鈥檝e been on holiday, and I鈥檓 very sick right now. Patience would be appreciated.

@szamacz this is a gentle reminder that this is an open source project and the developer has said that he's unwell at the moment. If you need the fix ASAP then I'd recommend forking it, fixing it, and submitting a pull request for consideration. Failing that, I'm sure you can get a full refund ;)

Dude, this is an open source project. Let's appreciate all the work that has been put into this and be respectful of the creators time. If it's too much of a problem you can figure out how to fix it and submit a pull request with the fix, hire someone to fix it, or just be patient.

facing same issue
@jimevans , get better soon

Resolved in 26d8b67. Thank you for your patience.

Was this page helpful?
0 / 5 - 0 ratings