Automate chrome browser on emulator having issue

Whenever I try to automate chrome browser on emulator it is launching chrome browser and then immediately setting the udid to null and saying device not found. Not sure why it is happening. Check below logs

C:\Users<user>>appium --allow-insecure chromedriver_autodownload
[Appium] Welcome to Appium v2.11.2
[Appium] Non-default server args:
[Appium] {
allowInsecure: [
‘chromedriver_autodownload’
]
}
[Appium] The autodetected Appium home path: C:\Users<user>.appium
[Appium] Attempting to load driver uiautomator2…
[Appium] Attempting to load driver espresso…
[Appium] Attempting to load driver windows…
[Appium] Requiring driver at C:\Users<user>.appium\node_modules\appium-windows-driver\build\index.js
[Appium] Requiring driver at C:\Users<user>.appium\node_modules\appium-uiautomator2-driver\build\index.js
[Appium] Requiring driver at C:\Users<user>.appium\node_modules\appium-espresso-driver\build\index.js
[Appium] WindowsDriver has been successfully loaded in 1.256s
[Appium] AndroidUiautomator2Driver has been successfully loaded in 1.258s
[Appium] EspressoDriver has been successfully loaded in 1.258s
[Appium] Attempting to load driver gecko…
[Appium] Attempting to load driver chromium…
[Appium] Requiring driver at C:\Users<user>.appium\node_modules\appium-geckodriver\build\index.js
[Appium] GeckoDriver has been successfully loaded in 0.058s
[Appium] Requiring driver at C:\Users<user>.appium\node_modules\appium-chromium-driver\index.js
[Appium] ChromiumDriver has been successfully loaded in 0.547s
[Appium] Appium REST http interface listener started on http://0.0.0.0:4723
[Appium] You can provide the following URLs in your client code to connect to this server:
http://127.0.0.1:4723/ (only accessible from the same host)
[Appium] Available drivers:
[Appium] - [email protected] (automationName ‘UiAutomator2’)
[Appium] - [email protected] (automationName ‘Espresso’)
[Appium] - [email protected] (automationName ‘Windows’)
[Appium] - [email protected] (automationName ‘Gecko’)
[Appium] - [email protected] (automationName ‘Chromium’)
[Appium] No plugins have been installed. Use the “appium plugin” command to install the one(s) you want to use.
[HTTP] Request idempotency key: 8114c147-f675-42b2-8c88-eacfcc2b9a64
[HTTP] → POST /session {“capabilities”:{“firstMatch”:[{}],“alwaysMatch”:{“platformName”:“ANDROID”,“browserName”:“chrome”,“appium:deviceName”:“pixel_6a”,“appium:automationName”:“UiAutomator2”,“appium:udid”:“emulator-5554”}}}
[AppiumDriver@0d7d] Calling AppiumDriver.createSession() with args: [null,null,{“firstMatch”:[{}],“alwaysMatch”:{“platformName”:“ANDROID”,“browserName”:“chrome”,“appium:deviceName”:“pixel_6a”,“appium:automationName”:“UiAutomator2”,“appium:udid”:“emulator-5554”}}]
[AppiumDriver@0d7d] Event ‘newSessionRequested’ logged at 1727949501762 (15:28:21 GMT+0530 (India Standard Time))
[Appium] Attempting to find matching driver for automationName ‘UiAutomator2’ and platformName ‘ANDROID’
[Appium] The ‘uiautomator2’ driver was installed and matched caps.
[Appium] Will require it at C:\Users<user>.appium\node_modules\appium-uiautomator2-driver
[Appium] Requiring driver at C:\Users<user>.appium\node_modules\appium-uiautomator2-driver\build\index.js
[AppiumDriver@0d7d] Appium v2.11.2 creating new AndroidUiautomator2Driver (v3.7.9) session
[AppiumDriver@0d7d] Checking BaseDriver versions for Appium and AndroidUiautomator2Driver
[AppiumDriver@0d7d] Appium’s BaseDriver version is 9.11.2
[AppiumDriver@0d7d] AndroidUiautomator2Driver’s BaseDriver version is 9.11.2
[AppiumDriver@0d7d] Explicitly enabling use of insecure features:
[AppiumDriver@0d7d] chromedriver_autodownload
[AndroidUiautomator2Driver@ac40] undefined
[AndroidUiautomator2Driver@ac40] Creating session with W3C capabilities: {
“alwaysMatch”: {
“platformName”: “ANDROID”,
“browserName”: “chrome”,
“appium:deviceName”: “pixel_6a”,
“appium:automationName”: “UiAutomator2”,
“appium:udid”: “emulator-5554”
},
“firstMatch”: [
{}
]
}
[686a1456][AndroidUiautomator2Driver@ac40] Session created with session id: 686a1456-c246-4403-ac57-54f4903eb1dd
[686a1456][ADB] Found 1 ‘build-tools’ folders under ‘C:\Users<user>\AppData\Local\Android\Sdk’ (newest first):
[686a1456][ADB] C:\Users<user>\AppData\Local\Android\Sdk\build-tools\34.0.0
[686a1456][ADB] Using ‘adb.exe’ from ‘C:\Users<user>\AppData\Local\Android\Sdk\platform-tools\adb.exe’
[686a1456][ADB] Running ‘C:\Users<user>\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 start-server’
[686a1456][AndroidUiautomator2Driver@ac40] Retrieving device list
[686a1456][ADB] Trying to find connected Android devices
[686a1456][ADB] Getting connected devices
[686a1456][ADB] Connected devices: [{“udid”:“emulator-5554”,“state”:“device”}]
[686a1456][AndroidUiautomator2Driver@ac40] Using device: emulator-5554
[686a1456][ADB] Using ‘adb.exe’ from ‘C:\Users<user>\AppData\Local\Android\Sdk\platform-tools\adb.exe’
[686a1456][ADB] Running ‘C:\Users<user>\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 start-server’
[686a1456][ADB] Setting device id to emulator-5554
[686a1456][AndroidUiautomator2Driver@ac40] We’re going to run a Chrome-based session
[686a1456][ADB] Running ‘C:\Users<user>\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 shell getprop ro.build.version.sdk’
[686a1456][ADB] Current device property ‘ro.build.version.sdk’: 34
[686a1456][ADB] Getting device platform version
[686a1456][ADB] Running ‘C:\Users<user>\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 shell getprop ro.build.version.release’
[686a1456][ADB] Current device property ‘ro.build.version.release’: 14
[686a1456][ADB] Device API level: 34
[686a1456][ADB] Running ‘C:\Users<user>\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 shell cmd package resolve-activity --brief com.android.chrome’
[686a1456][AndroidUiautomator2Driver@ac40] Chrome-type package and activity are com.android.chrome and com.android.chrome/com.google.android.apps.chrome.Main
[686a1456][AndroidUiautomator2Driver@ac40] Starting ‘com.android.chrome’ directly on the device
[686a1456][AndroidUiautomator2Driver@ac40] Relaxing hidden api policy
[686a1456][ADB] Running ‘C:\Users<user>\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 shell ‘settings put global hidden_api_policy_pre_p_apps 1;settings put global hidden_api_policy_p_apps 1;settings put global hidden_api_policy 1’’
[686a1456][AndroidUiautomator2Driver@ac40] No app sent in, not parsing package/activity
[686a1456][ADB] Running ‘C:\Users<user>\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 wait-for-device’
[686a1456][ADB] Running ‘C:\Users<user>\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 shell echo ping’
[686a1456][AndroidUiautomator2Driver@ac40] Pushing settings apk to the device…
[686a1456][ADB] Getting package info for ‘io.appium.settings’
[686a1456][ADB] Running ‘C:\Users<user>\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 shell dumpsys package io.appium.settings’
[686a1456][ADB] Using ‘aapt2.exe’ from ‘C:\Users<user>\AppData\Local\Android\Sdk\build-tools\34.0.0\aapt2.exe’
[686a1456][ADB] Reading package manifest: ‘C:\Users\\AppData\Local\Android\Sdk\build-tools\34.0.0\aapt2.exe dump badging C:\Users\\.appium\node_modules\appium-uiautomator2-driver\node_modules\io.appium.settings\apks\settings_apk-debug.apk’
[686a1456][ADB] The version name of the installed ‘io.appium.settings’ is greater or equal to the application version name (‘5.12.13’ >= ‘5.12.13’)
[686a1456][ADB] There is no need to install/upgrade ‘C:\Users<user>.appium\node_modules\appium-uiautomator2-driver\node_modules\io.appium.settings\apks\settings_apk-debug.apk’
[686a1456][ADB] Running ‘C:\Users<user>\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 shell dumpsys activity services io.appium.settings’
[686a1456][AndroidUiautomator2Driver@ac40] io.appium.settings is already running. There is no need to reset its permissions.
[686a1456][Logcat] Starting logs capture with command: C:\Users\\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 logcat -v threadtime
[686a1456][AndroidUiautomator2Driver@ac40] Forwarding UiAutomator2 Server port 6790 to local port 8200
[686a1456][ADB] Forwarding system: 8200 to device: 6790
[686a1456][ADB] Running ‘C:\Users<user>\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 forward tcp:8200 tcp:6790’
[686a1456][ADB] Getting package info for ‘io.appium.uiautomator2.server’
[686a1456][ADB] Running ‘C:\Users<user>\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 shell dumpsys package io.appium.uiautomator2.server’
[686a1456][ADB] Getting install status for io.appium.uiautomator2.server.test
[686a1456][AndroidUiautomator2Driver@ac40] No app capability. Assuming it is already on the device
[686a1456][ADB] Getting install status for com.android.chrome
[686a1456][ADB] Running ‘C:\Users<user>\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 shell cmd package list packages’
[686a1456][ADB] Running ‘C:\Users<user>\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 shell cmd package list packages’
[686a1456][ADB] ‘io.appium.uiautomator2.server.test’ is installed
[686a1456][ADB] Reading package manifest: ‘C:\Users\\AppData\Local\Android\Sdk\build-tools\34.0.0\aapt2.exe dump badging C:\Users\\.appium\node_modules\appium-uiautomator2-driver\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-v7.0.24.apk’
[686a1456][ADB] ‘com.android.chrome’ is installed
[686a1456][ADB] Running ‘C:\Users<user>\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 shell am force-stop com.android.chrome’
[686a1456][ADB] The version name of the installed ‘io.appium.uiautomator2.server’ is greater or equal to the application version name (‘7.0.24’ >= ‘7.0.24’)
[686a1456][AndroidUiautomator2Driver@ac40] Server packages status: [{“installState”:“sameVersionInstalled”,“appPath”:“C:\Users\\.appium\node_modules\appium-uiautomator2-driver\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-v7.0.24.apk”,“appId”:“io.appium.uiautomator2.server”},{“installState”:“sameVersionInstalled”,“appPath”:“C:\Users\\.appium\node_modules\appium-uiautomator2-driver\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-debug-androidTest.apk”,“appId”:“io.appium.uiautomator2.server.test”}]
[686a1456][AndroidUiautomator2Driver@ac40] Server packages are not going to be (re)installed
[686a1456][AndroidUiautomator2Driver@ac40] Waiting up to 30000ms for services to be available
[686a1456][ADB] Running ‘C:\Users<user>\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 shell pm list instrumentation’
[686a1456][ADB] Running ‘C:\Users<user>\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 shell pm clear com.android.chrome’
[686a1456][AndroidUiautomator2Driver@ac40] Instrumentation target ‘io.appium.uiautomator2.server.test/androidx.test.runner.AndroidJUnitRunner’ is available
[686a1456][ADB] Adding packages [“io.appium.settings”,“io.appium.uiautomator2.server”,“io.appium.uiautomator2.server.test”] to Doze whitelist
[686a1456][ADB] Got the following command chunks to execute: [[“dumpsys”,“deviceidle”,“whitelist”,“+io.appium.settings”,“;”,“dumpsys”,“deviceidle”,“whitelist”,“+io.appium.uiautomator2.server”,“;”,“dumpsys”,“deviceidle”,“whitelist”,“+io.appium.uiautomator2.server.test”,“;”]]
[686a1456][ADB] Running ‘C:\Users<user>\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 shell dumpsys deviceidle whitelist +io.appium.settings ; dumpsys deviceidle whitelist +io.appium.uiautomator2.server ; dumpsys deviceidle whitelist +io.appium.uiautomator2.server.test ;’
[686a1456][AndroidUiautomator2Driver@ac40] Performed fast reset on the installed ‘com.android.chrome’ application (stop and clear)
[686a1456][AndroidUiautomator2Driver@ac40] Performing shallow cleanup of automation leftovers
[686a1456][AndroidUiautomator2Driver@ac40] No obsolete sessions have been detected (socket hang up)
[686a1456][ADB] Running ‘C:\Users<user>\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 shell am force-stop io.appium.uiautomator2.server’
[686a1456][ADB] Running ‘C:\Users<user>\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 shell am force-stop io.appium.uiautomator2.server.test’
[686a1456][AndroidUiautomator2Driver@ac40] Starting UIAutomator2 server 7.0.24
[686a1456][AndroidUiautomator2Driver@ac40] Using UIAutomator2 server from ‘C:\Users<user>.appium\node_modules\appium-uiautomator2-driver\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-v7.0.24.apk’ and test from ‘C:\Users<user>.appium\node_modules\appium-uiautomator2-driver\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-debug-androidTest.apk’
[686a1456][AndroidUiautomator2Driver@ac40] Waiting up to 30000ms for UiAutomator2 to be online…
[686a1456][ADB] Creating ADB subprocess with args: [“-P”,“5037”,“-s”,“emulator-5554”,“shell”,“am”,“instrument”,“-w”,“-e”,“disableAnalytics”,“true”,“io.appium.uiautomator2.server.test/androidx.test.runner.AndroidJUnitRunner”]
[686a1456][AndroidUiautomator2Driver@ac40] Matched ‘/status’ to command name ‘getStatus’
[686a1456][AndroidUiautomator2Driver@ac40] Proxying [GET /status] to [GET http://127.0.0.1:8200/status] with no body
[686a1456][AndroidUiautomator2Driver@ac40] socket hang up
[686a1456][AndroidUiautomator2Driver@ac40] Matched ‘/status’ to command name ‘getStatus’
[686a1456][AndroidUiautomator2Driver@ac40] Proxying [GET /status] to [GET http://127.0.0.1:8200/status] with no body
[686a1456][AndroidUiautomator2Driver@ac40] socket hang up
[686a1456][AndroidUiautomator2Driver@ac40] [Instrumentation]
[686a1456][AndroidUiautomator2Driver@ac40] Matched ‘/status’ to command name ‘getStatus’
[686a1456][AndroidUiautomator2Driver@ac40] Proxying [GET /status] to [GET http://127.0.0.1:8200/status] with no body
[686a1456][AndroidUiautomator2Driver@ac40] socket hang up
[686a1456][AndroidUiautomator2Driver@ac40] Matched ‘/status’ to command name ‘getStatus’
[686a1456][AndroidUiautomator2Driver@ac40] Proxying [GET /status] to [GET http://127.0.0.1:8200/status] with no body
[686a1456][AndroidUiautomator2Driver@ac40] socket hang up
[686a1456][AndroidUiautomator2Driver@ac40] Matched ‘/status’ to command name ‘getStatus’
[686a1456][AndroidUiautomator2Driver@ac40] Proxying [GET /status] to [GET http://127.0.0.1:8200/status] with no body
[686a1456][AndroidUiautomator2Driver@ac40] Got response with status 200: {“sessionId”:“None”,“value”:{“message”:“UiAutomator2 Server is ready to accept commands”,“ready”:true}}
[686a1456][AndroidUiautomator2Driver@ac40] The initialization of the instrumentation process took 4402ms
[686a1456][AndroidUiautomator2Driver@ac40] Matched ‘/session’ to command name ‘createSession’
[686a1456][AndroidUiautomator2Driver@ac40] Proxying [POST /session] to [POST http://127.0.0.1:8200/session] with body: {“capabilities”:{“firstMatch”:[{“platformName”:“ANDROID”,“browserName”:“chrome”,“deviceName”:“emulator-5554”,“automationName”:“UiAutomator2”,“udid”:“emulator-5554”,“platform”:“LINUX”,“webStorageEnabled”:false,“takesScreenshot”:true,“javascriptEnabled”:true,“databaseEnabled”:false,“networkConnectionEnabled”:true,“locationContextEnabled”:false,“warnings”:{},“desired”:{“platformName”:“ANDROID”,“browserName”:“chrome”,“deviceName”:“pixel_6a”,“automationName”:“UiAutomator2”,“udid”:“emulator-5554”,“appPackage”:“com.android.chrome”,“appActivity”:“com.android.chrome/com.google.android.apps.chrome.Main”},“deviceUDID”:“emulator-5554”}],“alwaysMatch”:{}}}
[686a1456][AndroidUiautomator2Driver@ac40] Got response with status 200: {“sessionId”:“ad0cc3be-41f6-4223-a6e6-6be378fd5b3f”,“value”:{“capabilities”:{“firstMatch”:[{“platformName”:“ANDROID”,“browserName”:“chrome”,“deviceName”:“emulator-5554”,“automationName”:“UiAutomator2”,“udid”:“emulator-5554”,“platform”:“LINUX”,“webStorageEnabled”:false,“takesScreenshot”:true,“javascriptEnabled”:true,“databaseEnabled”:false,“networkConnectionEnabled”:true,“locationContextEnabled”:false,“warnings”:{},“desired”:{“platformName”:“ANDROID”,“browserName”:“chrome”,“deviceName”:“pixel_6a”,“automationName”:“UiAutomator2”,“udid”:“emulator-5554”,“appPackage”:“com.android.chrome”,“appActivity”:“com.android.chrome/com.google.android.apps.chrome.Main”},“deviceUDID”:“emulator-5554”}],“alwaysMatch”:{}},“sessionId”:“ad0cc3be-41f6-4223-a6e6-6be378fd5b3f”}}
[686a1456][AndroidUiautomator2Driver@ac40] Determined the downstream protocol as ‘W3C’
[686a1456][AndroidUiautomator2Driver@ac40] Proxying [GET /appium/device/pixel_ratio] to [GET http://127.0.0.1:8200/session/ad0cc3be-41f6-4223-a6e6-6be378fd5b3f/appium/device/pixel_ratio] with no body
[686a1456][AndroidUiautomator2Driver@ac40] Matched ‘/appium/device/system_bars’ to command name ‘getSystemBars’
[686a1456][AndroidUiautomator2Driver@ac40] Proxying [GET /appium/device/system_bars] to [GET http://127.0.0.1:8200/session/ad0cc3be-41f6-4223-a6e6-6be378fd5b3f/appium/device/system_bars] with no body
[686a1456][AndroidUiautomator2Driver@ac40] Matched ‘/window/current/size’ to command name ‘getWindowSize’
[686a1456][AndroidUiautomator2Driver@ac40] Proxying [GET /window/current/size] to [GET http://127.0.0.1:8200/session/ad0cc3be-41f6-4223-a6e6-6be378fd5b3f/window/current/size] with no body
[686a1456][AndroidUiautomator2Driver@ac40] Proxying [GET /appium/device/info] to [GET http://127.0.0.1:8200/session/ad0cc3be-41f6-4223-a6e6-6be378fd5b3f/appium/device/info] with no body
[686a1456][ADB] Running ‘C:\Users<user>\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 shell dumpsys window’
[686a1456][ADB] Running ‘C:\Users<user>\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 shell dumpsys power’
[686a1456][AndroidUiautomator2Driver@ac40] Got response with status 200: {“sessionId”:“ad0cc3be-41f6-4223-a6e6-6be378fd5b3f”,“value”:2.625}
[686a1456][AndroidUiautomator2Driver@ac40] Got response with status 200: {“sessionId”:“ad0cc3be-41f6-4223-a6e6-6be378fd5b3f”,“value”:{“height”:2400,“width”:1080}}
[686a1456][AndroidUiautomator2Driver@ac40] Got response with status 200: {“sessionId”:“ad0cc3be-41f6-4223-a6e6-6be378fd5b3f”,“value”:{“statusBar”:63}}
[686a1456][AndroidUiautomator2Driver@ac40] Got response with status 200: {“sessionId”:“ad0cc3be-41f6-4223-a6e6-6be378fd5b3f”,“value”:{“androidId”:“550124dbea767dd4”,“apiVersion”:“34”,“bluetooth”:{“state”:“ON”},“brand”:“google”,“carrierName”:“T-Mobile”,“displayDensity”:420,“locale”:“en_US”,“manufacturer”:“Google”,“model”:“sdk_gphone64_x86_64”,“networks”:[{“capabilities”:{“SSID”:null,“linkDownBandwidthKbps”:30000,“linkUpstreamBandwidthKbps”:12000,“networkCapabilities”:“NET_CAPABILITY_NOT_METERED,NET_CAPABILITY_INTERNET,NET_CAPABILITY_NOT_RESTRICTED,NET_CAPABILITY_TRUSTED,NET_CAPABILITY_NOT_VPN,NET_CAPABILITY_VALIDATED,NET_CAPABILITY_NOT_ROAMING,NET_CAPABILITY_FOREGROUND,NET_CAPABILITY_NOT_CONGESTED,NET_CAPABILITY_NOT_SUSPENDED”,“signalStrength”:-50,“transportTypes”:“TRANSPORT_WIFI”},“detailedState”:“CONNECTED”,“extraInfo”:“”,“isAvailable”:true,“isConnected”:true,“isFailover”:false,“isRoaming”:false,“state”:“CONNECTED”,“subtype”:-1,“subtypeName”:“”,“type”:1,“typeName”:“WIFI”},{“capabilities”:{“SSID”:null,“linkDownBandwidthKbps”:4300,“linkUpstreamBandwidthKbps”:1800,“networkCapabil…
[686a1456][AndroidUiautomator2Driver@ac40] Screen already unlocked, doing nothing
[686a1456][AndroidUiautomator2Driver@ac40] Starting a chrome-based browser session
[686a1456][AndroidUiautomator2Driver@ac40] A port was not given, using random free port: 56063
[686a1456][AndroidUiautomator2Driver@ac40] Precalculated Chromedriver capabilities: {
“androidPackage”: “com.android.chrome”,
“androidDeviceSerial”: “emulator-5554”
}
[686a1456][AndroidUiautomator2Driver@ac40] Before starting chromedriver, androidPackage is ‘com.android.chrome’
[686a1456][Chromedriver@cd8e] Changed state to ‘starting’
[686a1456][Chromedriver@cd8e] Using the static Chromedriver->Chrome mapping
[686a1456][Chromedriver@cd8e] The most recent known Chrome version: 128.0.6613
[686a1456][Chromedriver@cd8e] Found 2 executables in ‘C:\Users<user>.appium\node_modules\appium-uiautomator2-driver\node_modules\appium-chromedriver\chromedriver\win’
[686a1456][Chromedriver@cd8e] The following Chromedriver executables were found:
[686a1456][Chromedriver@cd8e] ‘C:\Users<user>.appium\node_modules\appium-uiautomator2-driver\node_modules\appium-chromedriver\chromedriver\win\chromedriver.exe’ (version ‘124.0.6367.0’, minimum Chrome version ‘124’)
[686a1456][Chromedriver@cd8e] ‘C:\Users<user>.appium\node_modules\appium-uiautomator2-driver\node_modules\appium-chromedriver\chromedriver\win\chromedriver_win32_v103.0.5060.134.exe’ (version ‘103.0.5060.134’, minimum Chrome version ‘103.0.5060’)
[686a1456][Chromedriver@cd8e] Found 1 Chromedriver, which is missing in the list of known versions: {“124.0.6367.0”:“124”}
[686a1456][Chromedriver@cd8e] No mapping path provided
[686a1456][ADB] Getting package info for ‘com.android.chrome’
[686a1456][ADB] Running ‘C:\Users<user>\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 shell dumpsys package com.android.chrome’
[686a1456][Chromedriver@cd8e] Found Chrome bundle ‘com.android.chrome’ version ‘124.0.6367’
[686a1456][Chromedriver@cd8e] Found 1 executable capable of automating Chrome ‘124.0.6367’.
Choosing the most recent, ‘C:\Users<user>.appium\node_modules\appium-uiautomator2-driver\node_modules\appium-chromedriver\chromedriver\win\chromedriver.exe’.
[686a1456][Chromedriver@cd8e] If a specific version is required, specify it with the chromedriverExecutabledesired capability.
[686a1456][Chromedriver@cd8e] Set chromedriver binary as: C:\Users<user>.appium\node_modules\appium-uiautomator2-driver\node_modules\appium-chromedriver\chromedriver\win\chromedriver.exe
[686a1456][Chromedriver@cd8e] Killing any old chromedrivers, running: wmic process where “commandline like ‘%chromedriver.exe%–port=56063%’” delete
[686a1456][Chromedriver@cd8e] Successfully cleaned up old chromedrivers
[686a1456][Chromedriver@cd8e] Cleaning this device’s adb forwarded port socket connections: emulator-5554
[686a1456][ADB] List forwarding ports
[686a1456][ADB] Running ‘C:\Users<user>\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 forward --list’
[686a1456][Chromedriver@cd8e] Spawning chromedriver with: C:\Users<user>.appium\node_modules\appium-uiautomator2-driver\node_modules\appium-chromedriver\chromedriver\win\chromedriver.exe --port=56063 --adb-port=5037 --verbose
[686a1456][Chromedriver@cd8e] ChromeDriver version: ‘124.0.6367.0’
[686a1456][Chromedriver@cd8e] Set ChromeDriver communication protocol to W3C
[686a1456][Chromedriver@cd8e] Matched ‘/status’ to command name ‘getStatus’
[686a1456][Chromedriver@cd8e] Proxying [GET /status] to [GET http://127.0.0.1:56063/status] with no body
[686a1456][Chromedriver@cd8e] connect ECONNREFUSED 127.0.0.1:56063
[686a1456][Chromedriver@cd8e] Matched ‘/status’ to command name ‘getStatus’
[686a1456][Chromedriver@cd8e] Proxying [GET /status] to [GET http://127.0.0.1:56063/status] with no body
[686a1456][Chromedriver@cd8e] Got response with status 200: {“value”:{“build”:{“version”:“124.0.6367.0 (e115223459bbd8f3349e0080592cb4482994bfc3-refs/branch-heads/6367@{#1})”},“message”:“ChromeDriver ready for new sessions.”,“os”:{“arch”:“x86_64”,“name”:“Windows NT”,“version”:“10.0.19045”},“ready”:true}}
[686a1456][Chromedriver@cd8e] Starting W3C Chromedriver session with capabilities: {
“capabilities”: {
“alwaysMatch”: {
“goog:chromeOptions”: {
“androidPackage”: “com.android.chrome”,
“androidDeviceSerial”: “emulator-5554”
},
“goog:loggingPrefs”: {
“browser”: “ALL”
}
}
}
}
[686a1456][Chromedriver@cd8e] Matched ‘/session’ to command name ‘createSession’
[686a1456][Chromedriver@cd8e] Proxying [POST /session] to [POST http://127.0.0.1:56063/session] with body: {“capabilities”:{“alwaysMatch”:{“goog:chromeOptions”:{“androidPackage”:“com.android.chrome”,“androidDeviceSerial”:“emulator-5554”},“goog:loggingPrefs”:{“browser”:“ALL”}}}}
[686a1456][Chromedriver@cd8e] Webview version: ‘Chrome/124.0.6367.82’
[686a1456][Chromedriver@cd8e] Got response with status 200: {“value”:{“capabilities”:{“acceptInsecureCerts”:false,“browserName”:“chrome”,“browserVersion”:“124.0.6367.82”,“chrome”:{“chromedriverVersion”:“124.0.6367.0 (e115223459bbd8f3349e0080592cb4482994bfc3-refs/branch-heads/6367@{#1})”},“fedcm:accounts”:true,“goog:chromeOptions”:{“debuggerAddress”:“localhost:56142”},“pageLoadStrategy”:“normal”,“platformName”:“android”,“proxy”:{},“setWindowRect”:false,“strictFileInteractability”:false,“timeouts”:{“implicit”:0,“pageLoad”:300000,“script”:30000},“unhandledPromptBehavior”:“dismiss and notify”,“webauthn:extension:credBlob”:false,“webauthn:extension:largeBlob”:false,“webauthn:extension:minPinLength”:false,“webauthn:extension:prf”:false,“webauthn:virtualAuthenticators”:false},“sessionId”:“8306a0a8c309f06f98e993fdf37ef937”}}
[686a1456][Chromedriver@cd8e] Determined the downstream protocol as ‘W3C’
[686a1456][Chromedriver@cd8e] Changed state to ‘online’
[686a1456][AppiumDriver@0d7d] New AndroidUiautomator2Driver session created successfully, session 686a1456-c246-4403-ac57-54f4903eb1dd added to master session list
[686a1456][AppiumDriver@0d7d] Event ‘newSessionStarted’ logged at 1727949513902 (15:28:33 GMT+0530 (India Standard Time))
[686a1456][AndroidUiautomator2Driver@ac40] Cached the protocol value ‘W3C’ for the new session 686a1456-c246-4403-ac57-54f4903eb1dd
[686a1456][AndroidUiautomator2Driver@ac40] Responding to client with driver.createSession() result: {“capabilities”:{“platformName”:“ANDROID”,“browserName”:“chrome”,“deviceName”:“emulator-5554”,“automationName”:“UiAutomator2”,“udid”:“emulator-5554”,“platform”:“LINUX”,“webStorageEnabled”:false,“takesScreenshot”:true,“javascriptEnabled”:true,“databaseEnabled”:false,“networkConnectionEnabled”:true,“locationContextEnabled”:false,“warnings”:{},“desired”:{“platformName”:“ANDROID”,“browserName”:“chrome”,“deviceName”:“pixel_6a”,“automationName”:“UiAutomator2”,“udid”:“emulator-5554”,“appPackage”:“com.android.chrome”,“appActivity”:“com.android.chrome/com.google.android.apps.chrome.Main”},“deviceUDID”:“emulator-5554”,“pixelRatio”:“2.625”,“statBarHeight”:63,“viewportRect”:{“left”:0,“top”:63,“width”:1080,“height”:2337},“deviceApiLevel”:34,“platformVersion”:“14”,“deviceManufacturer”:“Google”,“deviceModel”:“sdk_gphone64_x86_64”,“deviceScreenSize”:“1080x2400”,“deviceScreenDensity”:420}}
[686a1456][HTTP] ← POST /session 200 12146 ms - 946
[HTTP] Request idempotency key: 3fa125e2-38f5-4621-8bcb-737e02043218
[HTTP] → POST /session {“capabilities”:{“firstMatch”:[{}],“alwaysMatch”:{“platformName”:“ANDROID”,“browserName”:“chrome”,“appium:deviceName”:“OnePlus”,“appium:automationName”:“UiAutomator2”,“appium:udid”:”<enter_device_udid_here>>“}}}
[AppiumDriver@0d7d] Calling AppiumDriver.createSession() with args: [null,null,{“firstMatch”:[{}],“alwaysMatch”:{“platformName”:“ANDROID”,“browserName”:“chrome”,“appium:deviceName”:“OnePlus”,“appium:automationName”:“UiAutomator2”,“appium:udid”:”<enter_device_udid_here>>"}}]
[AppiumDriver@0d7d] Event ‘newSessionRequested’ logged at 1727949514633 (15:28:34 GMT+0530 (India Standard Time))
[Appium] Attempting to find matching driver for automationName ‘UiAutomator2’ and platformName ‘ANDROID’
[Appium] The ‘uiautomator2’ driver was installed and matched caps.
[Appium] Will require it at C:\Users<user>.appium\node_modules\appium-uiautomator2-driver
[Appium] Requiring driver at C:\Users<user>.appium\node_modules\appium-uiautomator2-driver\build\index.js
[AppiumDriver@0d7d] Appium v2.11.2 creating new AndroidUiautomator2Driver (v3.7.9) session
[AppiumDriver@0d7d] Checking BaseDriver versions for Appium and AndroidUiautomator2Driver
[AppiumDriver@0d7d] Appium’s BaseDriver version is 9.11.2
[AppiumDriver@0d7d] AndroidUiautomator2Driver’s BaseDriver version is 9.11.2
[AppiumDriver@0d7d] Explicitly enabling use of insecure features:
[AppiumDriver@0d7d] chromedriver_autodownload
[AndroidUiautomator2Driver@7311] undefined
[AndroidUiautomator2Driver@7311] Creating session with W3C capabilities: {
“alwaysMatch”: {
“platformName”: “ANDROID”,
“browserName”: “chrome”,
“appium:deviceName”: “OnePlus”,
“appium:automationName”: “UiAutomator2”,
“appium:udid”: “<enter_device_udid_here>>”
},
“firstMatch”: [
{}
]
}
[6ffc4c7a][AndroidUiautomator2Driver@7311] Session created with session id: 6ffc4c7a-9b4f-40ce-96f8-eadb2dec40e2
[6ffc4c7a][ADB] Using ‘adb.exe’ from ‘C:\Users<user>\AppData\Local\Android\Sdk\platform-tools\adb.exe’
[6ffc4c7a][ADB] Running ‘C:\Users<user>\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 start-server’
[6ffc4c7a][AndroidUiautomator2Driver@7311] Retrieving device list
[6ffc4c7a][ADB] Trying to find connected Android devices
[6ffc4c7a][ADB] Getting connected devices
[6ffc4c7a][ADB] Connected devices: [{“udid”:“emulator-5554”,“state”:“device”}]
[6ffc4c7a][AndroidUiautomator2Driver@7311] [
‘Device <enter_device_udid_here>> was not in the list of connected devices’
]
[6ffc4c7a][AndroidUiautomator2Driver@7311] Deleting UiAutomator2 session
[6ffc4c7a][AppiumDriver@0d7d] Event ‘newSessionStarted’ logged at 1727949514824 (15:28:34 GMT+0530 (India Standard Time))
[6ffc4c7a][AppiumDriver@0d7d] Encountered internal error running command: Error: Device <enter_device_udid_here>> was not in the list of connected devices
at Object.errorWithException (C:\Users<user>\AppData\Roaming\npm\node_modules\appium\node_modules@appium\support\lib\logging.js:41:45)
at Object.errorAndThrow (C:\Users<user>\AppData\Roaming\npm\node_modules\appium\node_modules@appium\support\lib\logging.js:44:18)
at AndroidUiautomator2Driver.getDeviceInfoFromCaps (C:\Users<user>.appium\node_modules\appium-uiautomator2-driver\node_modules\appium-android-driver\lib\commands\device\common.js:42:24)
at AndroidUiautomator2Driver.createSession (C:\Users<user>.appium\node_modules\appium-uiautomator2-driver\lib\driver.ts:365:30)
at AppiumDriver.createSession (C:\Users<user>\AppData\Roaming\npm\node_modules\appium\lib\appium.js:731:35)
[6ffc4c7a][HTTP] ← POST /session 500 218 ms - 716
[686a1456][HTTP] → GET /session/686a1456-c246-4403-ac57-54f4903eb1dd/screenshot {}
[686a1456][AndroidUiautomator2Driver@ac40] Driver proxy active, passing request on via HTTP proxy
[686a1456][Chromedriver@cd8e] Matched ‘/session/686a1456-c246-4403-ac57-54f4903eb1dd/screenshot’ to command name ‘getScreenshot’
[686a1456][Chromedriver@cd8e] Proxying [GET /session/686a1456-c246-4403-ac57-54f4903eb1dd/screenshot] to [GET http://127.0.0.1:56063/session/8306a0a8c309f06f98e993fdf37ef937/screenshot] with no body
[686a1456][Chromedriver@cd8e] Got response with status 200: {“value”:"iVBORw0KGgoAAAANSUhEUgAABDgAAAjiCAYAAACYFTmyAAAAAXNSR0IArs4c6QAAIABJREFUeJzs2EENACAQwDDAv+dDBA+ypFWw9/bMzAIAAAAIO78DAAAAAF4ZHAAAAECewQEAAADkGRwAAABAnsEBAAAA5BkcAAAAQJ7BAQAAAOQZHAAAAECewQEAAADkGRwAAABAnsEBAAAA5BkcAAAAQJ7BAQAAAOQZHAAAAECewQEAAADkGRwAAABAnsEBAAAA5BkcAAAAQJ7BAQAAAOQZHAAAAECewQEAAADkGRwAAABAnsEBAAAA5BkcAAAAQJ7BAQAAAOQZHAAAAECewQEAAADkGRwAAABAnsEBAAAA5BkcAAAAQJ7BAQAAAOQZHAAAAECewQEAAADkGRwAAABAnsEBAAAA5BkcAAAAQJ7BAQAAAOQZHAAAAECewQEAAADkGRwAAABAnsEBAAAA5BkcAAAAQJ7BAQAAAOQZHAAAAECewQEAAADkGRwAAABAnsEBAAAA5BkcAAAAQJ7BAQAAAOQZHAAAAECewQEAAADkGRwAAABAnsEBAAAA5BkcAAAAQJ7BAQAAAOQZHAAAAECewQEAAADkGRwAAABAnsEBAAAA5BkcAAAAQJ7BAQAAAOQZHAAAAECewQEAAADkGRwAAABAnsEBAAAA5BkcAAAAQJ7BAQAAAOQZHAAAAECewQEAAADkGRwAAABAnsEBAAAA5BkcAAAAQJ7BAQAAAOQZHAAAAECewQEAAADkGRwAAABAnsEBAAAA5BkcAAAAQJ7BAQAAAOQZHAAAAECewQEAAADkGRwAAABAnsEBAAAA5BkcAAAAQJ7BAQAAAOQZHAAAAECewQEAAADkGRwAAABAnsEBAAAA5BkcAAAAQJ7BAQAAAOQZHAAAAECewQEAAADkGRwAAABAnsEBAAAA5BkcAAAAQJ7BAQAAAOQZHAAAAECewQEAAADkGRwAAABAnsEBAAAA5BkcAAAAQJ7BAQAAAOQZHAA…
[686a1456][HTTP] ← GET /session/686a1456-c246-4403-ac57-54f4903eb1dd/screenshot 200 10329 ms - 19692
[686a1456][HTTP] → POST /session/686a1456-c246-4403-ac57-54f4903eb1dd/appium/stop_recording_screen {}
[686a1456][AndroidUiautomator2Driver@ac40] Calling AppiumDriver.stopRecordingScreen() with args: [null,“686a1456-c246-4403-ac57-54f4903eb1dd”]
[686a1456][ADB] Getting IDs of all ‘screenrecord’ processes
[686a1456][ADB] Running ‘C:\Users<user>\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 shell ‘pgrep --help; echo $?’’
[686a1456][ADB] Running ‘C:\Users<user>\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 shell pgrep -f ([[:blank:]]|^)screenrecord([[:blank:]]|$)’
[686a1456][AndroidUiautomator2Driver@ac40] Screen recording has not been previously started by Appium. There is nothing to stop
[686a1456][AndroidUiautomator2Driver@ac40] Responding to client with driver.stopRecordingScreen() result: “”
[686a1456][HTTP] ← POST /session/686a1456-c246-4403-ac57-54f4903eb1dd/appium/stop_recording_screen 200 134 ms - 12
[686a1456][HTTP] → DELETE /session/686a1456-c246-4403-ac57-54f4903eb1dd {}
[686a1456][AndroidUiautomator2Driver@ac40] Calling AppiumDriver.deleteSession() with args: [“686a1456-c246-4403-ac57-54f4903eb1dd”]
[686a1456][AppiumDriver@0d7d] Event ‘quitSessionRequested’ logged at 1727949525394 (15:28:45 GMT+0530 (India Standard Time))
[686a1456][AppiumDriver@0d7d] Removing session 686a1456-c246-4403-ac57-54f4903eb1dd from our master session list
[686a1456][AndroidUiautomator2Driver@ac40] Deleting UiAutomator2 session
[686a1456][AndroidUiautomator2Driver@ac40] Stopping chromedriver for context CHROMIUM
[686a1456][Chromedriver@cd8e] Changed state to ‘stopping’
[686a1456][Chromedriver@cd8e] Matched ‘’ to command name ‘deleteSession’
[686a1456][Chromedriver@cd8e] Proxying [DELETE /] to [DELETE http://127.0.0.1:56063/session/8306a0a8c309f06f98e993fdf37ef937] with no body
[686a1456][Chromedriver@cd8e] Got response with status 200: {“value”:null}
[686a1456][Chromedriver@cd8e] Changed state to ‘stopped’
[686a1456][AndroidUiautomator2Driver@ac40] Deleting UiAutomator2 server session
[686a1456][AndroidUiautomator2Driver@ac40] Matched ‘/’ to command name ‘deleteSession’
[686a1456][AndroidUiautomator2Driver@ac40] Proxying [DELETE /] to [DELETE http://127.0.0.1:8200/session/ad0cc3be-41f6-4223-a6e6-6be378fd5b3f] with no body
[686a1456][AndroidUiautomator2Driver@ac40] Got response with status 200: {“sessionId”:“ad0cc3be-41f6-4223-a6e6-6be378fd5b3f”,“value”:null}
[686a1456][AndroidUiautomator2Driver@ac40] [Instrumentation] io.appium.uiautomator2.server.test.AppiumUiAutomator2Server:
[686a1456][AndroidUiautomator2Driver@ac40] [Instrumentation] The process has exited with code null, signal SIGTERM
[686a1456][ADB] Running ‘C:\Users<user>\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 shell dumpsys activity services io.appium.settings/.recorder.RecorderService’
[686a1456][ADB] Removing forwarded port socket connection: 8200
[686a1456][ADB] Running ‘C:\Users<user>\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 forward --remove tcp:8200’
[686a1456][AndroidUiautomator2Driver@ac40] Restoring hidden api policy to the device default configuration
[686a1456][ADB] Running ‘C:\Users<user>\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 shell ‘settings delete global hidden_api_policy_pre_p_apps;settings delete global hidden_api_policy_p_apps;settings delete global hidden_api_policy’’
[686a1456][Logcat] Stopping logcat capture
[686a1456][AppiumDriver@0d7d] Event ‘quitSessionFinished’ logged at 1727949526055 (15:28:46 GMT+0530 (India Standard Time))
[686a1456][AppiumDriver@0d7d] Received response: null
[686a1456][AppiumDriver@0d7d] But deleting session, so not returning
[686a1456][AppiumDriver@0d7d] Responding to client with driver.deleteSession() result: null
[686a1456][HTTP] ← DELETE /session/686a1456-c246-4403-ac57-54f4903eb1dd 200 665 ms - 14