-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
Closed
Labels
Description
Have you read the Contributing Guidelines on issues?
- I have read the Contributing Guidelines on issues.
WebdriverIO Version
latest
Node.js Version
v22.12.0
Mode
WDIO Testrunner
Which capabilities are you using?
`capabilities: [
{
// capabilities for local Appium web tests on an Android Emulator
platformName: "Android",
// browserName: "Chrome",
"appium:automationName": "UiAutomator2",
"appium:options": {
udid: "emulator-5554",
},
port: 4724,
},
],`
Above code is the worked one but if we move automationName inside "appium:options" the error will occur for E.g.
`capabilities: [
{
// capabilities for local Appium web tests on an Android Emulator
platformName: "Android",
// browserName: "Chrome",
// "appium:automationName": "UiAutomator2",
"appium:options": {
udid: "emulator-5554",
automationName: "UiAutomator2",
},
port: 4724,
},
],`What happened?
While running test the @wdio/appium-service will skip launching appium server if we have the capabilities with automationName inside "appium:options"
Error msg: 2024-12-20T13:41:20.959Z WARN @wdio/appium-service: Could not identify any capability that indicates a local Appium session, skipping Appium launch
What is your expected behavior?
The wdio/appium-service should run with the capabilities like i mentioned
How to reproduce the bug.
Run test with the config above
Relevant log output
2024-12-20T13:41:20.959Z WARN @wdio/appium-service: Could not identify any capability that indicates a local Appium session, skipping Appium launchCode of Conduct
- I agree to follow this project's Code of Conduct
Is there an existing issue for this?
- I have searched the existing issues
Reactions are currently unavailable