Lyubomir Aleksiev

@navaneetit09 currently I am getting the same issue. I've been trying to figure where exactly it's coming from.

@navaneetit09 I assume you moved on from this project, but I was able to fix the issue by changing the configuration as seen before. I am able to run tests...

@yashwanthkumar1796 not sure what 4.0.6 refers to. What I was forced to do myself is make a new framework from scratch. There are so many issues with this one. Most...

"dependencies": { "@wdio/appium-service": "^5.16.5", "@wdio/cli": "^5.16.7", "@wdio/cucumber-framework": "^5.16.6", "@wdio/local-runner": "^5.16.8", "@wdio/reporter": "^5.15.2", "appium": "^1.15.1", "appium-uiautomator2-driver": "^1.39.0", "chai": "^4.2.0", "chai-as-promised": "^7.1.1", "cmake-js": "^6.0.0", "cucumber": "^6.0.5", "cucumber-html-reporter": "^5.0.2", "fs-extra": "^8.1.0", "multiple-cucumber-html-reporter": "^1.13.1",...

@yashwanthkumar1796 a number of the libraries are going unused, haven't had the budged to clean up yet the framework properly, or to add all the features I'd like

I'm not really sure why you are getting this error. One of my theories is that you're lacking a driver for the browser as my framework is specifically built and...

@yashwanthkumar1796 sadly no. What I need I make myself.

This sounds like an issue with the chromedriver version you have. I think you might have gotten chromedriver version 85 which is why you are getting this error. In other...

@herrld the best way is to add version arguments to the webdriver-manager update and start commands. Updating and starting your webdriver with these commands will force the version to always...

In what way are you launching your selenium server?