Firefox 50.1.0 not working #3823

stanbe · 2016-12-14T14:11:05Z

Bug report

Node Version: 6.7.0
Protractor Version: 4.0.10
Angular Version: 2.1.0
Browser(s): Firefox 50.1.0
Operating System and Version Win8.1 Enterprise
Your protractor configuration file

exports.config = {
    capabilities: {
        'browserName': 'firefox'
    },
    specs: ['**/*.e2e.spec.js'],
    useAllAngular2AppRoots: true,
    baseUrl: 'http://localhost:64065/',
    directConnect : true
};

A relevant example test

describe('Expense overview list', function () {

    it('should should have Anakin Skywalker as first entry', function () {
        browser.get('/home');
        expect(browser.getTitle()).toEqual('Angular');

        browser.get('/overview');

        expect(element(by.id('00000000-0000-0000-0000-000000000001')).getText()).toEqual('ANAKIN SKYWALKER');
    });
});

Output from running the test

[15:08:27] I/direct - Using FirefoxDriver directly...
[15:08:27] I/launcher - Running 1 instances of WebDriver
[15:09:12] E/launcher - Timed out waiting for the WebDriver server at http://127.0.0.1:60626/hub
[15:09:12] E/launcher - Error: Timed out waiting for the WebDriver server at http://127.0.0.1:60626/hub
    at Error (native)
    at onError (C:\Users\john\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\http\util.js:87:11)
    at ManagedPromise.invokeCallback_ (C:\Users\john\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\promise.js:1379:14)
    at TaskQueue.execute_ (C:\Users\john\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\promise.js:2913:14)
    at TaskQueue.executeNext_ (C:\Users\john\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\promise.js:2896:21)
    at asyncRun (C:\Users\john\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\promise.js:2775:27)
    at C:\Users\john\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\promise.js:639:7
    at process._tickCallback (internal/process/next_tick.js:103:7)
From: Task: WebDriver.createSession()
    at Function.createSession (C:\Users\john\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\webdriver.js:329:24)
    at Driver (C:\Users\john\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\firefox\index.js:386:38)
    at Direct.getNewDriver (C:\Users\john\AppData\Roaming\npm\node_modules\protractor\built\driverProviders\direct.js:75:26)
    at Runner.createBrowser (C:\Users\john\AppData\Roaming\npm\node_modules\protractor\built\runner.js:198:43)
    at C:\Users\john\AppData\Roaming\npm\node_modules\protractor\built\runner.js:285:30
    at _fulfilled (C:\Users\john\AppData\Roaming\npm\node_modules\protractor\node_modules\q\q.js:834:54)
    at self.promiseDispatch.done (C:\Users\john\AppData\Roaming\npm\node_modules\protractor\node_modules\q\q.js:863:30)
    at Promise.promise.promiseDispatch (C:\Users\john\AppData\Roaming\npm\node_modules\protractor\node_modules\q\q.js:796:13)
    at C:\Users\john\AppData\Roaming\npm\node_modules\protractor\node_modules\q\q.js:556:49
    at runSingle (C:\Users\john\AppData\Roaming\npm\node_modules\protractor\node_modules\q\q.js:137:13)
[15:09:12] E/launcher - Process exited with error code 199

Steps to reproduce the bug
just run protractor protractor.conf.js
The URL you are running your tests against (if relevant)
see protractor.conf.js

Firefox is starting but nothing happens, just an empty screen.

The text was updated successfully, but these errors were encountered:

Xotabu4 · 2016-12-14T18:34:49Z

+1

wh33ler · 2016-12-16T06:13:56Z

+1

BishuSinha · 2016-12-18T23:27:55Z

+1

juliemr · 2016-12-19T19:19:27Z

Right, firefox is very confused with the latest versions of selenium server. We're investigating what's compatible with what now, with marionettedriver and geckodriver and various versions of selenium. Stay tuned.

juliemr · 2016-12-19T19:20:14Z

See also #3750

sjelin · 2016-12-22T04:28:23Z

(assigning to you @mgiambalvo because I didn't assign many over issues to you, and I feel like I need to balance)

heathkit · 2017-01-10T23:30:41Z

We will need to update the directConnect provider for Selenium 3.0. However, Firefox is still broken. We can address this once Firefox 51 ships.

heathkit · 2017-01-18T21:59:08Z

Note that as of Protractor 5.1, we'll support Firefox 51+ and greater. Older versions of Firefox won't work with directConnect, but may work with selenium server and marionette: false. A bug was introduced in Selenium 3.0.0 that breaks the JS Firefox driver (SeleniumHQ/selenium#3115) - it's been fixed, but won't be available until the next release of selenium server (3.0.2 or greater). So to use the latest Firefox, you'll need to use selenium server 3.0.0-beta4 like so:

webdriver-manager update
wget http://selenium-release.storage.googleapis.com/3.0-beta4/selenium-server-standalone-3.0.0-beta4.jar -P ./node_modules/webdriver-manager/selenium
webdriver-manager start --versions.standalone 3.0.0-beta4

sdseenu · 2017-02-03T05:52:33Z

Protractor test is not running on FireFox 51+ for Windows 8.1 64bit

Browser is open but do not have any action take place getting below error

theandrewlane · 2017-02-08T21:10:27Z

+1

sjelin · 2017-02-08T22:18:45Z

+ @seanmay

esoyke · 2017-02-09T15:33:36Z

Thanks @mgiambalvo. It was driving me nuts why during the middle of the day, Protractor/Firefox had been working fine then suddenly Firefox wouldn't even go to the URL but instead timed out. Looking at Firefox's update history I discovered it had auto-updated from 50.1.0 to 51.0.1 while I was at lunch!

There were a few extra hoops I personally had to jump through. Some are Mac-specific, but this might help speed up others with the same issues.

1- OSX doesn't have wget installed by default, but it's an easy install
2- The webdriver-manager start failed as it expected the JAR in a different location (/Users/esoyke/.nvm/versions/node/v6.2.2/lib/node_modules/protractor/node_modules/webdriver-manager/selenium/selenium-server-standalone-3.0.0-beta4.jar). I manually moved it there.
3- Ran into another error starting Selenium (Exception in thread "main" java.lang.UnsupportedClassVersionError: org/openqa/grid/selenium/GridLauncherV3 : Unsupported major.minor version 52.0 ). The Mac had Java 7 so I upgraded to 8.
4- Was still getting the same error until I removed the "directConnect: true" from my config.

Back in the saddle!

JoshLipps · 2017-02-15T07:46:50Z

For me I also had to modify the original workaround slightly:

wget http://selenium-release.storage.googleapis.com/3.0-beta4/selenium-server-standalone-3.0.0-beta4.jar -P ./node_modules/protractor/node_modules/webdriver-manager/selenium
./node_modules/.bin/webdriver-manager start --versions.standalone 3.0.0-beta4

joeydaowang · 2017-02-27T01:14:39Z

Does anyone know whether Selenium 3.1.0 works or not?

JoshLipps · 2017-02-27T07:31:29Z

For me the release of 3.1.0 does seem to have fixed things. (I no longer have to use the above work around)

joeydaowang · 2017-02-27T20:53:38Z

@JoshLipps does 'directConnect: true' work for you?

rahulmr · 2017-03-15T04:35:07Z

directConnect:true not working for me on Firefox 52.0 32bit and gecko 15.0 while it works with selenium-standalone 3.3.1 but only when I provide below options and start server manually in another git bash shell.

-Dwebdriver.gecko.driver=./node_modules/protractor/node_modules/webdriver-manager/selenium/geckodriver-v0.15.0.exe

see logs here

benitogf · 2017-03-15T06:42:58Z

Same issue as @rahulmr here https://travis-ci.org/benitogf/corsarial

E/launcher - Unable to parse new session response: {"value": {"sessionId":"4c02cc6a-c507-4b7a-bf77-d0fa65abe8b6","value":{"XULappId":"{ec8030f7-c20a-464f-9b0e-13a3a9e97384}","acceptSslCerts":false,"appBuildId":"20170125094131","browserName":"firefox","browserVersion":"51.0.1","command_id":1,"count":1,"platform":"LINUX","platformName":"linux","platformVersion":"4.8.12-040812-generic","processId":7886,"proxy":{},"raisesAccessibilityExceptions":false,"rotatable":false,"specificationLevel":0,"takesElementScreenshot":true,"takesScreenshot":true,"version":"51.0.1"}}}

RaviKlair · 2017-04-10T22:59:36Z

@rahulmr how did you start the server manually with the mentioned option ?

rahulmr · 2017-04-11T02:29:38Z

@RaviKlair its a simple one. see below

java -Dwebdriver.gecko.driver="./node_modules/protractor/node_modules/webdriver-manager/selenium/geckodriver-v0.15.0.exe" -jar selenium-standalone-3.3.1,jar `

RaviKlair · 2017-04-11T16:31:43Z

@rahulmr where exactly is your .jar file present ? mine is in the same location as gecko driver.

And if I copy the .jar to the root then I get the following

jlin412 · 2017-04-11T16:51:57Z

It works with this combination selenium server 3.3.1 and gecko 0.15 and firefox 52. There is a bug for firefox less than 52.

…

On Tue, Apr 11, 2017 at 12:31 PM, CodeJockey ***@***.***> wrote: @rahulmr <https://github.com/rahulmr> where exactly is your .jar file present ? mine is in the same location as gecko driver. [image: image] <https://cloud.githubusercontent.com/assets/24551166/24919740/7e0faedc-1e99-11e7-85ef-1859bb18ba30.png> — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#3823 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABF6jYdEbIlFiUIGc-o0xBPX3m0FaLUKks5ru6r0gaJpZM4LM9nn> .

RaviKlair · 2017-04-11T17:31:50Z

i'm using protractor 5.0.0, firefox 52, angular1 application

It's installing selenium-server-standalone-2.53.1.jar

rahulmr · 2017-04-11T19:41:35Z

@RaviKlair sorry to confuse you. Here is the complete command and I am using protractor 5.1.1 here

D:\projects\gulp-protractor\example_2>java -Dwebdriver.gecko.driver=".\node_modules\protractor\node_modules\webdriver-manager\selenium\geckodriver-v0.15.0.exe" -jar .\node_modules\protractor\node_modules\webdriver-manager\selenium\selenium-server-standalone-3.3.1.jar

RaviKlair · 2017-04-11T19:56:11Z

@rahulmr Thanks for the detailed response! I'm able to start the server with the mentioned cmd but when I run a spec, its not grabbing the gecko driver present in selenium folder, rather its trying to find it in PATH.
Any comments ?

jlin412 · 2017-04-11T20:20:05Z

Currently, firefox doesn't work with direct connect with gecko driver 0.15. You need to set --seleniumAddress=

…

On Tue, Apr 11, 2017 at 3:56 PM, CodeJockey ***@***.***> wrote: @rahulmr <https://github.com/rahulmr> Thanks for the detailed response! I'm able to start the server with the mentioned cmd but when I run a spec, its not grabbing the gecko driver present in selenium folder, rather its trying to find it in PATH. Any comments ? [image: image] <https://cloud.githubusercontent.com/assets/24551166/24928130/28d9631e-1eb6-11e7-8210-818f25651f8c.png> — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#3823 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABF6jWYAWpXNoLzVFWnsvbEDgH2NdnUXks5ru9rdgaJpZM4LM9nn> .

rahulmr · 2017-04-11T20:30:10Z

@jlin412 is right . You need to set seleniumAddress in protractor.conf.js file like below

  seleniumAddress: 'http://localhost:4444/wd/hub',

RaviKlair · 2017-04-11T20:31:55Z

@rahulmr Right! I've added seleniumAddress: 'http://localhost:4444/wd/hub' in my conf file.
So, now if I run my test, it opens up firefox but closes it after 1 sec and spits out the following error

Sorry for spamming this thread

rahulmr · 2017-04-11T20:36:13Z

@RaviKlair you are right you should stop posting it here. Rather create your own repository and let's play it there. Create issue for yourself. May be you can create travis file. I will try to help you out there. It seems you are overriding some parameters.

jlin412 · 2017-04-11T20:37:56Z

I see this error if you are using firefox less than 52

…

On Tue, Apr 11, 2017 at 4:31 PM, CodeJockey ***@***.***> wrote: Right! I've added seleniumAddress: 'http://localhost:4444/wd/hub' in my conf file. So, now if I run my test, it opens up firefox but closes it after 1 sec and spits out the following error [image: image] <https://cloud.githubusercontent.com/assets/24551166/24929535/255a5b1c-1ebb-11e7-8026-564b452eb71f.png> Sorry for spamming this thread — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#3823 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABF6jUv-oX8f6sxoZ9h_m_qhHOOu6JQ2ks5ru-M-gaJpZM4LM9nn> .

rahulmr · 2017-04-11T20:38:55Z

@RaviKlair Few checkpoints though.

Firefox version (64 bit or 32 bit) 52 or greater
gecko version

RaviKlair · 2017-04-11T20:43:43Z

@rahulmr @jlin412 Apparently the protractor was not picking up the latest firefox version (52). Now with 52 the tests are running successfully. All it needed was a little nudge.
Thanks to you both!

mftaha · 2017-04-13T17:35:33Z

+1, still facing the issue on 5.1.1 FF 52.x

heathkit · 2017-05-01T02:22:22Z

See #4253 for the issues with directConnect and Firefox 52 in Protractor 5.1.1

pramodh06 · 2017-05-16T12:50:29Z

for this issue Firefox 52.0 and Protractor 5.1.1 is helpful

juliemr added browser: firefox status: needs investigation labels Dec 19, 2016

juliemr added the fixit: untriaged label Dec 19, 2016

sjelin assigned heathkit Dec 22, 2016

heathkit added type: bug and removed fixit: untriaged status: needs investigation labels Jan 10, 2017

heathkit mentioned this issue Jan 11, 2017

fix(firefox): Fix directConnect for Firefox 51+ #3953

Merged

heathkit added this to the 5.1 milestone Jan 18, 2017

heathkit added the status: fixed for next release label Jan 18, 2017

heathkit mentioned this issue Jan 18, 2017

Protractor failed to start firefox latest version - Accessibility support partially disabled #3980

Closed

heathkit closed this as completed in #3953 Jan 18, 2017

heathkit reopened this Jan 20, 2017

heathkit mentioned this issue Jan 20, 2017

Problem running Protractor 5.0.0 on FireFox #3993

Closed

heathkit changed the title ~~Firefox 50.1.0 not working with directConnect~~ Firefox 50.1.0 not working Jan 21, 2017

This was referenced Jan 21, 2017

Protractor test is not starting on Firefox #886

Closed

Add DirectConnect Support for Firefox 51+ #4005

Closed

heathkit mentioned this issue Apr 12, 2017

Protractor 5.1.1- Assertions failure is causing E/launcher - Process exited with error code 199 #4199

Closed

heathkit added status: external bug filed and removed status: fixed for next release type: bug labels May 1, 2017

heathkit closed this as completed May 1, 2017

Firefox 50.1.0 not working #3823

Firefox 50.1.0 not working #3823

Comments

stanbe commented Dec 14, 2016

Bug report

Xotabu4 commented Dec 14, 2016 • edited Loading

wh33ler commented Dec 16, 2016

BishuSinha commented Dec 18, 2016

juliemr commented Dec 19, 2016

juliemr commented Dec 19, 2016

sjelin commented Dec 22, 2016

heathkit commented Jan 10, 2017

heathkit commented Jan 18, 2017

sdseenu commented Feb 3, 2017

theandrewlane commented Feb 8, 2017

sjelin commented Feb 8, 2017 • edited Loading

esoyke commented Feb 9, 2017

JoshLipps commented Feb 15, 2017

joeydaowang commented Feb 27, 2017

JoshLipps commented Feb 27, 2017

joeydaowang commented Feb 27, 2017

rahulmr commented Mar 15, 2017

benitogf commented Mar 15, 2017 • edited Loading

RaviKlair commented Apr 10, 2017

rahulmr commented Apr 11, 2017 • edited Loading

RaviKlair commented Apr 11, 2017 • edited Loading

jlin412 commented Apr 11, 2017 via email

RaviKlair commented Apr 11, 2017

rahulmr commented Apr 11, 2017

RaviKlair commented Apr 11, 2017

jlin412 commented Apr 11, 2017 via email

rahulmr commented Apr 11, 2017

RaviKlair commented Apr 11, 2017 • edited Loading

rahulmr commented Apr 11, 2017

jlin412 commented Apr 11, 2017 via email

rahulmr commented Apr 11, 2017

RaviKlair commented Apr 11, 2017

mftaha commented Apr 13, 2017 • edited Loading

heathkit commented May 1, 2017

pramodh06 commented May 16, 2017

Xotabu4 commented Dec 14, 2016 •

edited

Loading

sjelin commented Feb 8, 2017 •

edited

Loading

benitogf commented Mar 15, 2017 •

edited

Loading

rahulmr commented Apr 11, 2017 •

edited

Loading

RaviKlair commented Apr 11, 2017 •

edited

Loading

RaviKlair commented Apr 11, 2017 •

edited

Loading

mftaha commented Apr 13, 2017 •

edited

Loading