Skip to content
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.

Sign up for GitHub

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

Jump to bottom

browserName option seems not to be working when setting "msedge" #115

Closed
chobeat opened this issue Jul 31, 2023 · 8 comments
Closed

browserName option seems not to be working when setting "msedge" #115

chobeat opened this issue Jul 31, 2023 · 8 comments

Comments

@chobeat
Copy link

chobeat commented Jul 31, 2023 •
edited
Loading

Hello.

I'm trying to use appium with Microsoft Edge. The browserName option seems to be completely ignored. I can run easily on chrome and the session starts correctly and opens google chrome. If I set browserName to msedge, it still opens Microsoft Edge.

This is my set of capabilities


    options = AppiumOptions()
    options.platform_name = "Linux"
    options.set_capability("browserName", "msedge")
    options.automation_name = "Chromium"
    options.new_command_timeout = 500
    edge_args= [
        "--no-sandbox",
        "--disable-dev-shm-usage",  # uses disk instead of ram
        "--window-size=800,1400",
    ]
    if headless:
        edge_args.append("--headless")
    if proxy:
        edge_args.append(f"--proxy-server={proxy}")
    options.set_capability(
        "ms:edgeOptions",
        {
            "w3c": False,
            "args": chrome_args,
        },
    )

Is it a bug on your side? Am I doing something wrong?
@jlipps
Copy link
Member

jlipps commented Jul 31, 2023

Can you link to a gist of the full appium server log please

@KazuCocoa
Copy link
Member

As https://github.com/appium/appium-chromium-driver, please make sure you gave the proper msedgedriver executable version as well.

msedgedriver support is limited. appium:autodownloadEnabled does not work for the driver, thus appium:executable is necessary to automate MSEdge browser properly.

@chobeat
Copy link
Author

chobeat commented Aug 1, 2023

Hello. I installed the driver and pointed to it explicitly. I've also made sense of a lot of documentation and examples that felt obscure before.

Now my capabilities look like this



    options = AppiumOptions()
    options.platform_name = "Linux"
    options.set_capability("browserName", "msedge")
    options.automation_name = "Chromium"

    options.set_capability("appium:executable","/usr/bin/msedgedriver")
    options.new_command_timeout = 500

I have msedgedriver and microsoft-edge installed.

With these capabilities the behavior I observe is that it opens google-chrome and prints this until I kill it

[AppiumDriver@a3c2] Appium v2.0.0-beta.71 creating new ChromiumDriver (v1.1.31) session
[AppiumDriver@a3c2] Checking BaseDriver versions for Appium and ChromiumDriver
[AppiumDriver@a3c2] Appium's BaseDriver version is 9.3.10
[AppiumDriver@a3c2] ChromiumDriver's BaseDriver version is 9.1.0
[debug] [ChromiumDriver@564e] Creating session with W3C capabilities: {
[debug] [ChromiumDriver@564e]   "alwaysMatch": {
[debug] [ChromiumDriver@564e]     "platformName": "Linux",
[debug] [ChromiumDriver@564e]     "browserName": "msedge",
[debug] [ChromiumDriver@564e]     "appium:automationName": "Chromium",
[debug] [ChromiumDriver@564e]     "appium:executable": "/usr/bin/msedgedriver",
[debug] [ChromiumDriver@564e]     "appium:newCommandTimeout": 500
[debug] [ChromiumDriver@564e]   },
[debug] [ChromiumDriver@564e]   "firstMatch": [
[debug] [ChromiumDriver@564e]     {}
[debug] [ChromiumDriver@564e]   ]
[debug] [ChromiumDriver@564e] }
[ChromiumDriver@564e (2ab0a527)] Session created with session id: 2ab0a527-e6ac-41e2-85b9-0b79f3939f0a
[debug] [Chromedriver@f0c3] Changed state to 'starting'
[Chromedriver@f0c3] Set chromedriver binary as: /usr/bin/msedgedriver
[debug] [Chromedriver@f0c3] Killing any old chromedrivers, running: pkill -15 -f "/usr/bin/msedgedriver.*--port=9515"
[Chromedriver@f0c3] No old chromedrivers seem to exist
[Chromedriver@f0c3] Spawning chromedriver with: /usr/bin/msedgedriver --port=9515 --verbose
[debug] [Chromedriver@f0c3] Microsoft Edge WebDriver version: '115.0.1901.188'
[debug] [Chromedriver@f0c3] Matched '/status' to command name 'getStatus'
[debug] [Chromedriver@f0c3] Proxying [GET /status] to [GET http://127.0.0.1:9515/status] with no body
[Chromedriver@f0c3] connect ECONNREFUSED 127.0.0.1:9515
[debug] [Chromedriver@f0c3] Matched '/status' to command name 'getStatus'
[debug] [Chromedriver@f0c3] Proxying [GET /status] to [GET http://127.0.0.1:9515/status] with no body
[debug] [Chromedriver@f0c3] Got response with status 200: {"value":{"build":{"version":"115.0.1901.188 (b51b39339c49c4dc7c61b77f8b61420ca0ab7b68)"},"message":"msedgedriver ready for new sessions.","os":{"arch":"x86_64","name":"Linux","version":"5.15.0-78-generic"},"ready":true}}
[Chromedriver@f0c3] Starting W3C Chromedriver session with capabilities: {
[Chromedriver@f0c3]   "capabilities": {
[Chromedriver@f0c3]     "alwaysMatch": {
[Chromedriver@f0c3]       "goog:loggingPrefs": {
[Chromedriver@f0c3]         "browser": "ALL"
[Chromedriver@f0c3]       }
[Chromedriver@f0c3]     }
[Chromedriver@f0c3]   }
[Chromedriver@f0c3] }
[debug] [Chromedriver@f0c3] Matched '/session' to command name 'createSession'
[debug] [Chromedriver@f0c3] Proxying [POST /session] to [POST http://127.0.0.1:9515/session] with body: {"capabilities":{"alwaysMatch":{"goog:loggingPrefs":{"browser":"ALL"}}}}
[debug] [Chromedriver@f0c3] Webview version: 'Chrome/114.0.5735.106'
[debug] [Chromedriver@f0c3] Webview version: 'Chrome/114.0.5735.106'
[debug] [Chromedriver@f0c3] Webview version: 'Chrome/114.0.5735.106'
[debug] [Chromedriver@f0c3] Webview version: 'Chrome/114.0.5735.106'
[debug] [Chromedriver@f0c3] Webview version: 'Chrome/114.0.5735.106'
[debug] [Chromedriver@f0c3] Webview version: 'Chrome/114.0.5735.106'
[debug] [Chromedriver@f0c3] Webview version: 'Chrome/114.0.5735.106'
[debug] [Chromedriver@f0c3] Webview version: 'Chrome/114.0.5735.106'
[debug] [Chromedriver@f0c3] Webview version: 'Chrome/114.0.5735.106'
[debug] [Chromedriver@f0c3] Webview version: 'Chrome/114.0.5735.106'
[debug] [Chromedriver@f0c3] Webview version: 'Chrome/114.0.5735.106'
[debug] [Chromedriver@f0c3] Webview version: 'Chrome/114.0.5735.106'

So it's clearly using the edge driver but then the behavior is weird.

@KazuCocoa
Copy link
Member

KazuCocoa commented Aug 1, 2023 •
edited
Loading

Thanks. Perhaps I need to take a look. I'll check it tonight

@chobeat
Copy link
Author

chobeat commented Aug 1, 2023

Let me know if I can help or if you struggle to reproduce the issue. In the next two weeks I have time to focus on this issue.

@KazuCocoa
Copy link
Member

KazuCocoa commented Aug 2, 2023 •
edited
Loading

hm, it worked on my local. (macOS env though)

[debug] [Chromedriver@512e] Proxying [GET /status] to [GET http://127.0.0.1:9515/status] with no body
[debug] [Chromedriver@512e] Got response with status 200: {"value":{"build":{"version":"115.0.1901.183 (db29db5e66a28f9f889ff1962ead6e0c377200e0)"},"message":"msedgedriver ready for new sessions.","os":{"arch":"arm64","name":"Mac OS X","version":"13.4.1"},"ready":true}}
[Chromedriver@512e] Starting W3C Chromedriver session with capabilities: {
[Chromedriver@512e]   "capabilities": {
[Chromedriver@512e]     "alwaysMatch": {
[Chromedriver@512e]       "goog:loggingPrefs": {
[Chromedriver@512e]         "browser": "ALL"
[Chromedriver@512e]       }
[Chromedriver@512e]     }
[Chromedriver@512e]   }
[Chromedriver@512e] }
[debug] [Chromedriver@512e] Matched '/session' to command name 'createSession'
[debug] [Chromedriver@512e] Proxying [POST /session] to [POST http://127.0.0.1:9515/session] with body: {"capabilities":{"alwaysMatch":{"goog:loggingPrefs":{"browser":"ALL"}}}}
[debug] [Chromedriver@512e] Webview version: 'Edg/115.0.1901.188'
[debug] [Chromedriver@512e] Got response with status 200: {"value":{"capabilities":{"acceptInsecureCerts":false,"browserName":"msedge","browserVersion":"115.0.1901.188","ms:edgeOptions":{"debuggerAddress":"localhost:61359"},"msedge":{"msedgedriverVersion":"115.0.1901.183 (db29db5e66a28f9f889ff1962ead6e0c377200e0)","userDataDir":"/var/folders/xt/hbb7vf_d2_g6ks5b765c890c0000gn/T/.com.microsoft.edgemac.OYtxcq"},"networkConnectionEnabled":false,"pageLoadStrategy":"normal","platformName":"mac os x","proxy":{},"setWindowRect":true,"strictFileInteractability":false,"timeouts":{"implicit":0,"pageLoad":300000,"script":30000},"unhandledPromptBehavior":"dismiss and notify","webauthn:extension:credBlob":true,"webauthn:extension:largeBlob":true,"webauthn:extension:minPinLength":true,"webauthn:extension:prf":true,"webauthn:virtualAuthenticators":true},"sessionId":"fbe9a36e3a7e0932004fb5c0844a02ce"}}
[Chromedriver@512e] Determined the downstream protocol as 'W3C'
[debug] [Chromedriver@512e (fbe9a36e)] Changed state to 'online'
[AppiumDriver@5e37] New ChromiumDriver session created successfully, session a702c4b3-4e8c-4bc1-9e3f-c51fce0f9b24 added to master session list
[debug] [AppiumDriver@5e37] Event 'newSessionStarted' logged at 1690965024466 (01:30:24 GMT-0700 (Pacific Daylight Time))
[debug] [ChromiumDriver@6a51 (a702c4b3)] Cached the protocol value 'W3C' for the new session a702c4b3-4e8c-4bc1-9e3f-c51fce0f9b24
[debug] [ChromiumDriver@6a51 (a702c4b3)] Responding to client with driver.createSession() result: {"capabilities":{"platformName":"macOS","browserName":"MicrosoftEdge","automationName":"Chromium","executable":"/Users/kazu/selenium/driver/msedgedriver_115.0.1901.183-m1/msedgedriver"}}
[HTTP] <-- POST /session 200 2014 ms - 247

I wondered if the driver's default browser binary search referred to a chorme binary on your local.
Then,

"ms:edgeOptions": {
    "binary": "/path/to/msedge/browser/binary"
}

may help

@chobeat
Copy link
Author

chobeat commented Aug 2, 2023

Yes, now it uses the right binary, thanks

@KazuCocoa
Copy link
Member

Perhaps it was edgedriver's Linux specific behavior. They do not customize the binary search I guess.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@jlipps @chobeat @KazuCocoa