Resolve Chromedriver’s original error: chrome not reachable

The error message is as follows:

error: Chromedriver: Chromedriver exited unexpectedly with code null, signal SIG
TERM
info: Chromedriver: Changed state to 'stopped'
warn: Chromedriver for context WEBVIEW_com.tencent.mm:tools stopped unexpectedly

warn: Chromedriver quit unexpectedly, but it wasn't the active context, ignoring

error: Chromedriver: Error: An error occurred (Original error: chrome not reacha
became
  (Driver info: chromedriver=2.18.343845 (73dd713ba7fbfb73cbb514e62641d8c96a9468
2a),platform=Windows NT 6.1 x86_64))
    at JWProxy.command$ (lib/proxy.js:133:15)
    but tryCatch (500: \ Program Files \ epochs \ node_modules \ appium \ node_modules \ appium
-chromedriver\node_modules\appium-jsonwp-proxy\node_modules\babel-runtime\regene
rator\runtime.js:67:40)
    at GeneratorFunctionPrototype.invoke [as _invoke] (D:\Program Files\Appium\n
ode_modules \ appium \ node_modules \ appium -chromedriver \ node_modules \ appium-jsonwp- p
roxy\node_modules\babel-runtime\regenerator\runtime.js:315:22)
    at GeneratorFunctionPrototype.prototype.(anonymous function) [as next] (D:\P
ROGRA Files \ epochs \ node_modules \ appium \ node_modules \ appium - chromedriver \ node_mo
dules \ appium -jsonwp-Proxy \ node_modules \ Isabel-runtime \ regenerator \ runtime.js: 100 :
 21 )
    at GeneratorFunctionPrototype.invoke (D:\Program Files\Appium\node_modules\a
ppium \ node_modules \ appium -chromedriver \ node_modules \ appium-jsonwp- Proxy \ node_mod
ules\babel-runtime\regenerator\runtime.js:136:37)
    at bound (domain.js:287:14)
    at GeneratorFunctionPrototype.runBound (domain.js:300:12)
    at run (500: \ Program Files \ epochs \ node_modules \ appium \ node_modules \ appium - genious
medriver\node_modules\appium-jsonwp-proxy\node_modules\babel-runtime\node_module
s\core-js\library\modules\es6.promise.js:89:39)
    at 500: \ Program Files \ epochs \ node_modules \ appium \ node_modules \ appium - chromedri
spring \ node_modules \ appium -jsonwp-Proxy \ node_modules \ babel- the runtime \ node_modules \ heart
the -JS \ Library \ modules \ es6.promise.js: 100 : 28 
    at Flush (500: \ Program Files \ epochs \ node_modules \ appium \ node_modules \ appium - ch
romedriver \ node_modules \ appium -jsonwp-Proxy \ node_modules \ babel- the runtime \ node_modu
les\core-js\library\modules\$.microtask.js:17:13)
    at nextTickCallbackWith0Args (node.js:420:9)
    at process._tickDomainCallback (node.js:390:13)
 { [Error: An error occurred (Original error: chrome not reachable
  (Driver info: chromedriver=2.18.343845 (73dd713ba7fbfb73cbb514e62641d8c96a9468
2a),platform=Windows NT 6.1 x86_64))]
  status: 100,
  value: { message: 'chrome not reachable\n  (Driver info: chromedriver=2.18.343
845 (73dd713ba7fbfb73cbb514e62641d8c96a94682a),platform=Windows NT 6.1 x86_64)'
},
  httpCode: 200 }

 

Solution: Modify the files in the Appium installation directory, for example:

500: \ Program Files \ epochs \ node_modules \ appium \ lib \ devices \ Android \ android-hybrid.js

Find the androidHybrid.startChromedriverProxy function and comment out the relevant content.

 

 

problem causes:

When Appium switches to the Html page for the first time, it will generate a new Chromedriver; when it switches to Html for the second time, it will use the existing Chromedriver. But in fact, every time we open an Activity in our application, a WebChromeClient is generally recreated, so here we change it to generate a new Chromedriver anyway.


Read More:

Leave a Reply

Your email address will not be published. Required fields are marked *