Edge 18 selenium- problem with trying to get cookies

Not reproducible Issue #23528060

Details

Author
Michael S.
Created
Sep 23, 2019
Privacy
This issue is public.
Found in
  • Microsoft Edge
Reports
Reported by 1 person

Sign in to watch or report this issue.

Steps to reproduce

This is a follow up to "Edge 18 selenium- problem with trying to get cookies": https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/20512308/
(I was unable to add a comment on this one after it was closed.)
The comment I wanted to add:
Hi Zachariah - this error (when executing the get_cookies() command) is occurring when using: MicrosoftWebDriver version 10.0.17763.1 (version 17763 looks to be the one which shipped with Edge 18 in MS’s 1809 release of Win 10). Are you able to test/reproduce on this version, or can you confirm that this error is due to this particular version of MicrosoftWebDriver?
Thank you,
Michael

Attachments

0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “Corey W.”

      Changed Assigned To to “Zachariah L.”

    • Hi Michael!

      I tested the Selenium .NET equivalent of get_cookies() and had no issues. Without having a minimal repro, I cannot provide any further insight into your problem. I tested this in C# because if I were to reproduce it there in addition to your language (python?) then that would mean that it was an issue with MicrosoftWebDriver and not the Selenium bindings for your language. This is an important thing to distinguish because we do not own nor maintain Selenium therefore any issues that are identified as “Selenium not webdriver” would have to be reported to their devs.  

      There are a few implementation quirks with Selenium and cookies but I assume that this is not your issue because I am assuming you are using the same test code on different browsers without issue. 

      For this issue to be actionable, I have to be able to reproduce the problem locally. Could you please provide me with a minimal reproduction?

      Thanks,

      Zach

    • Hi Zach,
      Thanks for looking into this. Yes, this command is working on other browsers but not Edge. This is my script I’m using on Sauce Labs using Java:

      import org.openqa.selenium.WebDriver;
      import org.openqa.selenium.remote.DesiredCapabilities;
      import org.openqa.selenium.remote.RemoteWebDriver;
      
      import java.net.URL;
      
      public class FirefoxW3C {
      
          public static final String USERNAME = System.getenv("SAUCE_USERNAME");
          public static final String ACCESS_KEY = System.getenv("SAUCE_ACCESS_KEY");
          public static final String URL = "https://" + USERNAME + ":" + ACCESS_KEY + "@ondemand.saucelabs.com:443/wd/hub";
      
          public static void main(String[] args) throws Exception {
      
              DesiredCapabilities caps = DesiredCapabilities.edge();
              caps.setCapability("seleniumVersion", "3.141.59");
              caps.setCapability("platform", "Windows 10");
              caps.setCapability("version", "latest");
              caps.setCapability("name", "jwp getCookies");
      
              WebDriver driver = new RemoteWebDriver(new URL(URL), caps);
      
              driver.get("https://www.google.com");
              driver.getTitle();
              driver.manage().getCookies();
              driver.quit();
          }
      
      }
      
    • Hi Michael!

      I tested the code you provided (locally and not through Saucelabs)  and I was able to get the cookies without error using Microsoft Edge 44.18362.329.0 Microsoft EdgeHTML 18.18362 on Windows 10 Version 1903 (OS Build 18362.356). Are you able to use this version on Saucelabs? It could be that this issue was resolved in an update.

      Thanks,

      Zach

    • Ok, thank you for that information. We don’t have this version running on Sauce Labs, but sounds like the later versions is where the issue lies. Thank you for testing this on your end!

      Michael

    • Hi Michael!

      My pleasure! I will resolve this issue as "Not Reproducible". If after testing on the newer version of Microsoft Edge, you are still experiencing this problem, then please feel free to reopen this issue and I will continue to look for a resolution.

      Thanks,

      Zach

    • Microsoft Edge Team

      Changed Status to “Not reproducible”

    You need to sign in to your Microsoft account to add a comment.

    Sign in