protractor: Protractor 5.1.1 doesn't work with Chrome 57

(node:9828) DeprecationWarning: os.tmpDir() is deprecated. Use os.tmpdir() instead.
[11:48:42] I/launcher - Running 1 instances of WebDriver
[11:48:42] I/local - Starting selenium standalone server...
[11:49:12] E/launcher - Error: Error: Timed out waiting for the WebDriver server at http://10.10.10.76:45678/wd/hub
    at onError (C:\projects\JustEat.TopPlacement.ManagementWeb\src\JustEat.TopPlacement.ManagementWeb.ProtractorTests\node_modules\selenium-webdriver\http\util.js:102:16)
    at process._tickCallback (internal/process/next_tick.js:103:7)
[11:49:12] E/launcher - Process exited with error code 100

Protractor.conf.js looks like this:

    allScriptsTimeout: 30000,
    specs: [
        "./**tests/*.js"
    ],
    capabilities: {
        browserName: "chrome",
        chromeOptions: {
            args: ["--test-type", "--no-sandbox"],
        },
        loggingPrefs: {
            browser: "ALL"
        }
    },
    jasmineNodeOpts: {
        showColors: true,
        defaultTimeoutInterval: 5 * 60 * 1000
    },

About this issue

Original URL
State: closed
Created 7 years ago
Reactions: 5
Comments: 34 (16 by maintainers)

Commits related to this issue

Added Chrome driver 2.28 to support Chrome 57 See angular/protractor#4146 — committed to serenity-js/tutorial-from-scripts-to-serenity by jan-molak 7 years ago
Add test for https://github.com/angular/protractor/issues/4146#issuecomment-286261677 — committed to NickTomlin/protractor-mcve by NickTomlin 7 years ago

Most upvoted comments

Just for completeness, thanks to @NickTulett suggestion, you can turn off the password manager (and infobars) in Protractor thusly…

    capabilities: {
        browserName: 'chrome',
        chromeOptions: {
            args: [
                '--disable-infobars'
            ],
            prefs: {
                // disable chrome's annoying password manager
                'profile.password_manager_enabled': false,
                'credentials_enable_service': false,
                'password_manager_enabled': false
            }
        }
    },

qualityshepherd on Mar 24, 2017

UPDATE: removing “–remote-debugging-port” option from Protractor config (but not Karma!) solves the issue (understandably, because it interferes with ChromeDriver on that port)! I.e. Protractor 5.1.1 works with Chrome 57 on a headless system without Xvfb. https://github.com/angular/protractor/issues/4164#issuecomment-288909191 if anyone is interested.

dinvlad on Mar 24, 2017

@qualityshepherd To get rid of the password prompts (in a node.js client - please translate for your usage): var prefs = utils.objectToMap({ “profile.password_manager_enabled”: false, “credentials_enable_service”: false, “password_manager_enabled”: false }); chromeOptions.setExperimentalOption(“prefs”, prefs);

NickTulett on Mar 19, 2017

Yeah, Chrome 65 now shows the infobar, with no apparent workaround. It caused my visual tests to fail. They also made a change to how you can workaround IDs starting with numbers… broke a couple tests there too. #thankschrome

qualityshepherd on Mar 16, 2018

Yeah, Nick. Seems like I’m having multiple issues with Chrome 57 (and 56). I opened an issue for my linux issue. From the mac side, I’m still figuring it out. Chrome does crash for me, when I interfere with the running test, by trying to dismiss the “Chrome is being controlled…” infobar.

FWIW, Chrome v55 (which is the cutoff for Protractor v5x), works fine for me… in case that helps anyone else seeing this.

qualityshepherd on Mar 18, 2017

So yeah this works, assuming protractor 5.0

gulp.task('protractor-install', function(done){
    child_process.spawn(getProtractorBinary('webdriver-manager'), ['update', '--versions.chrome=2.28'], {
        stdio: 'inherit'
    }).once('close', done);
});

aarr0n on Mar 14, 2017