Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Cannot launch Chrome: OSX 10.9.3, Selenium 2.42.0, chromedriver 2.10
See original GitHub issueTrying to run protractor tests on OSX. We get the error below. Have tried a variety of fixes suggested. I think we’re running the latest stand-alone server and chrome driver. Thoughts?
/Users/riley/dash.frontend/node_modules/grunt-protractor-runner/node_modules/protractor/node_modules/selenium-webdriver/lib/atoms/error.js:109
var template = new Error(this.message);
^
UnknownError: null
at new bot.Error (/Users/riley/dash.frontend/node_modules/grunt-protractor-runner/node_modules/protractor/node_modules/selenium-webdriver/lib/atoms/error.js:109:18)
at Object.bot.response.checkResponse (/Users/riley/dash.frontend/node_modules/grunt-protractor-runner/node_modules/protractor/node_modules/selenium-webdriver/lib/atoms/response.js:106:9)
at /Users/riley/dash.frontend/node_modules/grunt-protractor-runner/node_modules/protractor/node_modules/selenium-webdriver/lib/webdriver/webdriver.js:134:24
at /Users/riley/dash.frontend/node_modules/grunt-protractor-runner/node_modules/protractor/node_modules/selenium-webdriver/lib/goog/base.js:1243:15
at webdriver.promise.ControlFlow.runInNewFrame_ (/Users/riley/dash.frontend/node_modules/grunt-protractor-runner/node_modules/protractor/node_modules/selenium-webdriver/lib/webdriver/promise.js:1531:20)
at notify (/Users/riley/dash.frontend/node_modules/grunt-protractor-runner/node_modules/protractor/node_modules/selenium-webdriver/lib/webdriver/promise.js:354:12)
at notifyAll (/Users/riley/dash.frontend/node_modules/grunt-protractor-runner/node_modules/protractor/node_modules/selenium-webdriver/lib/webdriver/promise.js:323:7)
at resolve (/Users/riley/dash.frontend/node_modules/grunt-protractor-runner/node_modules/protractor/node_modules/selenium-webdriver/lib/webdriver/promise.js:301:7)
at fulfill (/Users/riley/dash.frontend/node_modules/grunt-protractor-runner/node_modules/protractor/node_modules/selenium-webdriver/lib/webdriver/promise.js:421:5)
at /Users/riley/dash.frontend/node_modules/grunt-protractor-runner/node_modules/protractor/node_modules/selenium-webdriver/lib/goog/base.js:1243:15
==== async task ====
WebDriver.createSession()
at Function.webdriver.WebDriver.acquireSession_ (/Users/riley/dash.frontend/node_modules/grunt-protractor-runner/node_modules/protractor/node_modules/selenium-webdriver/lib/webdriver/webdriver.js:131:49)
at Function.webdriver.WebDriver.createSession (/Users/riley/dash.frontend/node_modules/grunt-protractor-runner/node_modules/protractor/node_modules/selenium-webdriver/lib/webdriver/webdriver.js:111:30)
at Builder.build (/Users/riley/dash.frontend/node_modules/grunt-protractor-runner/node_modules/protractor/node_modules/selenium-webdriver/builder.js:106:20)
at HostedDriverProvider.getDriver (/Users/riley/dash.frontend/node_modules/grunt-protractor-runner/node_modules/protractor/lib/driverProviders/hosted.js:54:9)
at /Users/riley/dash.frontend/node_modules/grunt-protractor-runner/node_modules/protractor/lib/runner.js:207:35
at _fulfilled (/Users/riley/dash.frontend/node_modules/grunt-protractor-runner/node_modules/protractor/node_modules/q/q.js:797:54)
at self.promiseDispatch.done (/Users/riley/dash.frontend/node_modules/grunt-protractor-runner/node_modules/protractor/node_modules/q/q.js:826:30)
at Promise.promise.promiseDispatch (/Users/riley/dash.frontend/node_modules/grunt-protractor-runner/node_modules/protractor/node_modules/q/q.js:759:13)
at /Users/riley/dash.frontend/node_modules/grunt-protractor-runner/node_modules/protractor/node_modules/q/q.js:525:49
Issue Analytics
- State:
- Created 9 years ago
- Comments:25 (6 by maintainers)
Top Results From Across the Web
Fixing error: “chromedriver” cannot be opened because the ...
Solution: 1) Find a path to chromedriver binary; 2) Tell MacOS to trust the binary by ... Unable to launch the chrome browser...
Read more >MacOS Catalina(v 10.15.3): Error: “chromedriver” cannot be ...
Navigate to where your chrome driver application is saved / downloaded · Right click and select Open with · Select open with Terminal...
Read more >Unable to launch chrome browser on Mac - Tutorialspoint
New Selenium IDE Step1 − Navigate to the link:https://sites.google.com/chromium.org/driver/ and click on the download link of the chromedriver ...
Read more >How to Install Chrome Driver on Mac - Software Test Academy
Step1: Download Chrome Driver · Step2: Move the driver to the /usr/local/bin folder · 2 thoughts on “How to Install Chrome Driver on...
Read more >How to setup Chrome driver with Selenium on MacOS - Edureka
Open up Terminal. · Run sudo nano /etc/paths. · Enter your password. · Go to the bottom of the file and enter the...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I downgraded my chromedriver to 2.9 in /usr/bin location and /usr/local/lib/node_modules/protractor/selenium/ location (from 2.15) and it started working as expected.
I Downgraded from 2.10 to 2.9 as coderigo said and it solved the problem. I’m on chrome v 40.