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.

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

Driver failed to start session with message "No matching capabilities found" #275

Closed
SharpQ opened this issue Feb 29, 2024 · 3 comments
Closed

Comments

@SharpQ
Copy link

SharpQ commented Feb 29, 2024

Hello,
I am using Chromium driver for some time and recently updated it from "1.2.68" to "1.3.15" version.
After driver update, I receive error "session not created: No matching capabilities found" each time on session start.
I didn't change any capabilities from "1.2.68" version and on that version everything works fine.
Could you advise how can I resolve this error and use latest chromium driver version?

MacOS: 11.2.3
Appium Server: 2.2.2
Appium-Python-Client: 3.1.0
Chromium driver: 1.3.15

Driver capabilities:
Creating session with W3C capabilities: {
"alwaysMatch": {
"platformName": "macOS",
"browserName": "chrome",
"appium:automationName": "Chromium",
"appium:autodownloadEnabled": true
},
"firstMatch": [
{}
]
}

I am also attaching Appium log files:
appium_logs.log

@jlipps
Copy link
Member

jlipps commented Feb 29, 2024

try a platformName of 'mac' instead?

@KazuCocoa
Copy link
Member

Yes, it looks like chrome stricted the platformName to follow w3c webdriver spec chromium/chromium@cac9966
so macOS might be mac

@SharpQ
Copy link
Author

SharpQ commented Mar 1, 2024

try a platformName of 'mac' instead?

Just checked and it worked. Thanks a lot!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants