Chrome version 76 issue

Chrome latest version 76, not supported by appium version 1.14.
here in below image, it is clearly mentioned that appium support chrome version between 71 to 75.
but my current chrome version is 76. I don’t know how to resolve this issue.

@Vikrant_Shah
if you are installed appium with npm execute (uninstall is important!):

npm uninstall -g appium
npm install -g appium --chromedriver_version="76.0.3809.68"
1 Like

There is the link to the troubleshooting document in that error message. I’m just wondering on why nobody is reading that…

@mykola-mokhnach i am wondering why Appium by default installing outdated chromeDriver?

3 Likes

It installs the most recent version by default. It’s just too new for the given browser version.

hi @Aleksei and @mykola-mokhnach , i tried with all but can’t resolve this issue on android mobile emulator Chrome version "76.0.3809.111 ":
npm uninstall -g appium
npm install -g appium --chromedriver_version=“76.0.3809.111” .

@Nguy_n_Xuan_Tr_ng no. You chrome driver version is 2.46. Not 76… try exactly mine line of code. Do not change it

yeah , i tried it and my logs here :

Cmd : with your code.

@Nguy_n_Xuan_Tr_ng installing appium via “npm” will not update your apium GUI suite (screen with header: ‘The server is running’)!
After installing with NPM you should start appium in command line. with “appium …parameters”

1 Like

Thanks bro. It worked :+1:

i am very new, where to run this npm command

Thanks for solution i got same issue

Hi , My mobile has chrome version 76.0.3809.132, and my mac has
“76.0.3809.68”,

still getting below error,

[debug] [W3C (6f3328dd)] Calling AppiumDriver.setContext() with args: [“WEBVIEW_com.my11circle.android”,“6f3328dd-13ef-4a34-ba8a-135262ec6ef7”]
[debug] [AndroidDriver] Getting a list of available webviews
[debug] [ADB] Running ‘/Users/anilpatidar/Library/Android/sdk/platform-tools/adb -P 5037 -s 349c0ada shell cat /proc/net/unix’
[debug] [AndroidDriver] WEBVIEW_12760 mapped to pid 12760
[debug] [AndroidDriver] Getting process name for webview
[debug] [ADB] Running ‘/Users/anilpatidar/Library/Android/sdk/platform-tools/adb -P 5037 -s 349c0ada shell ps’
[debug] [AndroidDriver] Parsed pid: ‘12760’ pkg: ‘com.my11circle.android’ from
[debug] [AndroidDriver] USER PID PPID VSZ RSS WCHAN ADDR FRZ S NAME
[debug] [AndroidDriver] u0_a821 12760 1185 2116372 240484 0 0 efg S com.my11circle.android
[debug] [AndroidDriver] Returning process name: ‘com.my11circle.android’
[debug] [AndroidDriver] Found webviews: [“WEBVIEW_com.my11circle.android”]
[debug] [AndroidDriver] Available contexts: [“NATIVE_APP”,“WEBVIEW_com.my11circle.android”]
[debug] [AndroidDriver] Connecting to chrome-backed webview context ‘WEBVIEW_com.my11circle.android’
[debug] [AndroidDriver] A port was not given, using random free port: 8000
[debug] [AndroidDriver] Before starting chromedriver, androidPackage is ‘com.my11circle.android’
[debug] [Chromedriver] Changed state to ‘starting’
[debug] [Chromedriver] Found 1 executable in ‘/usr/local/lib/node_modules/appium/node_modules/appium-chromedriver/chromedriver/mac’
[debug] [Chromedriver] The following Chromedriver executables were found:
[debug] [Chromedriver] ‘/usr/local/lib/node_modules/appium/node_modules/appium-chromedriver/chromedriver/mac/chromedriver’ (version ‘76.0.3809.68’, minimum Chrome version ‘Unknown’)
[debug] [ADB] Getting package info for ‘com.android.chrome’
[debug] [ADB] Running ‘/Users/anilpatidar/Library/Android/sdk/platform-tools/adb -P 5037 -s 349c0ada shell dumpsys package com.android.chrome’
[debug] [Chromedriver] Found Chrome bundle ‘com.android.chrome’ version ‘76.0.3809’
[Chromedriver] No known Chromedriver available to automate Chrome version ‘76.0.3809’.
[Chromedriver] Using Chromedriver version ‘76.0.3809.68’, which has not been tested with Appium.

[Chromedriver] Set chromedriver binary as: /usr/local/lib/node_modules/appium/node_modules/appium-chromedriver/chromedriver/mac/chromedriver
[debug] [Chromedriver] Killing any old chromedrivers, running: pkill -15 -f “/usr/local/lib/node_modules/appium/node_modules/appium-chromedriver/chromedriver/mac/chromedriver.*–port=8000”
[Chromedriver] No old chromedrivers seem to exist
[debug] [Chromedriver] Cleaning any old adb forwarded port socket connections
[debug] [ADB] List forwarding ports
[debug] [ADB] Running ‘/Users/anilpatidar/Library/Android/sdk/platform-tools/adb -P 5037 -s 349c0ada forward --list’
[Chromedriver] Spawning chromedriver with: /usr/local/lib/node_modules/appium/node_modules/appium-chromedriver/chromedriver/mac/chromedriver --url-base=wd/hub --port=8000 --adb-port=5037 --verbose
[debug] [Chromedriver] Chromedriver version: ‘76.0.3809.68’
[debug] [WD Proxy] Matched ‘/status’ to command name ‘getStatus’
[debug] [WD Proxy] Proxying [GET /status] to [GET http://127.0.0.1:8000/wd/hub/status] with no body
[debug] [WD Proxy] Got response with status 200: “{“value”:{“build”:{“version”:“76.0.3809.68 (420c9498db8ce8fcd190a954d51297672c1515d5-refs/branch-heads/[email protected]{#864})”},“message”:“ChromeDriver ready for new sessions.”,“os”:{“arch”:“x86_64”,“name”:“Mac OS X”,“version”:“10.13.4”},“ready”:true}}”
[debug] [WD Proxy] Determined that the downstream protocol for proxy is W3C
[debug] [WD Proxy] Matched ‘/session’ to command name ‘createSession’
[debug] [WD Proxy] Proxying [POST /session] to [POST http://127.0.0.1:8000/wd/hub/session] with body: {“desiredCapabilities”:{“chromeOptions”:{“androidPackage”:“com.my11circle.android”,“androidUseRunningApp”:true,“androidDeviceSerial”:“349c0ada”},“loggingPrefs”:{“browser”:“ALL”}}}
[debug] [WD Proxy] Got response with status 200: {“sessionId”:“3d996353e928643b7e7c7208d502d3c6”,“status”:13,“value”:{“message”:“unknown error: Failed to get PID for the following process: com.my11circle.android\n (process name must be specified if not equal to package name)\n (Driver info: chromedriver=76.0.3809.68 (420c9498db8ce8fcd190a954d51297672c1515d5-refs/branch-heads/[email protected]{#864}),platform=Mac OS X 10.13.4 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: Failed to get PID for the following process: com.my11circle.android
[Chromedriver] (process name must be specified if not equal to package name)
[Chromedriver] (Driver info: chromedriver=76.0.3809.68 (420c9498db8ce8fcd190a954d51297672c1515d5-refs/branch-heads/[email protected]{#864}),platform=Mac OS X 10.13.4 x86_64)
[Chromedriver] at Object.wrappedLogger.errorAndThrow (/usr/local/lib/node_modules/appium/node_modules/appium-support/lib/logging.js:78:13)
[Chromedriver] at errorAndThrow (/usr/local/lib/node_modules/appium/node_modules/appium-chromedriver/lib/chromedriver.js:499:13)
[debug] [WD Proxy] Matched ‘/session’ to command name ‘createSession’
[debug] [WD Proxy] Proxying [POST /session] to [POST http://127.0.0.1:8000/wd/hub/session] with body: {“desiredCapabilities”:{“chromeOptions”:{“androidPackage”:“com.my11circle.android”,“androidUseRunningApp”:true,“androidDeviceSerial”:“349c0ada”},“loggingPrefs”:{“browser”:“ALL”}}}
[debug] [WD Proxy] Got response with status 200: {“sessionId”:“049d450c481a1bbe3f25440807325d7e”,“status”:13,“value”:{“message”:“unknown error: Failed to get PID for the following process: com.my11circle.android\n (process name must be specified if not equal to package name)\n (Driver info: chromedriver=76.0.3809.68 (420c9498db8ce8fcd190a954d51297672c1515d5-refs/branch-heads/[email protected]{#864}),platform=Mac OS X 10.13.4 x86_64)”}}