-
-
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
8.16.9
Node.js Version
20.6.21 - 18.17.1 - 14.21.2
Mode
WDIO Testrunner
Which capabilities are you using?
{
// capabilities for local Appium web tests on an Android Emulator
platformName: 'Android',
browserName: 'Chrome',
'appium:deviceName': 'Nexus 7 (2012) API 30',
'appium:platformVersion': '12.0',
'appium:automationName': 'UiAutomator2'
}What happened?
I tried to run the example e2e test template on an Android Emulator but it seems to fail anyways. I tried to change to different Node.js versions, deleting Node.js and reinstalling it from scratch and reinstalling Appium but nothing seems to work.
What is your expected behavior?
No response
How to reproduce the bug.
Create a package.json file:
npm init -y
Start wdio setup
npm init wdio .
Run wdio
npx wdio
Relevant log output
`PS C:\Users\erodriguez\Documents\test\wdio-gps> npx wdio
Execution of 1 workers started at 2023-09-15T16:32:57.422Z
2023-09-15T16:32:57.554Z INFO @wdio/cli:launcher: Run onPrepare hook
2023-09-15T16:32:57.562Z INFO @wdio/appium-service: Will spawn Appium process: cmd /c node C:\Users\erodriguez\Documents\test\wdio-gps\node_modules\appium\index.js --base-path /
2023-09-15T16:33:10.509Z ERROR @wdio/cli:utils: A service failed in the 'onPrepare' hook
Error: Appium exited before timeout (exit code: 1)
at ChildProcess.<anonymous> (file:///C:/Users/erodriguez/Documents/test/wdio-gps/node_modules/@wdio/appium-service/build/launcher.js:135:22)
at Object.onceWrapper (node:events:629:26)
at ChildProcess.emit (node:events:514:28)
at ChildProcess.emit (node:domain:489:12)
at ChildProcess._handle.onexit (node:internal/child_process:291:12)
Continue...
2023-09-15T16:33:10.515Z INFO @wdio/cli:launcher: Run onWorkerStart hook
2023-09-15T16:33:10.518Z INFO @wdio/local-runner: Start worker 0-0 with arg:
[0-0] Error: "ts-node/esm/transpile-only 'resolve'" did not call the next hook in its chain and did not explicitly signal a short circuit. If this is intentional, include `shortCircuit: true` in the hook's return.
[0-0] at new NodeError (node:internal/errors:405:5)
[0-0] at ESMLoader.resolve (node:internal/modules/esm/loader:843:13)
[0-0] at ESMLoader.getModuleJob (node:internal/modules/esm/loader:424:7)
[0-0] FAILED
2023-09-15T16:33:11.117Z INFO @wdio/cli:launcher: Run onWorkerEnd hook
2023-09-15T16:33:11.118Z INFO @wdio/cli:launcher: Run onComplete hook
Spec Files: 0 passed, 1 failed, 1 total (100% completed) in 00:00:13
2023-09-15T16:33:11.125Z INFO @wdio/local-runner: Shutting down spawned worker
2023-09-15T16:33:11.391Z INFO @wdio/local-runner: Waiting for 0 to shut down gracefully
2023-09-15T16:33:11.392Z INFO @wdio/local-runner: shutting downCode 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