New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"InvalidArgumentError: Could not convert 'text' to string" on selenium 3.4.0/firefox 53 #4041

Closed
dmaii opened this Issue May 19, 2017 · 8 comments

Comments

Projects
None yet
6 participants
@dmaii
Copy link

dmaii commented May 19, 2017

Meta -

OS: Ubuntu Xenial
Selenium Version: 3.4.0
Browser: Firefox

Browser Version: 53

Expected Behavior -

The google_search.js example should run without issues using the latest version of the selenium/standalone-firefox .

Actual Behavior -

I get the following error:

/usr/src/node_modules/selenium-webdriver/lib/promise.js:2634
        throw error;
        ^

InvalidArgumentError: Could not convert 'text' to string
    at WebDriverError (/usr/src/node_modules/selenium-webdriver/lib/error.js:27:5)
    at InvalidArgumentError (/usr/src/node_modules/selenium-webdriver/lib/error.js:64:5)
    at Object.throwDecodedError (/usr/src/node_modules/selenium-webdriver/lib/error.js:489:11)
    at parseHttpResponse (/usr/src/node_modules/selenium-webdriver/lib/http.js:519:13)
    at doSend.then.response (/usr/src/node_modules/selenium-webdriver/lib/http.js:441:30)
    at process._tickCallback (internal/process/next_tick.js:103:7)
From: Task: WebElement.sendKeys()
    at thenableWebDriverProxy.schedule (/usr/src/node_modules/selenium-webdriver/lib/webdriver.js:816:17)
    at WebElementPromise.schedule_ (/usr/src/node_modules/selenium-webdriver/lib/webdriver.js:2024:25)
    at WebElementPromise.sendKeys (/usr/src/node_modules/selenium-webdriver/lib/webdriver.js:2187:19)
    at driver.get.then._ (/usr/src/node_modules/selenium-webdriver/example/google_search.js:47:49)
    at ManagedPromise.invokeCallback_ (/usr/src/node_modules/selenium-webdriver/lib/promise.js:1384:14)
    at TaskQueue.execute_ (/usr/src/node_modules/selenium-webdriver/lib/promise.js:3092:14)
    at TaskQueue.executeNext_ (/usr/src/node_modules/selenium-webdriver/lib/promise.js:3075:27)
    at asyncRun (/usr/src/node_modules/selenium-webdriver/lib/promise.js:2935:27)
    at /usr/src/node_modules/selenium-webdriver/lib/promise.js:676:7
    at process._tickCallback (internal/process/next_tick.js:103:7)

Steps to reproduce -

docker build and docker run this Dockerfile, which uses the latest versions of the selenium/standalone-firefox docker image and selenium-webdriver npm module.

@dmaii dmaii changed the title `InvalidArgumentError: Could not convert 'text' to string` on selenium 3.4.0/firefox 53 "InvalidArgumentError: Could not convert 'text' to string" on selenium 3.4.0/firefox 53 May 19, 2017

@bighitbiker3

This comment has been minimized.

Copy link

bighitbiker3 commented May 23, 2017

I'm getting this as well

@lmtierney

This comment has been minimized.

Copy link
Member

lmtierney commented May 23, 2017

This is fixed in 6907a12, will be in the next release of javascript bindings

@lmtierney lmtierney closed this May 23, 2017

mbland added a commit to mbland/custom-links that referenced this issue May 24, 2017

end-to-end: Fix for PhantomJS; run in setup, CI
The issue on PhantomJS was that the Promise polyfill wasn't loaded. The
`urlp.loadApp()` function will now load the es6-promise polyfill if
`window.Promise` is undefined, enabling the end-to-end test to pass on
PhantomJS.

The end-to-end test now runs as part of `./go setup` as well as the
Travis CI build.

The `takeScreenshot()` function added in this commit facilitates
debugging. It can be called after any other selenium-webdriver call to
take a screenshot at that point in the test, saved as 'screenshot.png'
in the current working directory (usually `_GO_ROOTDIR` when run via
`./go test end-to-end`).

Note that the end-to-end test still fails on Firefox and Safari due to
the following issues that have been fixed upstream, but still need to
filter out to the next selenium-webdriver and Safari releases:

- Firefox: SeleniumHQ/selenium#4041
- Safari: SeleniumHQ/selenium#4030
@mo

This comment has been minimized.

Copy link

mo commented Jun 14, 2017

@jleyba did you decide on a date for 3.4.1 yet?

@gkushang

This comment has been minimized.

Copy link

gkushang commented Jun 28, 2017

Is this fix released yet?

@bighitbiker3

This comment has been minimized.

Copy link

bighitbiker3 commented Jun 28, 2017

@gkushang Nope, looks like we're still on 3.4.0

@thangakumard

This comment has been minimized.

Copy link

thangakumard commented Jul 2, 2017

still we have this issue in 3.4.0

@mo

This comment has been minimized.

Copy link

mo commented Jul 12, 2017

@jleyba is there someone other than you who can prepare a new release?

@gkushang

This comment has been minimized.

Copy link

gkushang commented Jul 12, 2017

+1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment