Sure, it’s very helpful for someone who knows what it means. While trying to follow that advice:
Question #1 Where exactly is that ChromeDriver for Appium in this Github repository? I cannot see any chromedriver.exe, chromedriver.js (or something like that) that is suposed to fix the issue here
Question #2 What exactly should be replaced and where exactly? Again, I cannot see any chromedriver.exe, chromedriver.js (or something like that) that is suposed to be fixed here:
Or does it mean that the issue can be fixed just by replacing any chromedriver.js which happens to be in C:\Users\<user_name>\AppData\Roaming\npm\node_modules\appium\node_modules\appium-chromedriver with any chromedriver.js which happens to be in GitHub - appium/appium-chromedriver: Node.js wrapper around Chromedriver ?
Question #3 If this is such a common error, would not it be very nice of Katalon to be more specific in their instructions? Wouldn’t it be very helpfull to show all the steps needed to fix this common error (with screenshots or maybe even video), for example, in case of Pixel 5 API 28 emulator used in Katalon’s examples
after following which I’m seeing the common error






