npm run protractor doesn't work on Mac OS X Yosemite machine

[carusog]

Hi, trying to run protractor on Mac OS X Yosemite, node v0.12.0, npm 2.5.1 I get the following error (notice [launcher] Error: Could not find chromedriver at /Users/papple/Devel/angular-phonecat/node_modules/protractor/selenium/chromedriver.exe ):

angular-phonecat git:(96a9b5b) npm run protractor

> angular-phonecat@0.0.0 preprotractor /Users/papple/Devel/angular-phonecat
> npm run update-webdriver


> angular-phonecat@0.0.0 preupdate-webdriver /Users/papple/Devel/angular-phonecat
> npm install

npm WARN package.json karma-chrome-launcher@0.1.7 No README data

> selenium-chromedriver@0.0.2 install /Users/papple/Devel/angular-phonecat/node_modules/selenium-chromedriver
> node install

Downloading http://chromedriver.storage.googleapis.com/2.8/chromedriver_mac32.zip
Saving to /var/folders/41/0fkmgjl13lq332yk4l_fplbm0000gn/T/selenium-chromedriver115112-46057-c53p2z/chromedriver.zip
Receiving...
Received 781K...
Received 1564K...
Received 2346K...
Received 3128K...
Received 3967K...
Received 4749K...
Received 5531K...
Received 6313K...
Received 7096K...
Received 7878K...
Received 8311K total.
/var/folders/41/0fkmgjl13lq332yk4l_fplbm0000gn/T/selenium-chromedriver115112-46057-zqxgoo
Extracting zip contents
Writing location.txt file
Done. chromedriver binary available at /Users/papple/Devel/angular-phonecat/node_modules/selenium-chromedriver/bin/chromedriver

> angular-phonecat@0.0.0 postinstall /Users/papple/Devel/angular-phonecat
> bower install


> angular-phonecat@0.0.0 update-webdriver /Users/papple/Devel/angular-phonecat
> webdriver-manager update

selenium standalone is up to date.
chromedriver is up to date.

> angular-phonecat@0.0.0 protractor /Users/papple/Devel/angular-phonecat
> protractor test/protractor-conf.js

util.puts: Use console.log instead
Using ChromeDriver directly...
[launcher] Error: Could not find chromedriver at /Users/papple/Devel/angular-phonecat/node_modules/protractor/selenium/chromedriver.exe

npm ERR! Darwin 14.1.0
npm ERR! argv "node" "/usr/local/bin/npm" "run" "protractor"
npm ERR! node v0.12.0
npm ERR! npm  v2.5.1
npm ERR! code ELIFECYCLE
npm ERR! angular-phonecat@0.0.0 protractor: `protractor test/protractor-conf.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the angular-phonecat@0.0.0 protractor script 'protractor test/protractor-conf.js'.
npm ERR! This is most likely a problem with the angular-phonecat package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     protractor test/protractor-conf.js
npm ERR! You can get their info via:
npm ERR!     npm owner ls angular-phonecat
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /Users/papple/Devel/angular-phonecat/npm-debug.log

[jpaljasma]

I got it working by changing package.json

Set devDependencies.protractor to be "*", removed node_modules, ran npm install and npm run update-webdriver

[gjermundgaraba]

I can confirm that the solution from @jpaljasma works.

[mannyfu]

I tried @jpaljasma 's approach but it didn't work for me. Any idea?
It doesn't happen when all the tests are successful, only when there is a failure.
Let me elaborate a bit on what happened to me.

1. I followed the same steps to change the package.son for the protractor dependency and performed a npm install.
2. I did 'npm run update-webdriver'
3. If I do not have any errors in my test, everything looks fine
4. If there is any test failed, then I got the following trace (same exact trace as before the change)

npm ERR! Darwin 14.1.0
npm ERR! argv "node" "/usr/local/bin/npm" "run" "protractor"
npm ERR! node v0.12.0
npm ERR! npm v2.5.1
npm ERR! code ELIFECYCLE
npm ERR! angular-phonecat@0.0.0 protractor: protractor test/protractor-conf.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the angular-phonecat@0.0.0 protractor script 'protractor test/protractor-conf.js'.
npm ERR! This is most likely a problem with the angular-phonecat package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! protractor test/protractor-conf.js
npm ERR! You can get their info via:
npm ERR! npm owner ls angular-phonecat
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR! /Users/papple/Devel/angular-phonecat/npm-debug.log

[carusog]

@jpaljasma Thanks for your help, but it doesn't work here either.

[ereze]

Worked for me, thanks!

[sai29]

@jpaljasma How do I remove all the node_modules,? Should I just delete the node_modules folder or is there a command?

[gjermundgaraba]

I just deleted the node_modules folder. It will be regenerated on npm install.

[sai29]

Thanks. It works fine when all the tests pass, but for a failing tests it shows which tests are failing and an error code 1 subsequently exits with the same error as for @mannyfu above.

[skjolber]

I had the same problem running linux (fedora 21) and the solution from jpaljasma worked for me as well.

[HughxDev]

@jpaljasma’s solution works for me on Mac OS X 10.9.5.

[mmadej]

works for me

[daple]

@jpaljasma’s solution works for me on Mac OS X 10.10.2 as well, thanks a lot!

[kevinhooke]

same issue, steps from @jpaljasma worked great - thanks!

[valsouche]

On macbook pro Yosemite, I solved the same error by downloading : https://sites.google.com/a/chromium.org/chromedriver/downloads manualy and copy in the good repertory. This error is due to a damage ZIP file.

I hope you'll resolve your problem.

[zanify]

I just followed @Tintin34 suggestion and it worked for me, also on a mbp yosemite.
Was stuck with e2e test on the angular tutorial, downloaded the mac zip from the linked repository, unzipped it and put it in the ... /node_modules/protractor/selenium/ directory.

[lukenofurther]

@tintin3's solution worked for me. I'm on Yosemite 10.10.2. The existing chromedriver zip file would not extract, but the 2.14 mac zip downloaded from http://chromedriver.storage.googleapis.com/index.html?path=2.14/ unzipped fine and protractor ran alright.

[jsphstls]

@Tintin34 solution also worked for me.

I ran npm run update-webdriver after and received:

selenium standalone is up to date. chromedriver is up to date.

[akm]

@Tintin34 solution also works for me on Mac OS X 10.10.3 - thanks!

[mlg87]

thanks @jpaljasma! worked like a charm

[palerdot]

I had this same problem in Ubuntu. What worked for me

• npm install chromedriver - This installed the chromedriver in angular-phonecat/node_modules/protractor/node_modules/chromedriver
• copy the zip file from the lib directory from the above installed location and put it in /angular-phonecat/node_modules/protractor/selenium/
• unzip the copied zip file to extract the binary. Now run npm run protractor

The problems for me seems to be invalid chromedriver zip file in /angular-phonecat/node_modules/protractor/selenium/. Getting the correct zip file and extracting the binary solved the issue.

There seems to too much issues on this on different OSes. Angular team should make a better documentation on this problem.

[karlli1976]

Thanks you @jpaljasma , your solution works for me :-)

Yosemite: 10.10.3

[sygint]

Thanks @jpaljasma, solution worked, Ubuntu 14.04

[ygarbage]

Thanks @jpaljasma, it worked on Debian 7.8.

[nickleus]

@Tintin34 thx :) downloaded the zip to ~/Downloads
unzipped it
copied the file "chromedriver" to folder /path-to-/angular-phonecat/node_modules/protractor/selenium/

[valsouche]

You're welcome :)

[halfzebra]

I have managed to fix similar issue by updating Java.

[mayra-cabrera]

Thanks @Tintin34! Your solution works on OS X 10.10.3 :)

[machinefixer]

@jpaljasma 's solution works for me, thx!

[warles34]

@Tintin34 solution solved my problem, and looks more solid and safe =D

[frak]

Thanks @Alecsandre - your solution worked for me

[AshCoolman]

I had to ensure I run webdriver-manager update from the version being used in the npm module e.g.
./node_modules/protractor/bin/webdriver-manager update

[amandaol]

@Alecsandre fix + @jpaljasma fix worked for me.

While the first fix alone seems to do the trick, adding @jpaljasma removed the rest of the errors that were printing out.

[jasunde]

On Mac OS X 10.11.1 I find that replacing chromeOnly: true with directConnect: true in test/protractor-conf.js solves the error without any additional npm update-webdriver.

[amaechler]

@jasunde fix worked for me.

[McAlyster]

@jasunde fix worked for me

[stevenluong]

@jasunde fix worked for me as well,thanks !

[SingpointGitHub]

@jasunde fix worked for me on Windows 10 x64

[rpajaziti]

@Tintin34 or now @valsouche solution worked for me. Tried almost every other solution but without luck.
If you dont have selenium folder under protractor(like me), then create a folder with that name and paste chromedriver in there. Try this solution before others. It will save your time, belive me.

[chadlajeunesse]

@jasunde fix also worked for me, thanks.

[jonathanboswell]

So spent a good bit of time looking into "Why?" @jasunde fix works.

In the office here we have Linux and Mac workstations. The default path to Chrome binary in Linux is /usr/bin/google-chrome and in OSX 10.10 it's /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome

When 'npm install' builds 'node_modules' and if that folder gets added to the Git repository of a project where users have different operating systems, protractor isn't able to find the Chrome executable.

A simple test which shows if this is the problem:
Fails: npm run protractor
But works: protractor ./path/to/protractor.conf.js

[gkalpak]

And that's a good examples of the reasons why one should not commit the node_modules/ directory 😃

[jonathanboswell]

Totally @gkalpak! And we fixed that stat on the dev's repository who had done that

[kematzy]

@jasunde fix worked for me on Mac OS X 10.11.3 (El Capitan) with node 5.0.0. Thanks a lot!

[liebecampbellroberts]

Hi,

I am using Mac OSX Yosimite 10.10.5

Just to say that I had to set "directConnect: true" in the protractor-conf.js file AND change "baseUrl", to 127.0.0.1:8000 (probably because I have not set the 127... to 'localhost' in my hosts file). So protractor-conf.js looks something like this:

...
directConnect: true,

chromeOnly: true,

baseUrl: 'http://127.0.0.1:8000/',
...

Thanks @Alecsandre and thanks guys, helped a lot!

[jquerygeek]

Still having the same issue as mentioned by @mannyfu
works fike when test pass, but getting error with failed test.
any idea? @jpaljasma

[carrigmore]

I find add sudo at the begin of the command will resolve the problem.

[schandra-rpx]

chromeOnly: true,
directConnect: true

this worked for me in osx 10.11.5

[gkalpak]

@schandra-rpx, ooc is chromeOnly: true necessary? Afaict, the version of protractor used in the tutorial only cares about directConnect: true.

[norbertsienkiewicz]

I was able to run via protractor ./test/protractor.config.js, but couldn't make it from npm run test-e2e (which had the same command as I was using in command line).

@AshCoolman fix worked for me OSX El Capitan (10.11.4)