appium / appium-chromedriver Goto Github PK
View Code? Open in Web Editor NEWNode.js wrapper around Chromedriver
License: Apache License 2.0
appium-chromedriver's Issues
Chromedriver needs updating
Chrome released v76, this module needs updating
ERROR webdriver: Request failed due to unknown error: An unknown server-side error occurred while processing the command. Original error: Unable to automate Chrome version because it is too old for this version of Chromedriver.
Chrome version on the device: Chrome/76.0.3809.89
Visit 'https://github.com/appium/appium/blob/master/docs/en/writing-running-appium/web/chromedriver.md' to troubleshoot the problem.
Failed to start Chromedriver session: A new session could not be created. Details: session not created: Chrome version must be between 71 and 75
(Driver info: chromedriver=2.46.628411 (3324f4c8be9ff2f70a05a30ebc72ffb013e1a71e),platform=Mac OS X 10.14.6 x86_64)
at getErrorFromResponseBody (/node_modules/webdriver/build/utils.js:215:10)
at Request._callback (/node_modules/webdriver/build/request.js:103:64)
at Request.self.callback (/node_modules/request/request.js:185:22)
at Request.emit (events.js:198:13)
at Request.EventEmitter.emit (domain.js:448:20)
at Request.<anonymous> (/node_modules/request/request.js:1161:10)
at Request.emit (events.js:198:13)
at Request.EventEmitter.emit (domain.js:448:20)
at IncomingMessage.<anonymous> (/node_modules/request/request.js:1083:12)
at Object.onceWrapper (events.js:286:20)
Getting error when trying to install running OS X
Hi,
I get the following errors when trying to install the npm package:
> [email protected] install /Users/philip.brechler/node_modules/appium-chromedriver
> node install-npm.js
/Users/philip.brechler/node_modules/appium-chromedriver/node_modules/appium-support/node_modules/bluebird/js/main/promisify.js:268
throw new TypeError("fn must be a function\u000a\u000a See http://goo.gl/916lJJ\u000a");
^
TypeError: fn must be a function
See http://goo.gl/916lJJ
at Function.Promise.promisify (/Users/philip.brechler/node_modules/appium-chromedriver/node_modules/appium-support/node_modules/bluebird/js/main/promisify.js:268:15)
at Object.<anonymous> (lib/fs.js:41:13)
at Module._compile (module.js:456:26)
at Object.Module._extensions..js (module.js:474:10)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:312:12)
at Module.require (module.js:364:17)
at require (module.js:380:17)
at Object.<anonymous> (/Users/philip.brechler/node_modules/appium-chromedriver/node_modules/appium-support/build/lib/tempdir.js:12:11)
at Module._compile (module.js:456:26)
at Object.Module._extensions..js (module.js:474:10)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:312:12)
at Module.require (module.js:364:17)
at require (module.js:380:17)
at Object.<anonymous> (/Users/philip.brechler/node_modules/appium-chromedriver/node_modules/appium-support/build/index.js:11:19)
at Module._compile (module.js:456:26)
at Object.Module._extensions..js (module.js:474:10)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:312:12)
at Module.require (module.js:364:17)
at require (module.js:380:17)
at Object.<anonymous> (lib/install.js:6:42)
at Module._compile (module.js:456:26)
at Object.Module._extensions..js (module.js:474:10)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:312:12)
at Module.require (module.js:364:17)
at require (module.js:380:17)
at /Users/philip.brechler/node_modules/appium-chromedriver/install-npm.js:13:5
at Object.oncomplete (fs.js:107:15)
npm ERR! [email protected] install: `node install-npm.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] install script.
npm ERR! This is most likely a problem with the appium-chromedriver package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node install-npm.js
npm ERR! You can get their info via:
npm ERR! npm owner ls appium-chromedriver
npm ERR! There is likely additional logging output above.
npm ERR! System Darwin 15.0.0
npm ERR! command "node" "/usr/local/bin/npm" "install" "appium-chromedriver" "--chromedriver_version=2.16"
npm ERR! cwd /Users/philip.brechler
npm ERR! node -v v0.10.22
npm ERR! npm -v 1.3.14
npm ERR! code ELIFECYCLE
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! /Users/philip.brechler/npm-debug.log
npm ERR! not ok code 0
Appium session times out after a long time waiting to interact with the Chrome browser
The problem
While the appium session is running on a web view on an Android device, the appium server waits for a long time, say around 10 minutes and finally closes by just logging an error message
Environment
Appium version (or git revision) that exhibits the issue: 1.12.1
Last Appium version that did not exhibit the issue (if applicable): Not sure, but may be way back like 1.9.0
Desktop OS/version used to run Appium: mac 10.14.4
Node.js version (unless using Appium.app|exe): 10.12.0
Npm or Yarn package manager: npm
Mobile platform/version under test: Android
Real device or emulator/simulator: Real Device
Appium CLI or Appium.app|exe: Appium CLI
Details
The below error message appears even if the element is visible and this is quite intermittent.
TimeoutException: Message: timeout: Timed out receiving message from renderer: 10.000 (Session info: chrome=73.0.3683.90)(Driver info: chromedriver=2.46.628411 (3324f4c8be9ff2f70a05a30ebc72ffb013e1a71e),platform=Mac OS X 10.14.4 x86_64)
Original error: unknown error: unable to discover open pages
Original error: unknown error: unable to discover open pages
[WD Proxy] Got response with status 200: {"sessionId":"f34c376720dcd3102bd8b0ece094a919","status":13,"value":{"message":"unknown error: unable to discover open pages\n (Driver info: chromedriver=2.21.371459 (36d3d07f660ff2bc1bf28a75d1cdabed0983e7c4),platform=Windows NT 6.1 SP1 x86_64)"}}
[WD Proxy] Got an unexpected response: {"sessionId":"f34c376720dcd3102bd8b0ece094a919","status":13,"value":{"message":"unknown error: unable to discover open pages\n (Driver info: chromedriver=2.21.371459 (36d3d07f660ff2bc1bf28a75d1cdabed0983e7c4),platform=Windows NT 6.1 SP1 x86_64)"}}
[debug] [MJSONWP] Matched JSONWP error code 13 to UnknownError
[Chromedriver] Error: Failed to start Chromedriver session: An unknown server-side error occurred while processing the
command. Original error: unknown error: unable to discover open pages
[Chromedriver] (Driver info: chromedriver=2.21.371459 (36d3d07f660ff2bc1bf28a75d1cdabed0983e7c4),platform=Windows NT
6.1 SP1 x86_64)
[Chromedriver] at Object.wrappedLogger.errorAndThrow (D:\autotest\nbpadAutoTest\node_modules\[email protected]@appium-support\lib\logging.js:78:13
-chromedriver-version:2.21.371459
-android system webview:46.0.2490.76
help!Thanks!
Issue in installing appium on mac through terminal window nom install appium command
sathiyans-MacBook-Pro:~ sathiyan$ npm install appium
[email protected] install /Users/sathiyan/node_modules/appium/node_modules/appium-android-driver/node_modules/appium-chromedriver
node install-npm.js
info Chromedriver Install Installing Chromedriver version '2.21' for platform 'mac' and architecture '32'
info Chromedriver Install Opening temp file to write chromedriver_mac32 to...
info Chromedriver Install Downloading http://chromedriver.storage.googleapis.com/2.21/chromedriver_mac32.zip...
RequestError: Error: connect ECONNREFUSED 74.125.68.128:80
at new RequestError (/Users/sathiyan/node_modules/appium/node_modules/request-promise/lib/errors.js:11:15)
at Request.RP$callback as _callback
at self.callback (/Users/sathiyan/node_modules/appium/node_modules/request-promise/node_modules/request/request.js:200:22)
at emitOne (events.js:96:13)
at Request.emit (events.js:188:7)
at Request.onRequestError (/Users/sathiyan/node_modules/appium/node_modules/request-promise/node_modules/request/request.js:831:8)
at emitOne (events.js:96:13)
at ClientRequest.emit (events.js:188:7)
at Socket.socketErrorListener (_http_client.js:308:9)
at emitOne (events.js:96:13)
at Socket.emit (events.js:188:7)
at emitErrorNT (net.js:1272:8)
at _combinedTickCallback (internal/process/next_tick.js:74:11)
at process._tickCallback (internal/process/next_tick.js:98:9)
[email protected] /Users/sathiyan
└── (empty)
npm ERR! Darwin 14.5.0
npm ERR! argv "/usr/local/Cellar/node/6.2.2/bin/node" "/usr/local/bin/npm" "install" "appium"
npm ERR! node v6.2.2
npm ERR! npm v3.9.5
npm ERR! code ELIFECYCLE
npm ERR! [email protected] install: node install-npm.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] install script 'node install-npm.js'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the appium-chromedriver package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node install-npm.js
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs appium-chromedriver
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls appium-chromedriver
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR! /Users/sathiyan/npm-debug.log
npm ERR! code 1
Error with chromedriver when installing appium
I am getting following error with chromedriver only when tried install of appium 1.6.0 from command line
info Chromedriver Install Downloading http://chromedriver.storage.googleapis.com
/2.21/chromedriver_win32.zip...
RequestError: Error: socket hang up
at new RequestError (C:\Users\nikhil.udgirkar\node_modules\appium\node_modul
es\request-promise\lib\errors.js:11:15)
at Request.RP$callback [as _callback](C:Usersnikhil.udgirkarnode_modules
appiumnode_modulesrequest-promiselibrp.js:60:32)
at self.callback (C:\Users\nikhil.udgirkar\node_modules\appium\node_modules
request\request.js:187:22)
at emitOne (events.js:96:13)
at Request.emit (events.js:188:7)
at Request.onRequestError (C:\Users\nikhil.udgirkar\node_modules\appium\node
_modules\request\request.js:813:8)
at emitOne (events.js:96:13)
at ClientRequest.emit (events.js:188:7)
at Socket.socketOnEnd (_http_client.js:342:9)
at emitNone (events.js:91:20)
at Socket.emit (events.js:185:7)
at endReadableNT (_stream_readable.js:926:12)
at _combinedTickCallback (internal/process/next_tick.js:74:11)
at process._tickCallback (internal/process/next_tick.js:98:9)
C:\Users\nikhil.udgirkar
`-- (empty)
npm WARN optional Skipping failed optional dependency /appium/fsevents:
npm WARN notsup Not compatible with your operating system or architecture: fseve
[email protected]
npm WARN enoent ENOENT: no such file or directory, open 'C:\Users\nikhil.udgirka
r\package.json'
npm WARN nikhil.udgirkar No description
npm WARN nikhil.udgirkar No repository field.
npm WARN nikhil.udgirkar No README data
npm WARN nikhil.udgirkar No license field.
npm ERR! Windows_NT 6.2.9200
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs
node_modules\npm\bin\npm-cli.js" "install" "appium-1.6.0.tgz"
npm ERR! node v6.0.0
npm ERR! npm v3.8.6
npm ERR! code ELIFECYCLE
npm ERR! [email protected] install: node install-npm.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] install script 'node install-np
m.js'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the appium-chromedriver p
ackage,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node install-npm.js
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs appium-chromedriver
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls appium-chromedriver
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR! C:\Users\nikhil.udgirkar\npm-debug.log
npm ERR! code 1
Please provide solution for this
thanks
Add Support for Installing Chromedriver 2.23+ on OS X
I tried to specify installing version 2.24 and noticed the install script is assuming 'chromedriver_mac32.zip' is the file it's looking for.
v2.23 and 2.24 use 'chromedriver_mac64.zip'
http://chromedriver.storage.googleapis.com/index.html?path=2.24/
info Chromedriver Install Downloading http://chromedriver.storage.googleapis.com/2.24/chromedriver_mac32.zip...
Cannot install - Socket Hang Up [OSX 10.11.4]
Once I had upgraded from OSX 10.11.3 to 10.11.4, I was first unable to install appium via npm, which pointed to this library, which I cannot install locally.
➜ tasker git:(112400479-add-categories) ✗ npm install appium-chromedriver
> [email protected] install /Users/jeremyeaton/projects/taskrabbit/tasker/node_modules/appium-chromedriver
> node install-npm.js
info Chromedriver Install Installing Chromedriver version '2.21' for platform 'mac' and architecture '32'
info Chromedriver Install Opening temp file to write chromedriver_mac32 to...
info Chromedriver Install Downloading http://chromedriver.storage.googleapis.com/2.21/chromedriver_mac32.zip...
RequestError: Error: socket hang up
at new RequestError (/Users/jeremyeaton/projects/taskrabbit/tasker/node_modules/request-promise/lib/errors.js:11:15)
at Request.RP$callback [as _callback] (/Users/jeremyeaton/projects/taskrabbit/tasker/node_modules/request-promise/lib/rp.js:60:32)
at self.callback (/Users/jeremyeaton/projects/taskrabbit/tasker/node_modules/request/request.js:199:22)
at emitOne (events.js:77:13)
at Request.emit (events.js:169:7)
at Request.onRequestError (/Users/jeremyeaton/projects/taskrabbit/tasker/node_modules/request/request.js:821:8)
at emitOne (events.js:77:13)
at ClientRequest.emit (events.js:169:7)
at Socket.socketOnEnd (_http_client.js:288:9)
at emitNone (events.js:72:20)
at Socket.emit (events.js:166:7)
at endReadableNT (_stream_readable.js:893:12)
at doNTCallback2 (node.js:429:9)
at process._tickCallback (node.js:343:17)
[email protected] /Users/jeremyeaton/projects/taskrabbit/tasker
└── [email protected] extraneous
npm ERR! Darwin 15.4.0
npm ERR! argv "/Users/jeremyeaton/.nvm/versions/node/v4.0.0/bin/node" "/Users/jeremyeaton/.nvm/versions/node/v4.0.0/bin/npm" "install" "appium-chromedriver"
npm ERR! node v4.0.0
npm ERR! npm v3.8.5
npm ERR! code ELIFECYCLE
npm ERR! [email protected] install: `node install-npm.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] install script 'node install-npm.js'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the appium-chromedriver package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node install-npm.js
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs appium-chromedriver
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls appium-chromedriver
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR! /Users/jeremyeaton/projects/taskrabbit/tasker/npm-debug.log
Unable to use chromedriver_autodownload
Starting appium with --allow-insecure=chromedriver_autodownload flag
Creating new session with chromedriverChromeMappingFile and chromedriverExecutableDir capabilitites
Expected result:
Proper chromedriver should be downloaded into the chromedriverExecutableDir and chromedriverChromeMappingFile should be updated
Actual result:
Encountered internal error running command: Error: No Chromedriver found that can automate Chrome '73.0.3683'. See https://github.com/appium/appium/blob/master/docs/en/writing-running-appium/web/chromedriver.md for more details. You could also try to enable automated chromedrivers download server feature
Environment
Appium 1.16.0
Ubuntu 18.04
Appium logs:
appium.log
Trying to use a chromedriver binary at the path /Users/automation/.appium/node_modules/appium-device-farm/chromedriver/chromedriver_mac64_v124.0.6367.207, but it doesn't exist!
We get an error when running our automation on android because the chromedriver binary filename it is searching for exists with dashes in the name and not with underscores. Maybe replace occurrences of dashes with underscores here?
The downloaded files have the name chromedriver-mac-arm64_vX.X.X.X instead of chromedriver_mac64_vX.X.X.X
Support for new chromedriver2.21
Node install failure on version 2.9.2
Hello!
My notice is that installing the appium-chromedriver 2.9.2 installing fails at node install-npm.js.
My OS is Windows_NT 6.1.7601, Node.js is 6.5.0 and npm is 3.10.7
Thanks for resolving issue!
The log is below:
npm-debug.zip
It's a connection error to the http://216.58.201.208.80/ address, that I also face from any browser.
Need update on npm
When i download appium-chromedriver using 'npm i appium-chromedriver' i get a version that goes up to chrome 93 (according to the mapping file).
I'm working on windows 10 and i'm terribly sorry if this issue is due to some sort problem with my npm or powershell version.
Action required: Greenkeeper could not be activated 🚨
🚨 You need to enable Continuous Integration on all branches of this repository. 🚨
To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.
Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.
If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.
Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper App’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.
Cannot `npm install` on linux because `node` command is used in install scripts
The install script in package.json uses node but by default there is only the nodejs command.
@sebv didn't you have a good method for getting around this? I can't remember
Action required: Greenkeeper could not be activated 🚨
🚨 You need to enable Continuous Integration on Greenkeeper branches of this repository. 🚨
To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.
Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.
If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.
Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please click the 'fix repo' button on account.greenkeeper.io.
Expose all the arguments of chromedriver.
Usage: chromedriver.exe [OPTIONS]
Options
--port=PORT port to listen on
--adb-port=PORT adb server port
--log-path=FILE write server log to file instead of stderr, increases log level to INFO
--verbose log verbosely
--version print the version number and exit
--silent log nothing
--url-base base URL path prefix for commands, e.g. wd/url
--port-server address of server to contact for reserving a port
--whitelisted-ips comma-separated whitelist of remote IPv4 addresses which are allowed to connect to ChromeDriver
Currently only port and url-base are used. Expose --verbose and --log-path for chromedriver executable from appium server args would be nice.
lib/chromedriver.js
lines >50
REGRESSION Adb port doesn't get properly handoverd to chromedriver
check appium/appium@b688a6e
here @lbielski fixed that the chromedriver uses the adb port configured for appium. Without beeing able to configure a custome adb port its nearly impossible to use it in a large real device setup (tons of devices connected to the same host)
@Jonahss @jlipps Does anyone know why this has been removed?
Test Script not able to locate element on Real Device post switching to webview of a hybrid app.
The problem
Unable to locate element on Real Device post switching to webview of a hybrid app.
Environment
Appium version : 1.22.2
Desktop OS/version used to run Appium: Windows 10 Android Version 10
Node.js version : v16.13.1
Npm or Yarn package manager: 8.1.2
Mobile platform/version under test: Android 10
Real device : Galaxy M20
Appium CLI or Appium.app|exe: Appium CLI
Chromedriver on Real Device used: 98.0.4758.48
Chromedriver on Emulator used: 83.0.4103.106
Links to chromedriver Logs
Chromedriver getpagesource() response logs on emulator. https://gist.github.com/Rahul1970/97f8e8fd0a5f1145873a237855ba33c1.js
Chromedriver getpagesource() response logs on real device.
https://gist.github.com/Rahul1970/bf078ac294e534b7749f5e33493bd110.js
Link to Appium logs
1..Appium logs for working code on emulator on successful switch context to webview and able to locate element.
https://gist.github.com/Rahul1970/c503aa9943cf60649a7fed269f5b5797.js
2. Appium logs on real device on successful switch context to webview but not able to locate element.
https://gist.github.com/Rahul1970/585e3c08718ec291bf2b0c4452af89b3.js
Details
In my hybrid mobile application on real device i am able to pass through the native views but when landing on webview and able to switch to webview i am not able to locate element. I am able to locate elements on webview in emulator but not able to do so on real device.
Code To Reproduce Issue [ Good To Have ]
DesiredCapabilities dc = new DesiredCapabilities();
dc.setCapability(MobileCapabilityType.DEVICE_NAME, deviceName);//deviceName
dc.setCapability(MobileCapabilityType.UDID, deviceName );
//dc.setCapability(MobileCapabilityType.PLATFORM_VERSION,platformVersion);
dc.setCapability(MobileCapabilityType.PLATFORM_NAME, "Android");
dc.setCapability(MobileCapabilityType.APP, System.getProperty("user.dir")+"/src/test/resources/apps/"+AppName);
dc.setCapability("automationName","UiAutomator2");
dc.setCapability("unicodeKeyboard", true);
dc.setCapability("resetKeyboard", true);
dc.setCapability("autoWebview", false);
//dc.setCapability(MobileCapabilityType.BROWSER_NAME, "Chrome");
//dc.setCapability("appWaitForLaunch", false);
dc.setCapability("appPackage", "com.crmnextmobile.crmnextofflineplay");
dc.setCapability("appActivity", "com.crmnextmobile.crmnextofflineplay.qr.QrScannerActivity");
driver = new AndroidDriver(service.getUrl(),dc);
driver.manage().timeouts().implicitlyWait(Duration.ofSeconds(10));
ReUsableMethods.mobileStartRecording();
login();
ReUsableMethods.clickElement(sp.itemMenu," Menu Summary Page ");
ReUsableMethods.clickElement(lp.leadMenu,"Lead Menu Page");
ReUsableMethods.clickElement(lp.addLead,"Lead Add icon");
ReUsableMethods.clickElement(lp.addNewLead,"Add new lead");
Set contextNames = ((SupportsContextSwitching)driver).getContextHandles();
for (String contextName : contextNames)
{
System.out.println("Available Context"+contextName);
}
System.out.println("Before Context Switch"); ////Switching context to webview
((SupportsContextSwitching) driver).context("WEBVIEW_com.crmnextmobile.crmnextofflineplay");
System.out.println("After Context Switch");
Thread.sleep(10000);
ReUsableMethods.mobileStartRecording();
ReUsableMethods.enterText(lp.shortName,Leads[0], "shortname is entered.");
System.out.println(" Context Switched");
Thread.sleep(4000);
Hi Team Any help in this direction would be very helpful.
npm install with custom chromedriver version does not work
This does not work:
npm install appium-chromedriver --chromedriver_version="2.10"
Instead of the v2.10 the latest version (i.e. v2.19) is installed.
Running Windows 7
[29.09.2015 15:14:23 C:\testautom\appium\1.4.0.0\node_modules\appium\] > npm uninstall appium-chromedriver unbuild [email protected] [29.09.2015 15:14:49 C:\testautom\appium\1.4.0.0\node_modules\appium\] > npm install appium-chromedriver --chromedriver_version="2.10" npm WARN package.json [email protected] No repository field. npm WARN package.json [email protected] No repository field. npm WARN package.json [email protected] path is also the name of a node core module. npm WARN package.json [email protected] No repository field. npm WARN package.json [email protected] No repository field. npm http GET https://registry.npmjs.org/appium-chromedriver npm http 304 https://registry.npmjs.org/appium-chromedriver npm http GET https://registry.npmjs.org/appium-logger npm http GET https://registry.npmjs.org/asyncbox npm http GET https://registry.npmjs.org/chromedriver npm http GET https://registry.npmjs.org/is-os npm http GET https://registry.npmjs.org/lodash npm http GET https://registry.npmjs.org/ps-node/0.0.3 npm http GET https://registry.npmjs.org/q npm http GET https://registry.npmjs.org/appium-jsonwp-proxy npm http GET https://registry.npmjs.org/babel-runtime npm http GET https://registry.npmjs.org/request npm http GET https://registry.npmjs.org/source-map-support npm http 304 https://registry.npmjs.org/lodash npm http 304 https://registry.npmjs.org/q npm http 304 https://registry.npmjs.org/request npm http 304 https://registry.npmjs.org/source-map-support npm http 304 https://registry.npmjs.org/babel-runtime npm http 304 https://registry.npmjs.org/appium-logger npm http 304 https://registry.npmjs.org/is-os npm http 304 https://registry.npmjs.org/asyncbox npm http 304 https://registry.npmjs.org/chromedriver npm http 304 https://registry.npmjs.org/ps-node/0.0.3 npm http 304 https://registry.npmjs.org/appium-jsonwp-proxy npm http GET https://registry.npmjs.org/table-parser npm http GET https://registry.npmjs.org/kew npm http GET https://registry.npmjs.org/npmconf npm http 304 https://registry.npmjs.org/npmconf npm http 304 https://registry.npmjs.org/kew npm http GET https://registry.npmjs.org/babel-runtime/5.5.5 npm http GET https://registry.npmjs.org/npmlog npm http 304 https://registry.npmjs.org/npmlog npm http GET https://registry.npmjs.org/jsonwp-status/0.0.1 npm http GET https://registry.npmjs.org/babel-runtime/5.5.5 npm http GET https://registry.npmjs.org/bluebird npm http GET https://registry.npmjs.org/chai npm http GET https://registry.npmjs.org/chai-as-promised npm http GET https://registry.npmjs.org/es6-mapify npm http GET https://registry.npmjs.org/source-map/0.1.32 npm http 304 https://registry.npmjs.org/babel-runtime/5.5.5 npm http 304 https://registry.npmjs.org/bluebird npm http 304 https://registry.npmjs.org/chai-as-promised npm http 304 https://registry.npmjs.org/babel-runtime/5.5.5 npm http GET https://registry.npmjs.org/bl npm http GET https://registry.npmjs.org/caseless npm http GET https://registry.npmjs.org/extend npm http GET https://registry.npmjs.org/forever-agent npm http GET https://registry.npmjs.org/form-data npm http GET https://registry.npmjs.org/json-stringify-safe npm http GET https://registry.npmjs.org/mime-types npm http GET https://registry.npmjs.org/qs npm http GET https://registry.npmjs.org/tunnel-agent npm http GET https://registry.npmjs.org/tough-cookie npm http GET https://registry.npmjs.org/http-signature npm http GET https://registry.npmjs.org/oauth-sign npm http GET https://registry.npmjs.org/hawk npm http GET https://registry.npmjs.org/aws-sign2 npm http GET https://registry.npmjs.org/stringstream npm http GET https://registry.npmjs.org/isstream npm http GET https://registry.npmjs.org/combined-stream npm http 304 https://registry.npmjs.org/table-parser npm http 304 https://registry.npmjs.org/jsonwp-status/0.0.1 npm http GET https://registry.npmjs.org/har-validator npm http 304 https://registry.npmjs.org/chai npm http 304 https://registry.npmjs.org/bl npm http 304 https://registry.npmjs.org/caseless npm http 304 https://registry.npmjs.org/forever-agent npm http 304 https://registry.npmjs.org/extend npm http 304 https://registry.npmjs.org/form-data npm http 304 https://registry.npmjs.org/json-stringify-safe npm http 304 https://registry.npmjs.org/mime-types npm http 304 https://registry.npmjs.org/tunnel-agent npm http 304 https://registry.npmjs.org/tough-cookie npm http 304 https://registry.npmjs.org/qs npm http 304 https://registry.npmjs.org/aws-sign2 npm http 304 https://registry.npmjs.org/stringstream npm http 304 https://registry.npmjs.org/oauth-sign npm http 304 https://registry.npmjs.org/hawk npm http 304 https://registry.npmjs.org/isstream npm http 304 https://registry.npmjs.org/http-signature npm http 304 https://registry.npmjs.org/combined-stream npm http 304 https://registry.npmjs.org/source-map/0.1.32 npm http 304 https://registry.npmjs.org/har-validator npm WARN engine [email protected]: wanted: {"node":">=0.10.32"} (current: {"node":"v0.10.26","npm":"1.4.6"}) npm http 304 https://registry.npmjs.org/es6-mapify npm http GET https://registry.npmjs.org/config-chain npm http GET https://registry.npmjs.org/inherits npm http GET https://registry.npmjs.org/ini npm http GET https://registry.npmjs.org/nopt npm http GET https://registry.npmjs.org/once npm http GET https://registry.npmjs.org/semver npm http GET https://registry.npmjs.org/osenv npm http GET https://registry.npmjs.org/uid-number/0.0.5 npm http 304 https://registry.npmjs.org/config-chain npm http 304 https://registry.npmjs.org/ini npm http 304 https://registry.npmjs.org/nopt npm http 304 https://registry.npmjs.org/semver npm http 304 https://registry.npmjs.org/inherits npm http 304 https://registry.npmjs.org/osenv npm http 304 https://registry.npmjs.org/once npm http 304 https://registry.npmjs.org/uid-number/0.0.5 npm http GET https://registry.npmjs.org/delayed-stream npm http 304 https://registry.npmjs.org/delayed-stream npm http GET https://registry.npmjs.org/mime-db npm http GET https://registry.npmjs.org/async npm http 304 https://registry.npmjs.org/mime-db npm http GET https://registry.npmjs.org/ansi npm http GET https://registry.npmjs.org/are-we-there-yet npm http GET https://registry.npmjs.org/gauge npm http 304 https://registry.npmjs.org/async npm http 304 https://registry.npmjs.org/ansi npm http 304 https://registry.npmjs.org/gauge npm http 304 https://registry.npmjs.org/are-we-there-yet npm http GET https://registry.npmjs.org/readable-stream npm http GET https://registry.npmjs.org/wrappy npm http 304 https://registry.npmjs.org/readable-stream npm http 304 https://registry.npmjs.org/wrappy npm http GET https://registry.npmjs.org/assert-plus npm http GET https://registry.npmjs.org/asn1/0.1.11 npm http GET https://registry.npmjs.org/ctype/0.5.3 npm http 304 https://registry.npmjs.org/assert-plus npm http 304 https://registry.npmjs.org/ctype/0.5.3 npm http 304 https://registry.npmjs.org/asn1/0.1.11 npm http GET https://registry.npmjs.org/os-homedir npm http GET https://registry.npmjs.org/os-tmpdir npm http 304 https://registry.npmjs.org/os-tmpdir npm http 304 https://registry.npmjs.org/os-homedir npm http GET https://registry.npmjs.org/commander npm http GET https://registry.npmjs.org/is-my-json-valid npm http GET https://registry.npmjs.org/chalk npm http 304 https://registry.npmjs.org/is-my-json-valid npm http 304 https://registry.npmjs.org/commander npm http 304 https://registry.npmjs.org/chalk npm http GET https://registry.npmjs.org/abbrev npm http GET https://registry.npmjs.org/proto-list npm http 304 https://registry.npmjs.org/abbrev npm http GET https://registry.npmjs.org/delegates npm http 304 https://registry.npmjs.org/delegates npm http GET https://registry.npmjs.org/has-unicode npm http GET https://registry.npmjs.org/lodash.pad npm http GET https://registry.npmjs.org/lodash.padleft npm http GET https://registry.npmjs.org/lodash.padright npm http GET https://registry.npmjs.org/ansi-styles npm http GET https://registry.npmjs.org/strip-ansi npm http GET https://registry.npmjs.org/supports-color npm http GET https://registry.npmjs.org/escape-string-regexp npm http GET https://registry.npmjs.org/has-ansi npm http 304 https://registry.npmjs.org/has-unicode npm http 304 https://registry.npmjs.org/lodash.pad npm http 304 https://registry.npmjs.org/lodash.padleft npm http 304 https://registry.npmjs.org/lodash.padright npm http 304 https://registry.npmjs.org/strip-ansi npm http 304 https://registry.npmjs.org/ansi-styles npm http 304 https://registry.npmjs.org/supports-color npm http 304 https://registry.npmjs.org/escape-string-regexp npm http 304 https://registry.npmjs.org/has-ansi npm http GET https://registry.npmjs.org/graceful-readlink npm http 304 https://registry.npmjs.org/graceful-readlink npm http GET https://registry.npmjs.org/lodash._basetostring npm http GET https://registry.npmjs.org/lodash._createpadding npm http GET https://registry.npmjs.org/ansi-regex npm http 304 https://registry.npmjs.org/lodash._basetostring npm http 304 https://registry.npmjs.org/lodash._createpadding npm http 304 https://registry.npmjs.org/ansi-regex npm http 304 https://registry.npmjs.org/proto-list npm http GET https://registry.npmjs.org/traceur npm http 304 https://registry.npmjs.org/traceur npm http GET https://registry.npmjs.org/amdefine npm http GET https://registry.npmjs.org/core-util-is npm http GET https://registry.npmjs.org/isarray/0.0.1 npm http GET https://registry.npmjs.org/process-nextick-args npm http GET https://registry.npmjs.org/string_decoder npm http GET https://registry.npmjs.org/lodash.repeat npm http GET https://registry.npmjs.org/util-deprecate npm http 304 https://registry.npmjs.org/core-util-is npm http 304 https://registry.npmjs.org/isarray/0.0.1 npm http 304 https://registry.npmjs.org/amdefine npm http 304 https://registry.npmjs.org/lodash.repeat npm http 304 https://registry.npmjs.org/util-deprecate npm http 304 https://registry.npmjs.org/string_decoder npm http 304 https://registry.npmjs.org/process-nextick-args > [email protected] install C:\testautom\appium\1.4.0.0\node_modules\appium\node_modules\appium-chromedriver\node_modules\chromedriver > node install.js Downloading http://chromedriver.storage.googleapis.com/2.19/chromedriver_win32.zip Saving to C:\Users\occ\AppData\Local\Temp\chromedriver\chromedriver_win32.zip Receiving... Received 784K... Received 1567K... Received 2351K... Received 2410K total. Extracting zip contents Copying to target path C:\testautom\appium\1.4.0.0\node_modules\appium\node_modules\appium-chromedriver\node_modules\chromedriver\lib\chromedriver Done. ChromeDriver binary available at C:\testautom\appium\1.4.0.0\node_modules\appium\node_modules\appium-chromedriver\node_modules\chromedriver\lib\chromedriver\chromedriver.exe npm http GET https://registry.npmjs.org/hoek npm http GET https://registry.npmjs.org/cryptiles npm http GET https://registry.npmjs.org/boom npm http GET https://registry.npmjs.org/sntp npm http 304 https://registry.npmjs.org/cryptiles npm http 304 https://registry.npmjs.org/hoek npm http 304 https://registry.npmjs.org/sntp npm http 304 https://registry.npmjs.org/boom npm WARN engine [email protected]: wanted: {"node":">=0.10.40"} (current: {"node":"v0.10.26","npm":"1.4.6"}) npm WARN engine [email protected]: wanted: {"node":">=0.10.40"} (current: {"node":"v0.10.26","npm":"1.4.6"}) npm WARN engine [email protected]: wanted: {"node":">=0.10.40"} (current: {"node":"v0.10.26","npm":"1.4.6"}) npm http GET https://registry.npmjs.org/jsonpointer/2.0.0 npm http GET https://registry.npmjs.org/xtend npm http GET https://registry.npmjs.org/generate-function npm http GET https://registry.npmjs.org/generate-object-property npm http 304 https://registry.npmjs.org/jsonpointer/2.0.0 npm http 304 https://registry.npmjs.org/xtend npm http 304 https://registry.npmjs.org/generate-function npm http 304 https://registry.npmjs.org/generate-object-property npm http GET https://registry.npmjs.org/is-property npm http GET https://registry.npmjs.org/assertion-error npm http GET https://registry.npmjs.org/deep-eql npm http GET https://registry.npmjs.org/type-detect npm http 304 https://registry.npmjs.org/is-property npm http 304 https://registry.npmjs.org/assertion-error npm http 304 https://registry.npmjs.org/deep-eql npm http 304 https://registry.npmjs.org/type-detect npm http GET https://registry.npmjs.org/core-js npm http 304 https://registry.npmjs.org/core-js npm http GET https://registry.npmjs.org/type-detect/0.1.1 npm http 304 https://registry.npmjs.org/type-detect/0.1.1 npm http GET https://registry.npmjs.org/glob npm http GET https://registry.npmjs.org/rsvp npm http 304 https://registry.npmjs.org/rsvp npm http 304 https://registry.npmjs.org/glob npm http GET https://registry.npmjs.org/inflight npm http GET https://registry.npmjs.org/minimatch npm http 304 https://registry.npmjs.org/inflight npm http 304 https://registry.npmjs.org/minimatch npm http GET https://registry.npmjs.org/brace-expansion npm http 304 https://registry.npmjs.org/brace-expansion npm http GET https://registry.npmjs.org/balanced-match npm http GET https://registry.npmjs.org/concat-map/0.0.1 npm http 304 https://registry.npmjs.org/concat-map/0.0.1 npm http 304 https://registry.npmjs.org/balanced-match [email protected] node_modules\appium-chromedriver ├── [email protected] ├── [email protected] ├── [email protected] ([email protected]) ├── [email protected] ([email protected]) ├── [email protected] ([email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], comb ├── [email protected] ├── [email protected] ([email protected], [email protected], [email protected]) ├── [email protected] ([email protected]) ├── [email protected] ([email protected], [email protected]) ├── [email protected] ([email protected], [email protected], [email protected], [email protected], [email protected], [email protected]) └── [email protected] ([email protected], [email protected]) [29.09.2015 15:15:22 C:\testautom\appium\1.4.0.0\node_modules\appium\] > [29.09.2015 15:15:31 C:\testautom\appium\1.4.0.0\node_modules\appium\] > npm info appium-chromedriver npm http GET https://registry.npmjs.org/appium-chromedriver npm http 304 https://registry.npmjs.org/appium-chromedriver { name: 'appium-chromedriver', description: 'Node.js wrapper around chromedriver.', 'dist-tags': { latest: '2.3.5' }, versions: [ '0.0.2', '0.1.0', '0.2.0', '0.2.1', '0.2.2', '1.0.0', '1.0.1', '1.1.0', '2.0.0', '2.0.1', '2.0.2', '2.0.3', '2.0.4', '2.0.5', '2.0.6', '2.0.7', '2.0.8', '2.0.9', '2.0.10', '2.1.0', '2.1.1', '2.1.2', '2.1.3', '2.2.0', '2.2.1', '2.3.0', '2.3.2', '2.3.3', '2.3.4', '2.3.5' ], maintainers: [ 'bootstraponline ', 'imurchie ', 'jlipps ', 'jonahss ', 'moizjv ', 'scottdixon ', 'sebv ' ], time: { modified: '2015-09-28T20:26:36.580Z', created: '2015-01-13T18:32:54.183Z', '0.0.2': '2015-01-13T18:32:54.183Z', '0.1.0': '2015-04-07T00:30:35.307Z', '0.2.0': '2015-04-07T16:04:23.136Z', '0.2.1': '2015-04-08T19:25:32.457Z', '0.2.2': '2015-04-08T21:19:11.244Z', '1.0.0': '2015-04-10T03:11:33.949Z', '1.0.1': '2015-04-14T22:02:05.820Z', '1.1.0': '2015-04-29T02:55:16.835Z', '2.0.0': '2015-05-11T21:19:13.450Z', '2.0.1': '2015-05-14T19:03:04.779Z', '2.0.2': '2015-05-14T20:18:54.313Z', '2.0.3': '2015-05-14T20:44:08.874Z', '2.0.4': '2015-05-22T01:58:00.273Z', '2.0.5': '2015-05-22T15:09:19.913Z', '2.0.6': '2015-05-22T16:20:45.270Z', '2.0.7': '2015-05-22T16:58:43.557Z', '2.0.8': '2015-05-22T17:26:04.921Z', '2.0.9': '2015-06-08T18:37:05.654Z', '2.0.10': '2015-06-09T00:43:03.134Z', '2.1.0': '2015-06-09T19:25:53.072Z', '2.1.1': '2015-06-12T00:39:32.714Z', '2.1.2': '2015-06-15T21:38:16.391Z', '2.1.3': '2015-06-17T16:45:12.829Z', '2.2.0': '2015-08-26T02:30:53.992Z', '2.2.1': '2015-08-27T20:40:41.989Z', '2.3.0': '2015-08-27T21:07:52.929Z', '2.3.2': '2015-08-28T20:24:41.681Z', '2.3.3': '2015-09-18T17:52:37.189Z', '2.3.4': '2015-09-25T15:43:47.593Z', '2.3.5': '2015-09-28T20:26:36.580Z' }, homepage: 'https://github.com/appium/appium-chromedriver#readme', keywords: [ 'appium', 'chrome', 'android' ], repository: { type: 'git', url: 'git+https://github.com/appium/appium-chromedriver.git' }, author: 'appium', bugs: { url: 'https://github.com/appium/appium-chromedriver/issues' }, license: 'Apache-2.0', readmeFilename: 'README.md', version: '2.3.5', engines: 'node', main: './build/index.js', bin: {}, directories: { lib: 'lib' }, dependencies: { 'adm-zip': '^0.4.7', 'appium-jsonwp-proxy': '^1.2.4', 'appium-logger': '^2.0.0', 'appium-support': '^2.0.0', asyncbox: '^2.0.2', 'babel-runtime': '=5.8.24', 'is-os': '^1.0.0', lodash: '^3.10.1', 'ps-node': '^0.0.5', q: '^1.2.0', request: '^2.57.0', 'request-promise': '^0.4.2', 'source-map-support': '^0.3.2', teen_process: '^1.3.1', through: '^2.3.7' }, scripts: { prepublish: 'gulp prepublish', test: 'gulp once', watch: 'gulp', install: 'node install-npm.js', chromedriver: 'node install-npm.js', chromedriver_all: 'node install-npm.js --all' }, devDependencies: { 'appium-gulp-plugins': '^1.3.11', chai: '^3.3.0', 'chai-as-promised': '^5.1.0', gulp: '^3.9.0', mocha: '^2.3.3' }, gitHead: 'd32365782a6aa2eba87be63d03e1c1f6088ba83f', dist: { shasum: '02ca34a825d67377d4f0c7b9b27769ce8d1f89ed', tarball: 'http://registry.npmjs.org/appium-chromedriver/-/appium-chromedriver-2.3.5.tgz' } } [29.09.2015 15:15:41 C:\testautom\appium\1.4.0.0\node_modules\appium\] >
Unit tests are failing on gulp.once
This is a tracking bug for unit test failures.
MacBook-Pro-2:appium-chromedriver rkavalap$ gulp once
[16:30:04] Using gulpfile ~/work/appium-chromedriver/gulpfile.js
[16:30:04] Starting 'once'...
[16:30:04] Starting 'clean'...
[16:30:04] Finished 'clean' after 23 ms
[16:30:04] Starting 'jshint'...
[16:30:05] Finished 'jshint' after 200 ms
[16:30:05] Starting 'lint'...
[16:30:05] Finished 'lint' after 3.75 μs
[16:30:05] Starting 'transpile'...
[16:30:05] Finished 'transpile' after 918 ms
[16:30:05] Starting 'unit-test'...
13 -_-_-_-_-_-_-_-_-__,------,
3 -_-_-_-_-_-_-_-_-__| /\_/\
1 -_-_-_-_-_-_-_-_-_~|_( x .x)
-_-_-_-_-_-_-_-_-_ "" ""
13 passing (2m)
1 pending
3 failing
1) chromedriver with EventEmitter should stop a session:
Error: timeout of 120000ms exceeded. Ensure the done() callback is being called in this test.
2) chromedriver with async/await should stop a session:
AssertionError: expected 'stopping' to deeply equal 'stopped'
+ expected - actual
-stopping
+stopped
at Suite.callee$1$0$ (test/chromedriver-specs.js:181:21)
at tryCatch (node_modules/babel-runtime/regenerator/runtime.js:67:40)
at GeneratorFunctionPrototype.invoke [as _invoke] (node_modules/babel-runtime/regenerator/runtime.js:315:22)
at GeneratorFunctionPrototype.prototype.(anonymous function) [as next] (node_modules/babel-runtime/regenerator/runtime.js:100:21)
at GeneratorFunctionPrototype.invoke (node_modules/babel-runtime/regenerator/runtime.js:136:37)
at bound (domain.js:280:14)
at GeneratorFunctionPrototype.runBound (domain.js:293:12)
3) chromedriver with async/await should throw an error during start if session does not work:
AssertionError: expected promise to be rejected with an error including 'cannot parse capability' but it was fulfilled with undefined
[16:32:35] Error in plugin 'gulp-mocha'
Message:
3 tests failed.
[16:32:35] 'unit-test' errored after 2.48 min
[16:32:35] Error in plugin 'gulp-mocha'
Message:
3 tests failed.
[16:32:35] 'once' errored after 2.5 min
[16:32:35] Error in plugin 'run-sequence(unit-test)'
Message:
3 tests failed.
> Stack:
> at finish (/Users/rkavalap/work/appium-chromedriver/node_modules/run-sequence/index.js:56:13)
> at Gulp.onError (/Users/rkavalap/work/appium-chromedriver/node_modules/run-sequence/index.js:67:4)
> at emitOne (events.js:101:20)
> at Gulp.emit (events.js:188:7)
> at Gulp.Orchestrator._emitTaskDone (/Users/rkavalap/work/appium-chromedriver/node_modules/orchestrator/index.js:264:8)
> at /Users/rkavalap/work/appium-chromedriver/node_modules/orchestrator/index.js:275:23
> at finish (/Users/rkavalap/work/appium-chromedriver/node_modules/orchestrator/lib/runTask.js:21:8)
> at Stream.<anonymous> (/Users/rkavalap/work/appium-chromedriver/node_modules/orchestrator/lib/runTask.js:52:4)
> at Stream.f (/Users/rkavalap/work/appium-chromedriver/node_modules/end-of-stream/node_modules/once/once.js:17:25)
> at emitOne (events.js:101:20)
> at Stream.emit (events.js:188:7)
> at /Users/rkavalap/work/appium-chromedriver/node_modules/gulp-mocha/index.js:60:12
> at done (/Users/rkavalap/work/appium-chromedriver/node_modules/mocha/lib/mocha.js:498:13)
> at Runner.<anonymous> (/Users/rkavalap/work/appium-chromedriver/node_modules/mocha/lib/runner.js:799:5)
> at emitNone (events.js:91:20)
> at Runner.emit (events.js:185:7)
Failed installation on CentOS 6.5
...
83933 verbose about to build /home/jenkins/node_modules/appium/node_modules/appium-adb/node_modules/winston/node_modules/request
83934 info build /home/jenkins/node_modules/appium/node_modules/appium-adb/node_modules/winston/node_modules/request
83935 verbose linkStuff [ false,
83935 verbose linkStuff false,
83935 verbose linkStuff false,
83935 verbose linkStuff '/home/jenkins/node_modules/appium/node_modules/appium-adb/node_modules/winston/node_modules' ]
83936 info linkStuff [email protected]
83937 verbose linkBins [email protected]
83938 verbose linkMans [email protected]
83939 verbose rebuildBundles [email protected]
83940 verbose rebuildBundles [ 'aws-sign',
83940 verbose rebuildBundles 'cookie-jar',
83940 verbose rebuildBundles 'forever-agent',
83940 verbose rebuildBundles 'form-data',
83940 verbose rebuildBundles 'hawk',
83940 verbose rebuildBundles 'json-stringify-safe',
83940 verbose rebuildBundles 'mime',
83940 verbose rebuildBundles 'oauth-sign',
83940 verbose rebuildBundles 'qs',
83940 verbose rebuildBundles 'tunnel-agent' ]
83941 info install [email protected]
83942 info postinstall [email protected]
83943 verbose unlock done using /home/jenkins/.npm/_locks/request-3faafdb2b3563410.lock for /home/jenkins/node_modules/appium/node_modules/appium-adb/node_modules/w
inston/node_modules/request
83944 verbose about to build /home/jenkins/node_modules/appium/node_modules/appium-adb/node_modules/winston
83945 info build /home/jenkins/node_modules/appium/node_modules/appium-adb/node_modules/winston
83946 verbose linkStuff [ false,
83946 verbose linkStuff false,
83946 verbose linkStuff false,
83946 verbose linkStuff '/home/jenkins/node_modules/appium/node_modules/appium-adb/node_modules' ]
83947 info linkStuff [email protected]
83948 verbose linkBins [email protected]
83949 verbose linkMans [email protected]
83950 verbose rebuildBundles [email protected]
83951 verbose rebuildBundles [ 'async',
83951 verbose rebuildBundles 'colors',
83951 verbose rebuildBundles 'cycle',
83951 verbose rebuildBundles 'eyes',
83951 verbose rebuildBundles 'pkginfo',
83951 verbose rebuildBundles 'request',
83951 verbose rebuildBundles 'stack-trace' ]
83952 info install [email protected]
83953 info postinstall [email protected]
83954 verbose unlock done using /home/jenkins/.npm/_locks/winston-b5e001f8f971b0da.lock for /home/jenkins/node_modules/appium/node_modules/appium-adb/node_modules/w
inston
83955 verbose about to build /home/jenkins/node_modules/appium/node_modules/appium-adb
83956 info build /home/jenkins/node_modules/appium/node_modules/appium-adb
83957 verbose linkStuff [ false,
83957 verbose linkStuff false,
83957 verbose linkStuff false,
83957 verbose linkStuff '/home/jenkins/node_modules/appium/node_modules' ]
83958 info linkStuff [email protected]
83959 verbose linkBins [email protected]
83960 verbose linkMans [email protected]
83961 verbose rebuildBundles [email protected]
83962 verbose rebuildBundles [ '.bin', 'appium-support', 'ncp', 'q', 'underscore', 'winston' ]
83963 info install [email protected]
83964 info postinstall [email protected]
83965 verbose unlock done using /home/jenkins/.npm/_locks/appium-adb-c64a3c8b5b86c264.lock for /home/jenkins/node_modules/appium/node_modules/appium-adb
83966 verbose about to build /home/jenkins/node_modules/appium
83967 verbose unlock done using /home/jenkins/.npm/_locks/appium-fc2de691fadef777.lock for /home/jenkins/node_modules/appium
83968 verbose stack Error: [email protected] install: node install-npm.js
83968 verbose stack Exit status 1
83968 verbose stack at EventEmitter. (/usr/lib/node_modules/npm/lib/utils/lifecycle.js:212:16)
83968 verbose stack at EventEmitter.emit (events.js:98:17)
83968 verbose stack at ChildProcess. (/usr/lib/node_modules/npm/lib/utils/spawn.js:14:12)
83968 verbose stack at ChildProcess.EventEmitter.emit (events.js:98:17)
83968 verbose stack at maybeClose (child_process.js:743:16)
83968 verbose stack at Process.ChildProcess._handle.onexit (child_process.js:810:5)
83969 verbose pkgid [email protected]
83970 verbose cwd /home/jenkins
83971 error Linux 2.6.32-573.1.1.el6.x86_64
83972 error argv "node" "/usr/bin/npm" "install" "[email protected]"
83973 error node v0.10.26
83974 error npm v2.1.18
83975 error code ELIFECYCLE
83976 error [email protected] install: node install-npm.js
83976 error Exit status 1
83977 error Failed at the [email protected] install script 'node install-npm.js'.
83977 error This is most likely a problem with the appium-chromedriver package,
83977 error not with npm itself.
83977 error Tell the author that this fails on your system:
83977 error node install-npm.js
83977 error You can get their info via:
83977 error npm owner ls appium-chromedriver
83977 error There is likely additional logging output above.
83978 verbose exit [ 1, true ]
83979 verbose unbuild node_modules/appium/node_modules/appium-chromedriver
83980 info preuninstall [email protected]
83981 info uninstall [email protected]
83982 verbose unbuild rmStuff [email protected] from /home/jenkins/node_modules
83983 verbose unbuild rmStuff in /home/jenkins/node_modules/appium/node_modules
83984 info postuninstall [email protected]
83985 verbose gentlyRm vacuuming /home/jenkins/node_modules/appium/node_modules/appium-chromedriver
83986 silly gentlyRm purging /home/jenkins/node_modules/appium/node_modules/appium-chromedriver
83987 silly gentlyRm quitting because other entries in /home/jenkins/node_modules/appium/node_modules
83988 verbose unbuild node_modules/appium
83989 info preuninstall [email protected]
83990 info uninstall [email protected]
83991 verbose unbuild rmStuff [email protected] from /home/jenkins/node_modules
83992 verbose gentlyRm verifying that /home/jenkins is managed by npm
83993 verbose gentlyRm verifying that /home/jenkins is managed by npm
83994 verbose gentlyRm verifying that /home/jenkins is managed by npm
83995 silly isManaged /home/jenkins is not inside /home/jenkins/node_modules
83996 silly isManaged /home/jenkins is not inside /home/jenkins/node_modules
83997 silly isManaged /home/jenkins is not inside /home/jenkins/node_modules
83998 silly isManaged /home/jenkins is not inside /home/jenkins/node_modules
83999 silly isManaged /home/jenkins is not inside /home/jenkins/node_modules
84000 silly isManaged /home/jenkins is not inside /home/jenkins/node_modules
84001 silly isManaged /home/jenkins is inside /home/jenkins
84002 silly gentlyRm /home/jenkins is managed by npm
84003 silly gentlyRm /home/jenkins/node_modules/.bin/appium is under /home/jenkins
84004 verbose gentlyRm vacuuming /home/jenkins/node_modules/.bin/appium up to /home/jenkins
84005 silly isManaged /home/jenkins is inside /home/jenkins
84006 silly gentlyRm /home/jenkins is managed by npm
84007 silly gentlyRm /home/jenkins/node_modules/.bin/appium-doctor is under /home/jenkins
84008 verbose gentlyRm vacuuming /home/jenkins/node_modules/.bin/appium-doctor up to /home/jenkins
84009 silly isManaged /home/jenkins is inside /home/jenkins
84010 silly gentlyRm /home/jenkins is managed by npm
84011 silly gentlyRm /home/jenkins/node_modules/.bin/authorize_ios is under /home/jenkins
84012 verbose gentlyRm vacuuming /home/jenkins/node_modules/.bin/authorize_ios up to /home/jenkins
84013 info postuninstall [email protected]
84014 verbose gentlyRm vacuuming /home/jenkins/node_modules/appium
84015 silly gentlyRm purging /home/jenkins/node_modules/appium
84016 silly gentlyRm removing /home/jenkins/node_modules
84017 silly gentlyRm finished vacuuming up to /home/jenkins
...
npm owner ls appium-chromedriver
bootstraponline [email protected]
imurchie [email protected]
jlipps [email protected]
jonahss [email protected]
moizjv [email protected]
scottdixon [email protected]
sebv [email protected]
Please change the proxy requirement
Currently appium-chromedriver package is designed to reach system proxy when downloading driver package.
Please change the behaviour and consider using npm proxy.
appium-chromedriver v2.8.1 requires Chrome browser v46+ on Android device
We're using Appium 1.4 in our system and we are exploring Appium to 1.5 before applying it. One thing we see is that the latest version of appium-chromedriver uses chromedriver v2.21 which only works with Chrome browser v46+ (released just 6 months ago). So we upgraded Chrome browser in our Android devices to v46+ in order to meet with this requirement
The thing is that if Appium 1.5 is installed to our system, we have to upgrade all Chrome browsers in our mobile devices to v46. I just wonder is using chromedriver v2.21 necessary for latest appium-chromedriver or a misconfiguration (using old version of chromedriver is still ok) ?
Note: if Chrome browser is device is below v46, below error message appears in console
org.openqa.selenium.WebDriverException: unknown error: Chrome version must be >= 46.0.2490.0 (Driver info: chromedriver=2.21.371459 (633e689b520b25f3e264a2ede6b74ccc23cb636a),platform=Windows NT 6.1 SP1 x86) (WARNING: The server did not provide any stacktrace information)
Error with chromedriver when installing appium1.6.0
I am getting following error with chromedriver only when tried install of appium 1.6.0 from command line
localhost:~ yongche$ npm install -g appium
[email protected] install /usr/local/lib/node_modules/appium/node_modules/appium-chromedriver
node install-npm.js
(node:2130) DeprecationWarning: os.tmpDir() is deprecated. Use os.tmpdir() instead.
info Chromedriver Install Installing Chromedriver version '2.21' for platform 'mac' and architecture '32'
info Chromedriver Install Opening temp file to write chromedriver_mac32 to...
info Chromedriver Install Downloading http://chromedriver.storage.googleapis.com/2.21/chromedriver_mac32.zip...
RequestError: Error: read ECONNRESET
at new RequestError (/Users/yongche/Downloads/Appium/appium-1.6.0/node_modules/request-promise/lib/errors.js:11:15)
at Request.RP$callback [as _callback] (/Users/yongche/Downloads/Appium/appium-1.6.0/node_modules/request-promise/lib/rp.js:60:32)
at self.callback (/Users/yongche/Downloads/Appium/appium-1.6.0/node_modules/request/request.js:187:22)
at emitOne (events.js:96:13)
at Request.emit (events.js:188:7)
at Request.onRequestError (/Users/yongche/Downloads/Appium/appium-1.6.0/node_modules/request/request.js:813:8)
at emitOne (events.js:96:13)
at ClientRequest.emit (events.js:188:7)
at Socket.socketErrorListener (_http_client.js:309:9)
at emitOne (events.js:96:13)
at Socket.emit (events.js:188:7)
at emitErrorNT (net.js:1281:8)
at _combinedTickCallback (internal/process/next_tick.js:74:11)
at process._tickCallback (internal/process/next_tick.js:98:9)
[email protected] node_modules/appium/node_modules/rcloader/node_modules/lodash -> node_modules/appium/node_modules/appium-android-driver/node_modules/lodash
[email protected] node_modules/appium/node_modules/jsdoctypeparser/node_modules/lodash -> node_modules/appium/node_modules/appium-chromedriver/node_modules/lodash
/usr/local/lib
└── (empty)
npm ERR! Darwin 15.5.0
npm ERR! argv "/usr/local/Cellar/node/7.1.0/bin/node" "/usr/local/bin/npm" "install" "-g" "appium"
npm ERR! node v7.1.0
npm ERR! npm v3.10.9
npm ERR! code ELIFECYCLE
npm ERR! [email protected] install: node install-npm.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] install script 'node install-npm.js'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the appium-chromedriver package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node install-npm.js
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs appium-chromedriver
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls appium-chromedriver
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR! /Users/yongche/npm-debug.log
npm ERR! code 1
Please provide solution for this
thanks
The Added Support for Installing Chromedriver 2.23+ on OS X
I am using version 1.5.3 of Appium and attempting to upgrade my ChromeDriver to 2.9.3 to overcome the issues related to version 6.0.1 on Android Devices. I'm using a MAC MINI using El Capitan. Appium and the tests were working fine until the Android Phones were updated. I found the previously resolved issue with the same title and created a comment on it and opend this issue. I did it this way because I wasn't certain if the issue I'm having relates directley to the packaging of the Chromedriver in the previous issue OR to the nmp update that may not working as expected...
@imurchie, I have used the npm to install [email protected] however when starting Appium 1.5.3 I see in the log the entry:
[Chromedriver] [SYSOUT] Starting ChromeDriver 2.21.371459
This is the second time that I tried to update the chrome driver (now showing version 2.9.4) which seems to be installed but Appium is either producing this erroneous message or not picking up the latest installed chromedriver. Maybe its not an error and I'm just doing something wrong?
startSession() should have restartAdb logic as present in previous versions of appium
@jlipps @imurchie got any thoughts on this.
line 168
async startSession does not handle failed to run adb command scenario. restartAdb logic is required.
This would require appium-chromedriver to take dependency on appium-adb.
below snipped pulled from appium v1.3.5 chromedriver.js - proxyNewSession method
if (typeof body !== "undefined" &&
typeof body.value !== "undefined" &&
typeof body.value.message !== "undefined" &&
body.value.message.indexOf("Failed to run adb command") !== -1) {
logger.error("Chromedriver had trouble running adb");
if (!alreadyRestarted) {
logger.error("Restarting adb for chromedriver");
return this.adb.restartAdb(function () {
this.adb.getConnectedDevices(function () {
doProxy(true);
}.bind(this));
}.bind(this));
} else {
cb(new Error("Chromedriver wasn't able to use adb. Is the server up?"));
}
} else {
logger.error("Chromedriver create session did not work. Status was " +
res.statusCode + " and body was " +
JSON.stringify(body));
cb(new Error("Did not get session redirect from Chromedriver"));
}
1.5 Cleanup
- Make sure all deps are up to date (and there are no unused deps)
- Take a look at all TODOs to see if we need to resolve any for the release
- Set up code coverage
- Set up CI (unit tests, functional tests, code coverage; should be on all relevant platforms, and should include multi-executor parallelism for long-running testsuites)
- Ensure that we are using appium-support functions, not home-grown helpers
- Ensure that we have high unit test code coverage percentage
- Ensure that we have sufficient/appropriate functional test coverage
- Write a decent README, explaining (a) what the purpose of the module is, (b) how it relates to other appium modules, and (c) how to use its interface
- Ensure that code conforms to our style
- Ensure we are not using any sync functions
- Ensure that code is well-commented
- Ensure that non-production code or assets are added to .npmignore to reduce npm install size
Tracking appium/appium#5539
appium-chromedriver npm install is not windows friendly
Some scripts are not executable on Windows environments, this fails when you try to install Appium as well via npm.
npm WARN engine [email protected]: wanted: {"node":"0.8.x"} (current: {"node":"v0.10.26","npm":"1.4.3"})
npm WARN engine [email protected]: wanted: {"node":"0.8.x"} (current: {"node":"v0.10.26","npm":"1.4.3"})
> [email protected] install C:\Users\xxxx\WebstormProjects\xxx\node_modules\appium\node_modules\appium-chromedriver
> $NODE ./bin/install-npm.js
'$NODE' is not recognized as an internal or external command,
operable program or batch file.
npm ERR! Error: ENOENT, lstat 'C:\Users\xxxx\WebstormProjects\xxxx\node_modules\appium\node_modules\appium-xcode\node_modules\babel-runtime\node_module
e.js'
npm ERR! If you need help, you may report this *entire* log,
npm ERR! including the npm and node versions, at:
npm ERR! <http://github.com/npm/npm/issues>
This part is not friendly for my Windows environment, Can we execute, for instance, gulp prepublish instead "$NODE ./node_modules/.bin/gulp prepublish"? And maybe everything else integrated into gulp it will be more friendly with Windows.
"scripts": {
"prepublish": "$NODE ./node_modules/.bin/gulp prepublish",
"test": "./node_modules/.bin/gulp once",
"watch": "./node_modules/.bin/gulp",
"install": "$NODE ./bin/install-npm.js",
"chromedriver": "./node_modules/.bin/gulp prepublish && node ./build/bin/install.js",
"chromedriver_all": "./node_modules/.bin/gulp prepublish && node ./build/bin/install.js --all"
},
ChromeDriver cannot switch context to webview in another app
In my setup, I am using app1 where upon clicking a button app2 is launched. App2 then launches an in-app webview. Switching context takes 60 seconds (times out), but does not throw an exception. This results in an obvious element not found exception when i try to click google's search textbox. It seems that ChromeDriver cannot handle webview in another app.
Last login: Thu Oct 13 22:10:53 on ttys002
apsomeUsers-MacBook-Pro:~ someUser$ appium
[Appium] Welcome to Appium v1.5.3 (REV 29a9c85389753fa6b3106dca6a9146674e1e5c58)
[Appium] Appium REST http interface listener started on 0.0.0.0:4723
[HTTP] --> POST /wd/hub/session {"desiredCapabilities":{"deviceName":"android","platformName":"Android","appActivity":"com.test.app1.MainActivity","appPackage":"com.test.app1","noReset":"true"}}
[MJSONWP] Calling AppiumDriver.createSession() with args: [{"deviceName":"android","p...
[Appium] Creating new AndroidDriver session
[Appium] Capabilities:
[Appium] deviceName: 'android'
[Appium] platformName: 'Android'
[Appium] appActivity: 'com.test.app1.MainActivity'
[Appium] appPackage: 'com.test.app1'
[Appium] noReset: 'true'
[BaseDriver] Capability 'noReset' changed from string to boolean. This may cause unexpected behavior
[BaseDriver] Session created with session id: f11e9520-856e-4bde-b8d5-b0104893ea16
[debug] [AndroidDriver] Getting Java version
[AndroidDriver] Java version is: 1.7.0_67
[ADB] Checking whether adb is present
[ADB] Using adb from /Users/someUser/software/android-sdk/platform-tools/adb
[AndroidDriver] Retrieving device list
[debug] [ADB] Trying to find a connected android device
[debug] [ADB] Getting connected devices...
[debug] [ADB] 1 device(s) connected
[AndroidDriver] Using device: 6666b2ca
[ADB] Checking whether adb is present
[ADB] Using adb from /Users/someUser/software/android-sdk/platform-tools/adb
[debug] [ADB] Setting device id to 6666b2ca
[AndroidDriver] App file was not listed, instead we're going to run com.test.app1 directly on the device
[debug] [AndroidDriver] Checking whether package is present on the device
[debug] [ADB] Getting connected devices...
[debug] [ADB] 1 device(s) connected
[debug] [ADB] Running /Users/someUser/software/android-sdk/platform-tools/adb with args: ["-P",5037,"-s","6666b2ca","shell","pm","list","packages","com.test.app1"]
[AndroidDriver] Starting Android session
[debug] [ADB] Running /Users/someUser/software/android-sdk/platform-tools/adb with args: ["-P",5037,"-s","6666b2ca","wait-for-device"]
[debug] [ADB] Getting connected devices...
[debug] [ADB] 1 device(s) connected
[debug] [ADB] Running /Users/someUser/software/android-sdk/platform-tools/adb with args: ["-P",5037,"-s","6666b2ca","shell","echo","ping"]
[debug] [Logcat] Starting logcat capture
[debug] [AndroidDriver] Pushing settings apk to device...
[debug] [ADB] Running /Users/someUser/software/android-sdk/platform-tools/adb with args: ["-P",5037,"-s","6666b2ca","install","/usr/local/lib/node_modules/appium/node_modules/appium-android-driver/node_modules/io.appium.settings/bin/settings_apk-debug.apk"]
[debug] [AndroidDriver] Pushing unlock helper app to device...
[debug] [ADB] Running /Users/someUser/software/android-sdk/platform-tools/adb with args: ["-P",5037,"-s","6666b2ca","install","/usr/local/lib/node_modules/appium/node_modules/appium-android-driver/node_modules/appium-unlock/bin/unlock_apk-debug.apk"]
[ADB] Getting device platform version
[debug] [ADB] Getting connected devices...
[debug] [ADB] 1 device(s) connected
[debug] [ADB] Running /Users/someUser/software/android-sdk/platform-tools/adb with args: ["-P",5037,"-s","6666b2ca","shell","getprop","ro.build.version.release"]
[debug] [ADB] Getting connected devices...
[debug] [ADB] 1 device(s) connected
[debug] [ADB] Running /Users/someUser/software/android-sdk/platform-tools/adb with args: ["-P",5037,"-s","6666b2ca","shell","dumpsys","window"]
[AndroidDriver] Screen already unlocked, doing nothing
[debug] [AndroidBootstrap] Watching for bootstrap disconnect
[debug] [ADB] Forwarding system: 4724 to device: 4724
[debug] [ADB] Running /Users/someUser/software/android-sdk/platform-tools/adb with args: ["-P",5037,"-s","6666b2ca","forward","tcp:4724","tcp:4724"]
[debug] [UiAutomator] Starting UiAutomator
[debug] [UiAutomator] Moving to state 'starting'
[debug] [UiAutomator] Parsing uiautomator jar
[debug] [UiAutomator] Found jar name: 'AppiumBootstrap.jar'
[debug] [ADB] Running /Users/someUser/software/android-sdk/platform-tools/adb with args: ["-P",5037,"-s","6666b2ca","push","/usr/local/lib/node_modules/appium/node_modules/appium-android-driver/node_modules/appium-android-bootstrap/bootstrap/bin/AppiumBootstrap.jar","/data/local/tmp/"]
[debug] [ADB] Attempting to kill all uiautomator processes
[debug] [ADB] Getting all processes with uiautomator
[debug] [ADB] Getting connected devices...
[debug] [ADB] 1 device(s) connected
[debug] [ADB] Running /Users/someUser/software/android-sdk/platform-tools/adb with args: ["-P",5037,"-s","6666b2ca","shell","ps","uiautomator"]
[ADB] No uiautomator process found to kill, continuing...
[debug] [UiAutomator] Starting UIAutomator
[debug] [ADB] Creating ADB subprocess with args: -P, 5037, -s, 6666b2ca, shell, uiautomator, runtest, AppiumBootstrap.jar, -c, io.appium.android.bootstrap.Bootstrap, -e, pkg, com.test.app1, -e, disableAndroidWatchers, false, -e, acceptSslCerts, false
[debug] [UiAutomator] Moving to state 'online'
[AndroidBootstrap] [BOOTSTRAP LOG] [debug] Registered crash watchers.
[AndroidBootstrap] Android bootstrap socket is now connected
[debug] [ADB] Getting connected devices...
[AndroidBootstrap] [BOOTSTRAP LOG] [debug] Client connected
[debug] [ADB] 1 device(s) connected
[debug] [ADB] Running /Users/someUser/software/android-sdk/platform-tools/adb with args: ["-P",5037,"-s","6666b2ca","shell","getprop","ro.build.version.sdk"]
[debug] [ADB] Device API level: 23
[debug] [ADB] Getting connected devices...
[debug] [ADB] 1 device(s) connected
[debug] [ADB] Running /Users/someUser/software/android-sdk/platform-tools/adb with args: ["-P",5037,"-s","6666b2ca","shell","am","start","-n","com.test.app1/com.test.app1.MainActivity","-S","-a","android.intent.action.MAIN","-c","android.intent.category.LAUNCHER","-f","0x10200000"]
[Appium] New AndroidDriver session created successfully, session f11e9520-856e-4bde-b8d5-b0104893ea16 added to master session list
[MJSONWP] Responding to client with driver.createSession() result: {"platform":"LINUX","webSto...
[HTTP] <-- POST /wd/hub/session 200 6667 ms - 600
[HTTP] --> POST /wd/hub/session/f11e9520-856e-4bde-b8d5-b0104893ea16/element {"using":"id","value":"com.test.app1:id/button"}
[MJSONWP] Calling AppiumDriver.findElement() with args: ["id","com.test.app1:id/but...
[debug] [BaseDriver] Waiting up to 0 ms for condition
[debug] [AndroidBootstrap] Sending command to android: {"cmd":"action","action":"find","params":{"strategy":"id","selector":"com.test.app1:id/button","context":"","multiple":false}}
[AndroidBootstrap] [BOOTSTRAP LOG] [debug] Got data from client: {"cmd":"action","action":"find","params":{"strategy":"id","selector":"com.test.app1:id/button","context":"","multiple":false}}
[AndroidBootstrap] [BOOTSTRAP LOG] [debug] Got command of type ACTION
[AndroidBootstrap] [BOOTSTRAP LOG] [debug] Got command action: find
[AndroidBootstrap] [BOOTSTRAP LOG] [debug] Finding 'com.test.app1:id/button' using 'ID' with the contextId: '' multiple: false
[AndroidBootstrap] [BOOTSTRAP LOG] [debug] Using: UiSelector[INSTANCE=0, RESOURCE_ID=com.test.app1:id/button]
[AndroidBootstrap] [BOOTSTRAP LOG] [debug] Returning result: {"status":0,"value":{"ELEMENT":"1"}}
[debug] [AndroidBootstrap] Received command result from bootstrap
[MJSONWP] Responding to client with driver.findElement() result: {"ELEMENT":"1"}
[HTTP] <-- POST /wd/hub/session/f11e9520-856e-4bde-b8d5-b0104893ea16/element 200 722 ms - 87
[HTTP] --> POST /wd/hub/session/f11e9520-856e-4bde-b8d5-b0104893ea16/element/1/click {"id":"1"}
[MJSONWP] Calling AppiumDriver.click() with args: ["1","f11e9520-856e-4bde-b8...
[debug] [AndroidBootstrap] Sending command to android: {"cmd":"action","action":"element:click","params":{"elementId":"1"}}
[AndroidBootstrap] [BOOTSTRAP LOG] [debug] Got data from client: {"cmd":"action","action":"element:click","params":{"elementId":"1"}}
[AndroidBootstrap] [BOOTSTRAP LOG] [debug] Got command of type ACTION
[AndroidBootstrap] [BOOTSTRAP LOG] [debug] Got command action: click
[AndroidBootstrap] [BOOTSTRAP LOG] [debug] Returning result: {"status":0,"value":true}
[debug] [AndroidBootstrap] Received command result from bootstrap
[MJSONWP] Responding to client with driver.click() result: true
[HTTP] <-- POST /wd/hub/session/f11e9520-856e-4bde-b8d5-b0104893ea16/element/1/click 200 241 ms - 76
[HTTP] --> GET /wd/hub/session/f11e9520-856e-4bde-b8d5-b0104893ea16/contexts {}
[MJSONWP] Calling AppiumDriver.getContexts() with args: ["f11e9520-856e-4bde-b8d5-b...
[debug] [AndroidDriver] Getting a list of available webviews
[debug] [ADB] Getting connected devices...
[debug] [ADB] 1 device(s) connected
[debug] [ADB] Running /Users/someUser/software/android-sdk/platform-tools/adb with args: ["-P",5037,"-s","6666b2ca","shell","cat","/proc/net/unix"]
[debug] [AndroidDriver] WEBVIEW_8446 mapped to pid 8446
[debug] [AndroidDriver] Getting process name for webview
[debug] [ADB] Getting connected devices...
[debug] [ADB] 1 device(s) connected
[debug] [ADB] Running /Users/someUser/software/android-sdk/platform-tools/adb with args: ["-P",5037,"-s","6666b2ca","shell","ps"]
[debug] [AndroidDriver] Parsed pid: 8446 pkg: com.test.app2!
[debug] [AndroidDriver] from: u0_a183,8446,458,2414196,193540,SyS_epoll_,0000000000,S,com.test.app2
[debug] [AndroidDriver] returning process name: com.test.app2
[debug] [AndroidDriver] Found webviews: ["WEBVIEW_com.test.app2"]
[debug] [AndroidDriver] Available contexts: ["NATIVE_APP","WEBVIEW_com.test.app2"]
[MJSONWP] Responding to client with driver.getContexts() result: ["NATIVE_APP","WEBVIEW_com....
[HTTP] <-- GET /wd/hub/session/f11e9520-856e-4bde-b8d5-b0104893ea16/contexts 200 172 ms - 110
[HTTP] --> POST /wd/hub/session/f11e9520-856e-4bde-b8d5-b0104893ea16/context {"name":"WEBVIEW_com.test.app2"}
[MJSONWP] Calling AppiumDriver.setContext() with args: ["WEBVIEW_com.test.app2","f...
[debug] [AndroidDriver] Getting a list of available webviews
[debug] [ADB] Getting connected devices...
[debug] [ADB] 1 device(s) connected
[debug] [ADB] Running /Users/someUser/software/android-sdk/platform-tools/adb with args: ["-P",5037,"-s","6666b2ca","shell","cat","/proc/net/unix"]
[debug] [AndroidDriver] WEBVIEW_8446 mapped to pid 8446
[debug] [AndroidDriver] Getting process name for webview
[debug] [ADB] Getting connected devices...
[debug] [ADB] 1 device(s) connected
[debug] [ADB] Running /Users/someUser/software/android-sdk/platform-tools/adb with args: ["-P",5037,"-s","6666b2ca","shell","ps"]
[debug] [AndroidDriver] Parsed pid: 8446 pkg: com.test.app2!
[debug] [AndroidDriver] from: u0_a183,8446,458,2439776,204188,SyS_epoll_,0000000000,S,com.test.app2
[debug] [AndroidDriver] returning process name: com.test.app2
[debug] [AndroidDriver] Found webviews: ["WEBVIEW_com.test.app2"]
[debug] [AndroidDriver] Available contexts: ["NATIVE_APP","WEBVIEW_com.test.app2"]
[debug] [AndroidDriver] Connecting to chrome-backed webview context 'WEBVIEW_com.test.app2'
[debug] [Chromedriver] Changed state to 'starting'
[Chromedriver] Set chromedriver binary as: /usr/local/lib/node_modules/appium/node_modules/appium-android-driver/node_modules/appium-chromedriver/chromedriver/mac/chromedriver
[Chromedriver] Killing any old chromedrivers, running: pkill -15 -f "/usr/local/lib/node_modules/appium/node_modules/appium-android-driver/node_modules/appium-chromedriver/chromedriver/mac/chromedriver.*--port=9515"
[Chromedriver] No old chromedrivers seemed to exist
[Chromedriver] Spawning chromedriver with: /usr/local/lib/node_modules/appium/node_modules/appium-android-driver/node_modules/appium-chromedriver/chromedriver/mac/chromedriver --url-base=wd/hub --port=9515 --adb-port=5037
[Chromedriver] [STDOUT] Starting ChromeDriver 2.21.371459 (36d3d07f660ff2bc1bf28a75d1cdabed0983e7c4) on port 9515
Only local connections are allowed.
[JSONWP Proxy] Proxying [GET /status] to [GET http://127.0.0.1:9515/wd/hub/status] with no body
[Chromedriver] [STDERR] [warn] kq_init: detected broken kqueue; not using.: Undefined error: 0
[JSONWP Proxy] Got response with status 200: "{\"sessionId\":\"\",\"stat...
[JSONWP Proxy] Proxying [POST /session] to [POST http://127.0.0.1:9515/wd/hub/session] with body: {"desiredCapabilities":{"ch...
[JSONWP Proxy] Got response with status 200: {"sessionId":"976f0690a1f8a...
[debug] [Chromedriver] Changed state to 'online'
[MJSONWP] Responding to client with driver.setContext() result: null
[HTTP] <-- POST /wd/hub/session/f11e9520-856e-4bde-b8d5-b0104893ea16/context 200 60868 ms - 76
[HTTP] --> POST /wd/hub/session/f11e9520-856e-4bde-b8d5-b0104893ea16/element {"using":"id","value":"lst-ib"}
[MJSONWP] Driver proxy active, passing request on via HTTP proxy
[JSONWP Proxy] Proxying [POST /wd/hub/session/f11e9520-856e-4bde-b8d5-b0104893ea16/element] to [POST http://127.0.0.1:9515/wd/hub/session/976f0690a1f8a1fa8f834ab56f740828/element] with body: {"using":"id","value":"lst-...
[JSONWP Proxy] Got response with status 200: {"sessionId":"976f0690a1f8a...
[JSONWP Proxy] Replacing sessionId 976f0690a1f8a1fa8f834ab56f740828 with f11e9520-856e-4bde-b8d5-b0104893ea16
[HTTP] <-- POST /wd/hub/session/f11e9520-856e-4bde-b8d5-b0104893ea16/element 200 6 ms - 220
[HTTP] --> DELETE /wd/hub/session/f11e9520-856e-4bde-b8d5-b0104893ea16 {}
[MJSONWP] Calling AppiumDriver.deleteSession() with args: ["f11e9520-856e-4bde-b8d5-b...
[debug] [AndroidDriver] Shutting down Android driver
[debug] [AndroidDriver] Stopping chromedriver for context WEBVIEW_com.test.app2
[debug] [Chromedriver] Changed state to 'stopping'
[JSONWP Proxy] Proxying [DELETE /] to [DELETE http://127.0.0.1:9515/wd/hub/session/976f0690a1f8a1fa8f834ab56f740828] with no body
[JSONWP Proxy] Got response with status 200: "{\"sessionId\":\"976f0690a...
[debug] [Chromedriver] Changed state to 'stopped'
[debug] [ADB] Getting connected devices...
[debug] [ADB] 1 device(s) connected
[debug] [ADB] Running /Users/someUser/software/android-sdk/platform-tools/adb with args: ["-P",5037,"-s","6666b2ca","shell","am","force-stop","com.test.app1"]
[debug] [ADB] Getting connected devices...
[debug] [ADB] 1 device(s) connected
[debug] [ADB] Running /Users/someUser/software/android-sdk/platform-tools/adb with args: ["-P",5037,"-s","6666b2ca","shell","am","force-stop","io.appium.unlock"]
[debug] [ADB] Pressing the HOME button
[debug] [ADB] Getting connected devices...
[debug] [ADB] 1 device(s) connected
[debug] [ADB] Running /Users/someUser/software/android-sdk/platform-tools/adb with args: ["-P",5037,"-s","6666b2ca","shell","input","keyevent",3]
[debug] [Logcat] Stopping logcat capture
[debug] [AndroidBootstrap] Sending command to android: {"cmd":"shutdown"}
[AndroidBootstrap] [BOOTSTRAP LOG] [debug] Got data from client: {"cmd":"shutdown"}
[AndroidBootstrap] [BOOTSTRAP LOG] [debug] Got command of type SHUTDOWN
[AndroidBootstrap] [BOOTSTRAP LOG] [debug] Returning result: {"status":0,"value":"OK, shutting down"}
[debug] [AndroidBootstrap] Received command result from bootstrap
[debug] [UiAutomator] Shutting down UiAutomator
[debug] [UiAutomator] Moving to state 'stopping'
[debug] [UiAutomator] UiAutomator shut down normally
[debug] [UiAutomator] Moving to state 'stopped'
[debug] [ADB] Attempting to kill all uiautomator processes
[debug] [ADB] Getting all processes with uiautomator
[debug] [ADB] Getting connected devices...
[debug] [ADB] 1 device(s) connected
[debug] [ADB] Running /Users/someUser/software/android-sdk/platform-tools/adb with args: ["-P",5037,"-s","6666b2ca","shell","ps","uiautomator"]
[ADB] No uiautomator process found to kill, continuing...
[debug] [UiAutomator] Moving to state 'stopped'
[Appium] Removing session f11e9520-856e-4bde-b8d5-b0104893ea16 from our master session list
[debug] [MJSONWP] Received response: null
[debug] [MJSONWP] But deleting session, so not returning
[MJSONWP] Responding to client with driver.deleteSession() result: null
[HTTP] <-- DELETE /wd/hub/session/f11e9520-856e-4bde-b8d5-b0104893ea16 200 2641 ms - 76
Installation via proxy
info Chromedriver Install Downloading http://chromedriver.storage.googleapis.com/2.21/chromedriver_linux64.zip...
RequestError: Error: Invalid protocol: squid-cluster.prod.dak.polsatc:
at new RequestError (/atms/nodejs/lib/node_modules/appium-chromedriver/node_modules/request-promise/lib/errors.js:11:15)
at Request.RP$callback as _callback
at self.callback (/atms/nodejs/lib/node_modules/appium-chromedriver/node_modules/request/request.js:199:22)
at emitOne (events.js:90:13)
at Request.emit (events.js:182:7)
at Request.init (/atms/nodejs/lib/node_modules/appium-chromedriver/node_modules/request/request.js:472:17)
at Request.RP$initInterceptor as init
at new Request (/atms/nodejs/lib/node_modules/appium-chromedriver/node_modules/request/request.js:141:8)
at request (/atms/nodejs/lib/node_modules/appium-chromedriver/node_modules/request/index.js:55:10)
at Function.get (/atms/nodejs/lib/node_modules/appium-chromedriver/node_modules/request/index.js:63:12)
at installForPlatform$ (lib/install.js:80:28)
at tryCatch (/atms/nodejs/lib/node_modules/appium-chromedriver/node_modules/babel-runtime/regenerator/runtime.js:67:40)
at GeneratorFunctionPrototype.invoke as _invoke
at GeneratorFunctionPrototype.prototype.(anonymous function) as next
at GeneratorFunctionPrototype.invoke (/atms/nodejs/lib/node_modules/appium-chromedriver/node_modules/babel-runtime/regenerator/runtime.js:136:37)
at run (/atms/nodejs/lib/node_modules/appium-chromedriver/node_modules/core-js/library/modules/es6.promise.js:104:47)
Error trying to install Chromedriver binary. Waiting and trying again.
I cannot install the appium-chromedriver from npm currently as I get the following error:
Error trying to install Chromedriver binary. Waiting and trying again.
Error: Cannot find module './build/lib/install'
What can I do to fix this?
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.