If the browser does not load while recording tests on Low Code Automation and you see the error “Different chromedriver path already configured in System environment variables“, it could be because a different chromedriver path might be already set in your System environment or PATH variables. To confirm, try these commands from the command prompt:
Windows:
- --> chromedriver --version [This should be compatible with your current Chrome browser version]
- --> where chromedriver.exe
MacOS
- --> chromedriver --version [This should be compatible with your current Chrome browser version]
- --> which chromedriver
Check if this returns a path that you used earlier to install chromedriver.
The desktop app automatically takes care of managing the chromedriver versions on your machine. If you have a different chromedriver path configured in your System environment or PATH variables, please remove the path and try relaunching the Low Code Automation desktop app again.
Please contact support if you still face any issues after trying the above steps.
