Error Logs:
Mar 06, 2022 7:07:10 PM io.appium.java_client.remote.AppiumCommandExecutor$1 lambda$0
INFO: Detected dialect: W3C
NATIVE_APP
WEBVIEW_org.chromium.webview_shell
Exception in thread “main” io.appium.java_client.NoSuchContextException: An unknown server-side error occurred while processing the command. Original error: No Chromedriver found that can automate Chrome ‘83.0.4103’. You could also try to enable automated chromedrivers download server feature. See https://github.com/appium/appium/blob/master/docs/en/writing-running-appium/web/chromedriver.md for more details
Build info: version: ‘3.141.59’, revision: ‘e82be7d358’, time: ‘2018-11-14T08:17:03’
System info: host: ‘DESKTOP-4U6Q6EG’, ip: ‘192.168.18.160’, os.name: ‘Windows 10’, os.arch: ‘amd64’, os.version: ‘10.0’, java.version: ‘17.0.1’
Driver info: io.appium.java_client.android.AndroidDriver
Capabilities {app: C:\Users\kristine.moreno\ec…, appPackage: com.androidsample.generalstore, automationName: uiautomator2, databaseEnabled: false, desired: {app: C:\Users\kristine.moreno\ec…, automationName: uiautomator2, deviceName: KristineEmulator, platformName: android}, deviceApiLevel: 30, deviceManufacturer: unknown, deviceModel: Android SDK built for x86, deviceName: emulator-5554, deviceScreenDensity: 560, deviceScreenSize: 1440x2880, deviceUDID: emulator-5554, javascriptEnabled: true, locationContextEnabled: false, networkConnectionEnabled: true, pixelRatio: 3.5, platform: LINUX, platformName: Android, platformVersion: 11, statBarHeight: 84, takesScreenshot: true, viewportRect: {height: 2628, left: 0, top: 84, width: 1440}, warnings: {}, webStorageEnabled: false}
Session ID: e430b48b-a138-46e7-a2cc-3432055a585a
at io.appium.java_client.AppiumDriver.context(AppiumDriver.java:232)
at ecommerce_tc_5.main(ecommerce_tc_5.java:85)
Caused by: org.openqa.selenium.WebDriverException: An unknown server-side error occurred while processing the command. Original error: No Chromedriver found that can automate Chrome ‘83.0.4103’. You could also try to enable automated chromedrivers download server feature. See https://github.com/appium/appium/blob/master/docs/en/writing-running-appium/web/chromedriver.md for more details
Build info: version: ‘3.141.59’, revision: ‘e82be7d358’, time: ‘2018-11-14T08:17:03’
System info: host: ‘DESKTOP-4U6Q6EG’, ip: ‘192.168.18.160’, os.name: ‘Windows 10’, os.arch: ‘amd64’, os.version: ‘10.0’, java.version: ‘17.0.1’
Driver info: io.appium.java_client.android.AndroidDriver
Capabilities {app: C:\Users\kristine.moreno\ec…, appPackage: com.androidsample.generalstore, automationName: uiautomator2, databaseEnabled: false, desired: {app: C:\Users\kristine.moreno\ec…, automationName: uiautomator2, deviceName: KristineEmulator, platformName: android}, deviceApiLevel: 30, deviceManufacturer: unknown, deviceModel: Android SDK built for x86, deviceName: emulator-5554, deviceScreenDensity: 560, deviceScreenSize: 1440x2880, deviceUDID: emulator-5554, javascriptEnabled: true, locationContextEnabled: false, networkConnectionEnabled: true, pixelRatio: 3.5, platform: LINUX, platformName: Android, platformVersion: 11, statBarHeight: 84, takesScreenshot: true, viewportRect: {height: 2628, left: 0, top: 84, width: 1440}, warnings: {}, webStorageEnabled: false}
Session ID: e430b48b-a138-46e7-a2cc-3432055a585a
at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:77)
at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.base/java.lang.reflect.Constructor.newInstanceWithCaller(Constructor.java:499)
at java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:480)
at org.openqa.selenium.remote.http.W3CHttpResponseCodec.createException(W3CHttpResponseCodec.java:187)
at org.openqa.selenium.remote.http.W3CHttpResponseCodec.decode(W3CHttpResponseCodec.java:122)
at org.openqa.selenium.remote.http.W3CHttpResponseCodec.decode(W3CHttpResponseCodec.java:49)
at org.openqa.selenium.remote.HttpCommandExecutor.execute(HttpCommandExecutor.java:158)
at io.appium.java_client.remote.AppiumCommandExecutor.execute(AppiumCommandExecutor.java:250)
at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:552)
at io.appium.java_client.DefaultGenericMobileDriver.execute(DefaultGenericMobileDriver.java:41)
at io.appium.java_client.AppiumDriver.execute(AppiumDriver.java:1)
at io.appium.java_client.android.AndroidDriver.execute(AndroidDriver.java:1)
at io.appium.java_client.AppiumDriver.context(AppiumDriver.java:229)
… 1 more
APPIUM LOGS
[HTTP] --> POST /wd/hub/session/e430b48b-a138-46e7-a2cc-3432055a585a/context
[HTTP] {“name”:“WEBVIEW_com.androidsample.generalstore”}
[debug] [W3C (e430b48b)] Calling AppiumDriver.setContext() with args: [“WEBVIEW_com.androidsample.generalstore”,“e430b48b-a138-46e7-a2cc-3432055a585a”]
[debug] [AndroidDriver] Getting a list of available webviews
[debug] [ADB] Running ‘C:\Users\kristine.moreno\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 shell cat /proc/net/unix’
[debug] [AndroidDriver] Parsed 2 active devtools sockets: ["@webview_devtools_remote_15926","@webview_devtools_remote_17911"]
[debug] [AndroidDriver] Collecting CDP data of 2 webviews
[debug] [AndroidDriver] Forwarding remote port webview_devtools_remote_15926 to a local port in range 10900…11000
[debug] [AndroidDriver] You could use the ‘webviewDevtoolsPort’ capability to customize the starting port number
[debug] [AndroidDriver] Forwarding remote port webview_devtools_remote_17911 to a local port in range 10900…11000
[debug] [AndroidDriver] You could use the ‘webviewDevtoolsPort’ capability to customize the starting port number
[debug] [ADB] Running ‘C:\Users\kristine.moreno\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 forward tcp:10900 localabstract:webview_devtools_remote_15926’
[debug] [ADB] Removing forwarded port socket connection: 10900
[debug] [ADB] Running ‘C:\Users\kristine.moreno\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 forward --remove tcp:10900’
[debug] [ADB] Running ‘C:\Users\kristine.moreno\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 forward tcp:10900 localabstract:webview_devtools_remote_17911’
[debug] [ADB] Removing forwarded port socket connection: 10900
[debug] [ADB] Running ‘C:\Users\kristine.moreno\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 forward --remove tcp:10900’
[debug] [AndroidDriver] CDP data collection completed
[debug] [AndroidDriver] WEBVIEW_15926 mapped to pid 15926
[debug] [AndroidDriver] Getting process name for webview ‘WEBVIEW_15926’
[debug] [ADB] Running ‘C:\Users\kristine.moreno\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 shell ps -A’
[debug] [AndroidDriver] Got process name: ‘org.chromium.webview_shell’
[debug] [AndroidDriver] WEBVIEW_17911 mapped to pid 17911
[debug] [AndroidDriver] Getting process name for webview ‘WEBVIEW_17911’
[debug] [ADB] Running ‘C:\Users\kristine.moreno\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 shell ps -A’
[debug] [AndroidDriver] Got process name: ‘com.androidsample.generalstore’
[debug] [AndroidDriver] Found 2 webviews: [“WEBVIEW_org.chromium.webview_shell”,“WEBVIEW_com.androidsample.generalstore”]
[debug] [AndroidDriver] Available contexts: [“NATIVE_APP”,“WEBVIEW_org.chromium.webview_shell”,“WEBVIEW_com.androidsample.generalstore”]
[debug] [AndroidDriver] Connecting to chrome-backed webview context ‘WEBVIEW_com.androidsample.generalstore’
[debug] [AndroidDriver] A port was not given, using random free port: 8000
[debug] [AndroidDriver] Passing web view details to the Chromedriver constructor: {
[debug] [AndroidDriver] “info”: {
[debug] [AndroidDriver] “Android-Package”: “com.androidsample.generalstore”,
[debug] [AndroidDriver] “Browser”: “Chrome/83.0.4103.106”,
[debug] [AndroidDriver] “Protocol-Version”: “1.3”,
[debug] [AndroidDriver] “User-Agent”: “Mozilla/5.0 (Linux; Android 11; Android SDK built for x86 Build/RSR1.210210.001.A1; wv) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/83.0.4103.106 Mobile Safari/537.36”,
[debug] [AndroidDriver] “V8-Version”: “8.3.110.13”,
[debug] [AndroidDriver] “WebKit-Version”: “537.36 (@ce7134bb3d95141cd18f1e65772a4247f282d950)”,
[debug] [AndroidDriver] “webSocketDebuggerUrl”: “ws://127.0.0.1:10900/devtools/browser”
[debug] [AndroidDriver] },
[debug] [AndroidDriver] “process”: {
[debug] [AndroidDriver] “name”: “com.androidsample.generalstore”,
[debug] [AndroidDriver] “id”: “17911”
[debug] [AndroidDriver] }
[debug] [AndroidDriver] }
[debug] [AndroidDriver] Automated Chromedriver download is disabled. Use ‘chromedriver_autodownload’ server feature to enable it
[debug] [AndroidDriver] Precalculated Chromedriver capabilities: {
[debug] [AndroidDriver] “androidPackage”: “com.androidsample.generalstore”,
[debug] [AndroidDriver] “androidUseRunningApp”: true,
[debug] [AndroidDriver] “androidProcess”: “com.androidsample.generalstore”,
[debug] [AndroidDriver] “androidDeviceSerial”: “emulator-5554”
[debug] [AndroidDriver] }
[debug] [AndroidDriver] Before starting chromedriver, androidPackage is ‘com.androidsample.generalstore’
[debug] [Chromedriver] Changed state to ‘starting’
[debug] [Chromedriver] Using the static Chromedriver->Chrome mapping
[debug] [Chromedriver] The most recent known Chrome version: 91.0.4472
[debug] [Chromedriver] Found 0 executables in ‘C:\Users\kristine.moreno\AppData\Roaming\npm\node_modules\appium\node_modules\appium-chromedriver\chromedriver\win’
[Chromedriver] No Chromedrivers were found in ‘C:\Users\kristine.moreno\AppData\Roaming\npm\node_modules\appium\node_modules\appium-chromedriver\chromedriver\win’
[debug] [Chromedriver] Browser version in the supplied details: Chrome/83.0.4103.106
[debug] [Chromedriver] Found Chrome bundle ‘undefined’ version ‘83.0.4103’
[debug] [Chromedriver] Error: No Chromedriver found that can automate Chrome ‘83.0.4103’. You could also try to enable automated chromedrivers download server feature. See https://github.com/appium/appium/blob/master/docs/en/writing-running-appium/web/chromedriver.md for more details
[debug] [Chromedriver] at Chromedriver.getCompatibleChromedriver (C:\Users\kristine.moreno\AppData\Roaming\npm\node_modules\appium\node_modules\appium-chromedriver\lib\chromedriver.js:367:15)
[debug] [Chromedriver] at Chromedriver.initChromedriverPath (C:\Users\kristine.moreno\AppData\Roaming\npm\node_modules\appium\node_modules\appium-chromedriver\lib\chromedriver.js:391:11)
[debug] [Chromedriver] at Chromedriver.start (C:\Users\kristine.moreno\AppData\Roaming\npm\node_modules\appium\node_modules\appium-chromedriver\lib\chromedriver.js:456:7)
[debug] [Chromedriver] at AndroidUiautomator2Driver.setupNewChromedriver (C:\Users\kristine.moreno\AppData\Roaming\npm\node_modules\appium\node_modules\appium-android-driver\lib\commands\context.js:472:3)
[debug] [Chromedriver] at AndroidUiautomator2Driver.startChromedriverProxy (C:\Users\kristine.moreno\AppData\Roaming\npm\node_modules\appium\node_modules\appium-android-driver\lib\commands\context.js:221:10)
[debug] [Chromedriver] at AndroidUiautomator2Driver.switchContext (C:\Users\kristine.moreno\AppData\Roaming\npm\node_modules\appium\node_modules\appium-android-driver\lib\commands\context.js:128:5)
[debug] [Chromedriver] at AndroidUiautomator2Driver.setContext (C:\Users\kristine.moreno\AppData\Roaming\npm\node_modules\appium\node_modules\appium-android-driver\lib\commands\context.js:54:3)[Chromedriver] No Chromedriver found that can automate Chrome ‘83.0.4103’. You could also try to enable automated chromedrivers download server feature. See https://github.com/appium/appium/blob/master/docs/en/writing-running-appium/web/chromedriver.md for more details
[debug] [W3C (e430b48b)] Encountered internal error running command: Error: No Chromedriver found that can automate Chrome ‘83.0.4103’. You could also try to enable automated chromedrivers download server feature. See https://github.com/appium/appium/blob/master/docs/en/writing-running-appium/web/chromedriver.md for more details
[debug] [W3C (e430b48b)] at Object.errorAndThrow (C:\Users\kristine.moreno\AppData\Roaming\npm\node_modules\appium\node_modules\appium-support\lib\logging.js:94:35)
[debug] [W3C (e430b48b)] at Chromedriver.start (C:\Users\kristine.moreno\AppData\Roaming\npm\node_modules\appium\node_modules\appium-chromedriver\lib\chromedriver.js:541:11)
[debug] [W3C (e430b48b)] at AndroidUiautomator2Driver.setupNewChromedriver (C:\Users\kristine.moreno\AppData\Roaming\npm\node_modules\appium\node_modules\appium-android-driver\lib\commands\context.js:472:3)
[debug] [W3C (e430b48b)] at AndroidUiautomator2Driver.startChromedriverProxy (C:\Users\kristine.moreno\AppData\Roaming\npm\node_modules\appium\node_modules\appium-android-driver\lib\commands\context.js:221:10)
[debug] [W3C (e430b48b)] at AndroidUiautomator2Driver.switchContext (C:\Users\kristine.moreno\AppData\Roaming\npm\node_modules\appium\node_modules\appium-android-driver\lib\commands\context.js:128:5)
[debug] [W3C (e430b48b)] at AndroidUiautomator2Driver.setContext (C:\Users\kristine.moreno\AppData\Roaming\npm\node_modules\appium\node_modules\appium-android-driver\lib\commands\context.js:54:3)
[HTTP] <-- POST /wd/hub/session/e430b48b-a138-46e7-a2cc-3432055a585a/context 500 988 ms - 1089
