question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

npm install -g appium

See original GitHub issue

The problem

Appium installation fails at downloading chromedriver. When I checked the folder the driver is there, so not sure why it fails. I WAS able to download the Appium client, WS; just not Appium server.

[Snippet] [17:47:56] [Chromedriver Install] Downloading https://chromedriver.storage.googleapis.com/2.46/chromedriver_win32.zip… RequestError: Error: connect ETIMEDOUT 172.217.164.144:443

[Full message]

c:\node-v10.15.3-win-x64>npm install -g appium
npm WARN deprecated fsevents@2.0.1: Not Ready For Production
c:\node-v10.15.3-win-x64\authorize-ios -> c:\node-v10.15.3-win-x64\node_modules\appium\node_modules\.bin\authorize-ios
c:\node-v10.15.3-win-x64\appium -> c:\node-v10.15.3-win-x64\node_modules\appium\build\lib\main.js

> appium-chromedriver@4.11.0 install c:\node-v10.15.3-win-x64\node_modules\appium\node_modules\appium-chromedriver
> node install-npm.js

[17:47:56] [Chromedriver Install] Installing Chromedriver version '2.46' for platform 'win' and architecture '32'
[17:47:56] [Chromedriver Install] Opening temp file to write 'chromedriver_win32' to...
[17:47:56] [Chromedriver Install] Opened temp file 'C:\Users\deng\AppData\Local\Temp\2\2019221-1936-1huogvw.no7ui\chromedriver_win32.zip'
[17:47:56] [Chromedriver Install] Downloading https://chromedriver.storage.googleapis.com/2.46/chromedriver_win32.zip...
RequestError: Error: connect ETIMEDOUT 172.217.164.144:443
    at new RequestError (c:\node-v10.15.3-win-x64\node_modules\appium\node_modules\request-promise-core\lib\errors.js:14:15)
    at Request.plumbing.callback (c:\node-v10.15.3-win-x64\node_modules\appium\node_modules\request-promise-core\lib\plumbing.js:87:29)
    at Request.RP$callback [as _callback] (c:\node-v10.15.3-win-x64\node_modules\appium\node_modules\request-promise-core\lib\plumbing.js:46:31)
    at self.callback (c:\node-v10.15.3-win-x64\node_modules\appium\node_modules\request\request.js:185:22)
    at Request.emit (events.js:189:13)
    at Request.onRequestError (c:\node-v10.15.3-win-x64\node_modules\appium\node_modules\request\request.js:881:8)
    at ClientRequest.emit (events.js:189:13)
    at TLSSocket.socketErrorListener (_http_client.js:392:9)
    at TLSSocket.emit (events.js:189:13)
    at emitErrorNT (internal/streams/destroy.js:82:8)
    at emitErrorAndCloseNT (internal/streams/destroy.js:50:3)
    at process._tickCallback (internal/process/next_tick.js:63:19)
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.0.1 (node_modules\appium\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.0.1: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"}
)

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! appium-chromedriver@4.11.0 install: `node install-npm.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the appium-chromedriver@4.11.0 install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\deng\AppData\Roaming\npm-cache\_logs\2019-03-22T00_49_07_467Z-debug.log

c:\node-v10.15.3-win-x64>

Environment

  • Appium version: the latest one that npm installs
  • Last Appium version that did not exhibit the issue (if applicable): unsure
  • Desktop OS/version used to run Appium: Win 7
  • Node.js version (unless using Appium.app|exe): 10.15.3
  • Npm or Yarn package manager: NPM 6.4.1
  • Mobile platform/version under test: Appium
  • Real device or emulator/simulator: unsure
  • Appium CLI or Appium.app|exe: unsure

Details

If necessary, describe the problem you have been experiencing in more detail.

Link to Appium logs

Create a GIST which is a paste of your full Appium logs, and link them here. Do NOT paste your full Appium logs here, as it will make this issue very long and hard to read! If you are reporting a bug, always include Appium logs!

Code To Reproduce Issue [ Good To Have ]

  1. Open CMD 2, execute command: npm install -g appium

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Comments:19 (5 by maintainers)

github_iconTop GitHub Comments

6reactions
mykola-mokhnachcommented, Mar 22, 2019

developer

5reactions
dpgrahamcommented, Mar 22, 2019

@DavidEngNJ you can download Appium Desktop from http://appium.io… it’s a GUI with Appium bundled in it.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Getting Started - Appium
Appium can be installed in one of two ways: via NPM or by downloading Appium Desktop, which is a graphical, desktop-based way to...
Read more >
appium - npm
Start using appium in your project by running `npm i appium`. There are 50 other projects in the npm registry using appium.
Read more >
How to Download and Install Appium | BrowserStack
Method 2: Installing Appium using Appium Desktop Client · Visit the official Appium site · Click on the Download Appium button. Appium download....
Read more >
Install Appium via npm - GitBook
One of the alternative way to install Appium is to install via npm (Node JS Package Manager). ... Brew will be very handy...
Read more >
Appium Installation 2022: How to Install Appium on Windows ...
1. Install Appium with node.js ... To install homebrew, all you need to do is to copy the script as seen in the...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found