-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
Closed
Closed
Copy link
Labels
Bug 🐛good first picka reasonable task to start getting familiar with the code basea reasonable task to start getting familiar with the code basehelp wantedIssues that are free to take by anyone interestedIssues that are free to take by anyone interested
Description
Have you read the Contributing Guidelines on issues?
- I have read the Contributing Guidelines on issues.
WebdriverIO Version
7.19
Node.js Version
18.3.0
Mode
Standalone Mode
Which capabilities are you using?
{
browserName: "chrome",
browserVersion: "latest",
platformName: "MacOS Catalina"
}What happened?
I'm getting this error. It has no helpful info whatsoever, no line numbers, nothing about what object is not interactable. below is the entirety of the output:
What is your expected behavior?
No response
How to reproduce the bug.
run npx wdio
Relevant log output
[chrome 103.0.5060.114 mac os x #0-0] element not interactable
(Session info: chrome=103.0.5060.114)
[chrome 103.0.5060.114 mac os x #0-0] element not interactable: element not interactable
[chrome 103.0.5060.114 mac os x #0-0] (Session info: chrome=103.0.5060.114)
[chrome 103.0.5060.114 mac os x #0-0] at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
Spec Files: 0 passed, 1 failed, 1 total (100% completed) in 00:01:31Code 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
Metadata
Metadata
Assignees
Labels
Bug 🐛good first picka reasonable task to start getting familiar with the code basea reasonable task to start getting familiar with the code basehelp wantedIssues that are free to take by anyone interestedIssues that are free to take by anyone interested