[info] [Appium] Welcome to Appium v1.21.0
[info] [Appium] Non-default server args:
[info] [Appium]   relaxedSecurityEnabled: true
[info] [Appium]   allowInsecure: {
[info] [Appium]   }
[info] [Appium]   denyInsecure: {
[info] [Appium]   }
[info] [Appium] Appium REST http interface listener started on 0.0.0.0:4723[debug] [HTTP] Request idempotency key: 80165f53-ebb8-4a8d-b3ee-2950cbfd5e70
[info] [HTTP] --> POST /wd/hub/session
[info] [HTTP] {"capabilities":{"firstMatch":[{"platformName":"Android","appium:deviceName":"6f5cca76"}]},"desiredCapabilities":{"platformName":"Android","deviceName":"6f5cca76"}}
[debug] [W3C] Calling AppiumDriver.createSession() with args: [{"platformName":"Android","deviceName":"6f5cca76"},null,{"firstMatch":[{"platformName":"Android","appium:deviceName":"6f5cca76"}]}]
[debug] [BaseDriver] Event 'newSessionRequested' logged at 1625623741032 (10:09:01 GMT+0800 (中国标准时间))
[warn] [Appium] 
[warn] [Appium] ======================================================================
[warn] [Appium]   DEPRECATION WARNING:
[warn] [Appium] 
[warn] [Appium]   The 'automationName' capability was not provided in the desired 
[warn] [Appium]   capabilities for this Android session
[warn] [Appium] 
[warn] [Appium]   Setting 'automationName=UiAutomator2' by default and using the 
[warn] [Appium]   UiAutomator2 Driver
[warn] [Appium] 
[warn] [Appium]   The next major version of Appium (2.x) will **require** the 
[warn] [Appium]   'automationName' capability to be set for all sessions on all 
[warn] [Appium]   platforms
[warn] [Appium] 
[warn] [Appium]   In previous versions (Appium <= 1.13.x), the default was 
[warn] [Appium]   'automationName=UiAutomator1'
[warn] [Appium] 
[warn] [Appium]   If you wish to use that automation instead of UiAutomator2, please 
[warn] [Appium]   add 'automationName=UiAutomator1' to your desired capabilities
[warn] [Appium] 
[warn] [Appium]   For more information about drivers, please visit 
[warn] [Appium]   http://appium.io/docs/en/about-appium/intro/ and explore the 
[warn] [Appium]   'Drivers' menu
[warn] [Appium] 
[warn] [Appium] ======================================================================
[warn] [Appium] 
[info] [Appium] Appium v1.21.0 creating new AndroidUiautomator2Driver (v1.65.0) session
[info] [Appium] Applying relaxed security to 'AndroidUiautomator2Driver' as per server command line argument. All insecure features will be enabled unless explicitly disabled by --deny-insecure
[debug] [BaseDriver] W3C capabilities and MJSONWP desired capabilities were provided
[debug] [BaseDriver] Creating session with W3C capabilities: {
[debug] [BaseDriver]   "alwaysMatch": {
[debug] [BaseDriver]     "platformName": "Android",
[debug] [BaseDriver]     "appium:deviceName": "6f5cca76"
[debug] [BaseDriver]   },
[debug] [BaseDriver]   "firstMatch": [
[debug] [BaseDriver]     {}
[debug] [BaseDriver]   ]
[debug] [BaseDriver] }
[info] [BaseDriver] Session created with session id: e11936e1-7fb2-46a9-af60-3e7535ea248b
[info] [UiAutomator2] Neither 'app' nor 'appPackage' was set. Starting UiAutomator2 without the target application[info] [ADB] Found 1 'build-tools' folders under 'C:\Program Files (x86)\Android\android-sdk' (newest first):
[info] [ADB]     C:/Program Files (x86)/Android/android-sdk/build-tools/29.0.3
[info] [ADB] Using 'adb.exe' from 'C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe'
[debug] [ADB] Running 'C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 start-server'
[info] [AndroidDriver] Retrieving device list
[debug] [ADB] Trying to find a connected android device
[debug] [ADB] Getting connected devices[info] [ADB] Using 'adb.exe' from 'C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe'
[debug] [ADB] Running 'C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 start-server'
[debug] [ADB] Setting device id to 6f5cca76
[debug] [ADB] Running 'C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 -s 6f5cca76 shell getprop ro.build.version.sdk'[debug] [ADB] Current device property 'ro.build.version.sdk': 28
[info] [ADB] Getting device platform version
[debug] [ADB] Running 'C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 -s 6f5cca76 shell getprop ro.build.version.release'
[debug] [ADB] Current device property 'ro.build.version.release': 9
[debug] [ADB] Device API level: 28
[info] [UiAutomator2] Relaxing hidden api policy
[debug] [ADB] Running 'C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 -s 6f5cca76 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''[warn] [AndroidDriver] No app sent in, not parsing package/activity
[debug] [ADB] Running 'C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 -s 6f5cca76 wait-for-device'
[debug] [ADB] Running 'C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 -s 6f5cca76 shell echo ping'[debug] [AndroidDriver] Pushing settings apk to device...
[debug] [ADB] Getting install status for io.appium.settings
[debug] [ADB] Running 'C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 -s 6f5cca76 shell dumpsys package io.appium.settings'[debug] [ADB] 'io.appium.settings' is not installed
[debug] [ADB] App 'C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\io.appium.settings\apks\settings_apk-debug.apk' is not installed
[debug] [ADB] Installing 'C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\io.appium.settings\apks\settings_apk-debug.apk'
[debug] [ADB] Running 'C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 -s 6f5cca76 help'
[debug] [ADB] Running 'C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 -s 6f5cca76 features'
[info] [ADB] The application at 'C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\io.appium.settings\apks\settings_apk-debug.apk' will not be cached, because the device under test has confirmed the support of streamed installs
[debug] [ADB] Running 'C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 -s 6f5cca76 install -g C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\io.appium.settings\apks\settings_apk-debug.apk'[info] [ADB] The installation of 'settings_apk-debug.apk' took 642ms
[debug] [ADB] Install command stdout: Performing Streamed Install
[debug] [ADB] Success
[debug] [ADB] Getting IDs of all 'io.appium.settings' processes
[debug] [ADB] Running 'C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 -s 6f5cca76 shell 'pgrep --help; echo $?''[debug] [ADB] Running 'C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 -s 6f5cca76 shell pgrep -f \(\[\[:blank:\]\]\|\^\)io\.appium\.settings\(\[\[:blank:\]\]\|\$\)'[debug] [ADB] Getting IDs of all 'io.appium.settings' processes
[debug] [ADB] Running 'C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 -s 6f5cca76 shell pgrep -f \(\[\[:blank:\]\]\|\^\)io\.appium\.settings\(\[\[:blank:\]\]\|\$\)'[debug] [ADB] Starting Appium Settings app
[debug] [ADB] Running 'C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 -s 6f5cca76 shell am start -n io.appium.settings/.Settings -a android.intent.action.MAIN -c android.intent.category.LAUNCHER'[debug] [ADB] Getting IDs of all 'io.appium.settings' processes
[debug] [ADB] Running 'C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 -s 6f5cca76 shell pgrep -f \(\[\[:blank:\]\]\|\^\)io\.appium\.settings\(\[\[:blank:\]\]\|\$\)'[debug] [ADB] Getting IDs of all 'io.appium.settings' processes
[debug] [ADB] Running 'C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 -s 6f5cca76 shell pgrep -f \(\[\[:blank:\]\]\|\^\)io\.appium\.settings\(\[\[:blank:\]\]\|\$\)'[debug] [ADB] Running 'C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 -s 6f5cca76 shell appops set io.appium.settings android:mock_location allow'[debug] [Logcat] Starting logs capture with command: 'C:\\Program Files (x86)\\Android\\android-sdk\\platform-tools\\adb.exe' -P 5037 -s 6f5cca76 logcat -v threadtime[debug] [UiAutomator2] Forwarding UiAutomator2 Server port 6790 to local port 8201
[debug] [ADB] Forwarding system: 8201 to device: 6790
[debug] [ADB] Running 'C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 -s 6f5cca76 forward tcp:8201 tcp:6790'
[debug] [ADB] Getting install status for io.appium.uiautomator2.server
[debug] [ADB] Running 'C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 -s 6f5cca76 shell dumpsys package io.appium.uiautomator2.server'[debug] [ADB] 'io.appium.uiautomator2.server' is not installed
[debug] [ADB] App 'C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-v4.21.1.apk' is not installed
[debug] [UiAutomator2] io.appium.uiautomator2.server installation state: notInstalled
[debug] [ADB] Checking app cert for C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-v4.21.1.apk
[info] [ADB] Using 'apksigner.jar' from 'C:\Program Files (x86)\Android\android-sdk\build-tools\29.0.3\lib\apksigner.jar'
[debug] [ADB] Starting apksigner: 'C:\\Program Files\\Java\\jdk1.8.0_171\\bin\\java.exe' -Xmx1024M -Xss1m -jar 'C:\\Program Files (x86)\\Android\\android-sdk\\build-tools\\29.0.3\\lib\\apksigner.jar' verify --print-certs C:\\Users\\Xpeng\\AppData\\Local\\Programs\\Appium\\resources\\app\\node_modules\\appium\\node_modules\\appium-uiautomator2-server\\apks\\appium-uiautomator2-server-v4.21.1.apk[debug] [ADB] apksigner stdout: Signer #1 certificate DN: EMAILADDRESS=android@android.com, CN=Android, OU=Android, O=Android, L=Mountain View, ST=California, C=US
[debug] [ADB] Signer #1 certificate SHA-256 digest: a40da80a59d170caa950cf15c18c454d47a39b26989d8b640ecd745ba71bf5dc
[debug] [ADB] Signer #1 certificate SHA-1 digest: 61ed377e85d386a8dfee6b864bd85b0bfaa5af81
[debug] [ADB] Signer #1 certificate MD5 digest: e89b158e4bcf988ebd09eb83f5378e87
[debug] [ADB] 
[debug] [ADB] sha256 hash did match for 'appium-uiautomator2-server-v4.21.1.apk'
[info] [ADB] 'C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-v4.21.1.apk' is signed with the default certificate
[debug] [ADB] Getting install status for io.appium.uiautomator2.server.test
[debug] [ADB] Running 'C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 -s 6f5cca76 shell dumpsys package io.appium.uiautomator2.server.test'[debug] [ADB] 'io.appium.uiautomator2.server.test' is not installed
[debug] [ADB] Checking app cert for C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-debug-androidTest.apk
[debug] [ADB] Starting apksigner: 'C:\\Program Files\\Java\\jdk1.8.0_171\\bin\\java.exe' -Xmx1024M -Xss1m -jar 'C:\\Program Files (x86)\\Android\\android-sdk\\build-tools\\29.0.3\\lib\\apksigner.jar' verify --print-certs C:\\Users\\Xpeng\\AppData\\Local\\Programs\\Appium\\resources\\app\\node_modules\\appium\\node_modules\\appium-uiautomator2-server\\apks\\appium-uiautomator2-server-debug-androidTest.apk[debug] [ADB] apksigner stdout: Signer #1 certificate DN: EMAILADDRESS=android@android.com, CN=Android, OU=Android, O=Android, L=Mountain View, ST=California, C=US
[debug] [ADB] Signer #1 certificate SHA-256 digest: a40da80a59d170caa950cf15c18c454d47a39b26989d8b640ecd745ba71bf5dc
[debug] [ADB] Signer #1 certificate SHA-1 digest: 61ed377e85d386a8dfee6b864bd85b0bfaa5af81
[debug] [ADB] Signer #1 certificate MD5 digest: e89b158e4bcf988ebd09eb83f5378e87
[debug] [ADB] 
[debug] [ADB] sha256 hash did match for 'appium-uiautomator2-server-debug-androidTest.apk'
[info] [ADB] 'C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-debug-androidTest.apk' is signed with the default certificate
[info] [UiAutomator2] Server packages are going to be (re)installed
[debug] [ADB] Running 'C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 -s 6f5cca76 version'[info] [ADB] The application at 'C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-v4.21.1.apk' will not be cached, because the device under test has confirmed the support of streamed installs
[debug] [ADB] Running 'C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 -s 6f5cca76 install -r C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-v4.21.1.apk'[info] [ADB] The installation of 'appium-uiautomator2-server-v4.21.1.apk' took 512ms
[debug] [ADB] Install command stdout: Performing Streamed Install
[debug] [ADB] Success
[info] [ADB] The application at 'C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-debug-androidTest.apk' will not be cached, because the device under test has confirmed the support of streamed installs
[debug] [ADB] Running 'C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 -s 6f5cca76 install -r C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-debug-androidTest.apk'[info] [ADB] The installation of 'appium-uiautomator2-server-debug-androidTest.apk' took 868ms
[debug] [ADB] Install command stdout: Performing Streamed Install
[debug] [ADB] Success
[debug] [UiAutomator2] Waiting up to 30000ms for services to be available
[debug] [ADB] Running 'C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 -s 6f5cca76 shell pm list instrumentation'[debug] [UiAutomator2] Instrumentation target 'io.appium.uiautomator2.server.test/androidx.test.runner.AndroidJUnitRunner' is available
[info] [ADB] Adding packages ["io.appium.settings","io.appium.uiautomator2.server","io.appium.uiautomator2.server.test"] to Doze whitelist
[debug] [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",";"]]
[debug] [ADB] Running 'C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 -s 6f5cca76 shell dumpsys deviceidle whitelist +io.appium.settings ; dumpsys deviceidle whitelist +io.appium.uiautomator2.server ; dumpsys deviceidle whitelist +io.appium.uiautomator2.server.test ;'[debug] [UiAutomator2] No app capability. Assuming it is already on the device
[debug] [UiAutomator2] Performing shallow cleanup of automation leftovers
[debug] [UiAutomator2] No obsolete sessions have been detected (socket hang up)
[debug] [ADB] Running 'C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 -s 6f5cca76 shell am force-stop io.appium.uiautomator2.server.test'[info] [UiAutomator2] Starting UIAutomator2 server 4.21.1
[info] [UiAutomator2] Using UIAutomator2 server from 'C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-v4.21.1.apk' and test from 'C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-debug-androidTest.apk'
[info] [UiAutomator2] Waiting up to 30000ms for UiAutomator2 to be online...
[debug] [ADB] Creating ADB subprocess with args: ["-P",5037,"-s","6f5cca76","shell","am","instrument","-w","-e","disableAnalytics",true,"io.appium.uiautomator2.server.test/androidx.test.runner.AndroidJUnitRunner"]
[debug] [WD Proxy] Matched '/status' to command name 'getStatus'
[debug] [WD Proxy] Proxying [GET /status] to [GET http://127.0.0.1:8201/wd/hub/status] with no body
[info] [WD Proxy] socket hang up[debug] [WD Proxy] Matched '/status' to command name 'getStatus'
[debug] [WD Proxy] Proxying [GET /status] to [GET http://127.0.0.1:8201/wd/hub/status] with no body
[info] [WD Proxy] socket hang up[debug] [WD Proxy] Matched '/status' to command name 'getStatus'
[debug] [WD Proxy] Proxying [GET /status] to [GET http://127.0.0.1:8201/wd/hub/status] with no body
[info] [WD Proxy] socket hang up[debug] [WD Proxy] Matched '/status' to command name 'getStatus'
[debug] [WD Proxy] Proxying [GET /status] to [GET http://127.0.0.1:8201/wd/hub/status] with no body
[info] [WD Proxy] socket hang up[debug] [Instrumentation] io.appium.uiautomator2.server.test.AppiumUiAutomator2Server:[debug] [WD Proxy] Matched '/status' to command name 'getStatus'
[debug] [WD Proxy] Proxying [GET /status] to [GET http://127.0.0.1:8201/wd/hub/status] with no body
[info] [WD Proxy] socket hang up[debug] [WD Proxy] Matched '/status' to command name 'getStatus'
[debug] [WD Proxy] Proxying [GET /status] to [GET http://127.0.0.1:8201/wd/hub/status] with no body[debug] [WD Proxy] Got response with status 200: {"sessionId":"None","value":{"message":"UiAutomator2 Server is ready to accept commands","ready":true}}
[debug] [UiAutomator2] The initialization of the instrumentation process took 5231ms
[debug] [WD Proxy] Matched '/session' to command name 'createSession'
[debug] [WD Proxy] Proxying [POST /session] to [POST http://127.0.0.1:8201/wd/hub/session] with body: {"capabilities":{"firstMatch":[{"platform":"LINUX","webStorageEnabled":false,"takesScreenshot":true,"javascriptEnabled":true,"databaseEnabled":false,"networkConnectionEnabled":true,"locationContextEnabled":false,"warnings":{},"desired":{"platformName":"Android","deviceName":"6f5cca76"},"platformName":"Android","deviceName":"6f5cca76","deviceUDID":"6f5cca76"}],"alwaysMatch":{}}}
[debug] [WD Proxy] Got response with status 200: {"sessionId":"89de2b56-f696-4590-b08c-568dd20ce025","value":{"capabilities":{"firstMatch":[{"platform":"LINUX","webStorageEnabled":false,"takesScreenshot":true,"javascriptEnabled":true,"databaseEnabled":false,"networkConnectionEnabled":true,"locationContextEnabled":false,"warnings":{},"desired":{"platformName":"Android","deviceName":"6f5cca76"},"platformName":"Android","deviceName":"6f5cca76","deviceUDID":"6f5cca76"}],"alwaysMatch":{}},"sessionId":"89de2b56-f696-4590-b08c-568dd20ce025"}}
[info] [WD Proxy] Determined the downstream protocol as 'W3C'
[debug] [WD Proxy] Proxying [GET /appium/device/info] to [GET http://127.0.0.1:8201/wd/hub/session/89de2b56-f696-4590-b08c-568dd20ce025/appium/device/info] with no body[debug] [WD Proxy] Got response with status 200: {"sessionId":"89de2b56-f696-4590-b08c-568dd20ce025","value":{"androidId":"383f7d5aab0c2a44","apiVersion":"28","bluetooth":{"state":"OFF"},"brand":"XPENG","carrierName":"","displayDensity":160,"locale":"zh_CN","manufacturer":"XiaoPeng","model":"E28","networks":[{"capabilities":{"SSID":null,"linkDownBandwidthKbps":1048576,"linkUpstreamBandwidthKbps":1048576,"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":-65,"transportTypes":"TRANSPORT_WIFI"},"detailedState":"CONNECTED","extraInfo":null,"isAvailable":true,"isConnected":true,"isFailover":false,"isRoaming":false,"state":"CONNECTED","subtype":0,"subtypeName":"","type":1,"typeName":"WIFI"}],"platformVersion":"9","realDisplaySize":"1700x956","timeZone":"Asia/Shanghai"}}
[debug] [ADB] Running 'C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 -s 6f5cca76 shell dumpsys window'[info] [AndroidDriver] Screen already unlocked, doing nothing
[debug] [WD Proxy] Proxying [GET /appium/device/pixel_ratio] to [GET http://127.0.0.1:8201/wd/hub/session/89de2b56-f696-4590-b08c-568dd20ce025/appium/device/pixel_ratio] with no body
[debug] [WD Proxy] Got response with status 200: {"sessionId":"89de2b56-f696-4590-b08c-568dd20ce025","value":1}
[debug] [WD Proxy] Matched '/appium/device/system_bars' to command name 'getSystemBars'
[debug] [WD Proxy] Proxying [GET /appium/device/system_bars] to [GET http://127.0.0.1:8201/wd/hub/session/89de2b56-f696-4590-b08c-568dd20ce025/appium/device/system_bars] with no body
[debug] [WD Proxy] Got response with status 200: {"sessionId":"89de2b56-f696-4590-b08c-568dd20ce025","value":{"statusBar":10}}
[debug] [WD Proxy] Matched '/window/current/size' to command name 'getWindowSize'
[debug] [WD Proxy] Proxying [GET /window/current/size] to [GET http://127.0.0.1:8201/wd/hub/session/89de2b56-f696-4590-b08c-568dd20ce025/window/current/size] with no body[debug] [WD Proxy] Got response with status 200: {"sessionId":"89de2b56-f696-4590-b08c-568dd20ce025","value":{"height":956,"width":1700}}
[info] [Appium] New AndroidUiautomator2Driver session created successfully, session e11936e1-7fb2-46a9-af60-3e7535ea248b added to master session list
[debug] [BaseDriver] Event 'newSessionStarted' logged at 1625623757697 (10:09:17 GMT+0800 (中国标准时间))
[debug] [W3C (e11936e1)] Cached the protocol value 'W3C' for the new session e11936e1-7fb2-46a9-af60-3e7535ea248b
[debug] [W3C (e11936e1)] Responding to client with driver.createSession() result: {"capabilities":{"platform":"LINUX","webStorageEnabled":false,"takesScreenshot":true,"javascriptEnabled":true,"databaseEnabled":false,"networkConnectionEnabled":true,"locationContextEnabled":false,"warnings":{},"desired":{"platformName":"Android","deviceName":"6f5cca76"},"platformName":"Android","deviceName":"6f5cca76","deviceUDID":"6f5cca76","deviceApiLevel":28,"platformVersion":"9","deviceScreenSize":"1700x956","deviceScreenDensity":160,"deviceModel":"E28","deviceManufacturer":"XiaoPeng","pixelRatio":1,"statBarHeight":10,"viewportRect":{"left":0,"top":10,"width":1700,"height":946}}}
[info] [HTTP] <-- POST /wd/hub/session 200 16671 ms - 652
[info] [HTTP] 
[info] [HTTP] --> POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/timeouts
[info] [HTTP] {"implicit":20000}
[debug] [W3C (e11936e1)] Calling AppiumDriver.timeouts() with args: [null,null,null,null,20000,"e11936e1-7fb2-46a9-af60-3e7535ea248b"]
[debug] [BaseDriver] W3C timeout argument: {"implicit":20000}}
[debug] [BaseDriver] Set implicit wait to 20000ms
[debug] [W3C (e11936e1)] Responding to client with driver.timeouts() result: null
[info] [HTTP] <-- POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/timeouts 200 6 ms - 14
[info] [HTTP] [error] [Logcat] Logcat terminated with code 0, signal null
[debug] [Instrumentation] The process has exited with code 0[info] [HTTP] --> POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element
[info] [HTTP] {"using":"id","value":"com.xiaopeng.oobe:id/view_passistant_text"}
[debug] [W3C (e11936e1)] Calling AppiumDriver.findElement() with args: ["id","com.xiaopeng.oobe:id/view_passistant_text","e11936e1-7fb2-46a9-af60-3e7535ea248b"]
[debug] [BaseDriver] Valid locator strategies for this request: xpath, id, class name, accessibility id, css selector, -android uiautomator
[debug] [BaseDriver] Waiting up to 20000 ms for condition
[debug] [W3C (e11936e1)] Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: 'POST /element' cannot be proxied to UiAutomator2 server because the instrumentation process is not running (probably crashed). Check the server log and/or the logcat output for more details
[debug] [W3C (e11936e1)]     at UIA2Proxy.command (C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\jsonwp-proxy\proxy.js:274:13)
[debug] [W3C (e11936e1)]     at processTicksAndRejections (internal/process/task_queues.js:85:5)
[info] [HTTP] <-- POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element 500 54 ms - 886
[info] [HTTP] [info] [HTTP] --> POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element
[info] [HTTP] {"using":"id","value":"com.xiaopeng.oobe:id/view_passistant_text"}
[debug] [W3C (e11936e1)] Calling AppiumDriver.findElement() with args: ["id","com.xiaopeng.oobe:id/view_passistant_text","e11936e1-7fb2-46a9-af60-3e7535ea248b"]
[debug] [BaseDriver] Valid locator strategies for this request: xpath, id, class name, accessibility id, css selector, -android uiautomator
[debug] [BaseDriver] Waiting up to 20000 ms for condition
[debug] [W3C (e11936e1)] Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: 'POST /element' cannot be proxied to UiAutomator2 server because the instrumentation process is not running (probably crashed). Check the server log and/or the logcat output for more details
[debug] [W3C (e11936e1)]     at UIA2Proxy.command (C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\jsonwp-proxy\proxy.js:274:13)
[debug] [W3C (e11936e1)]     at processTicksAndRejections (internal/process/task_queues.js:85:5)
[info] [HTTP] <-- POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element 500 4 ms - 886
[info] [HTTP] [info] [HTTP] --> POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element
[info] [HTTP] {"using":"id","value":"com.xiaopeng.oobe:id/view_passistant_text"}
[debug] [W3C (e11936e1)] Calling AppiumDriver.findElement() with args: ["id","com.xiaopeng.oobe:id/view_passistant_text","e11936e1-7fb2-46a9-af60-3e7535ea248b"]
[debug] [BaseDriver] Valid locator strategies for this request: xpath, id, class name, accessibility id, css selector, -android uiautomator
[debug] [BaseDriver] Waiting up to 20000 ms for condition
[debug] [W3C (e11936e1)] Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: 'POST /element' cannot be proxied to UiAutomator2 server because the instrumentation process is not running (probably crashed). Check the server log and/or the logcat output for more details
[debug] [W3C (e11936e1)]     at UIA2Proxy.command (C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\jsonwp-proxy\proxy.js:274:13)
[debug] [W3C (e11936e1)]     at processTicksAndRejections (internal/process/task_queues.js:85:5)
[info] [HTTP] <-- POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element 500 8 ms - 886
[info] [HTTP] [info] [HTTP] --> POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element
[info] [HTTP] {"using":"id","value":"com.xiaopeng.oobe:id/view_passistant_text"}
[debug] [W3C (e11936e1)] Calling AppiumDriver.findElement() with args: ["id","com.xiaopeng.oobe:id/view_passistant_text","e11936e1-7fb2-46a9-af60-3e7535ea248b"]
[debug] [BaseDriver] Valid locator strategies for this request: xpath, id, class name, accessibility id, css selector, -android uiautomator
[debug] [BaseDriver] Waiting up to 20000 ms for condition
[debug] [W3C (e11936e1)] Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: 'POST /element' cannot be proxied to UiAutomator2 server because the instrumentation process is not running (probably crashed). Check the server log and/or the logcat output for more details
[debug] [W3C (e11936e1)]     at UIA2Proxy.command (C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\jsonwp-proxy\proxy.js:274:13)
[debug] [W3C (e11936e1)]     at processTicksAndRejections (internal/process/task_queues.js:85:5)
[info] [HTTP] <-- POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element 500 8 ms - 886
[info] [HTTP] [info] [HTTP] --> POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element
[info] [HTTP] {"using":"id","value":"com.xiaopeng.oobe:id/view_passistant_text"}
[debug] [W3C (e11936e1)] Calling AppiumDriver.findElement() with args: ["id","com.xiaopeng.oobe:id/view_passistant_text","e11936e1-7fb2-46a9-af60-3e7535ea248b"]
[debug] [BaseDriver] Valid locator strategies for this request: xpath, id, class name, accessibility id, css selector, -android uiautomator
[debug] [BaseDriver] Waiting up to 20000 ms for condition
[debug] [W3C (e11936e1)] Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: 'POST /element' cannot be proxied to UiAutomator2 server because the instrumentation process is not running (probably crashed). Check the server log and/or the logcat output for more details
[debug] [W3C (e11936e1)]     at UIA2Proxy.command (C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\jsonwp-proxy\proxy.js:274:13)
[debug] [W3C (e11936e1)]     at processTicksAndRejections (internal/process/task_queues.js:85:5)
[info] [HTTP] <-- POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element 500 8 ms - 886
[info] [HTTP] [info] [HTTP] --> POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element
[info] [HTTP] {"using":"id","value":"com.xiaopeng.oobe:id/view_passistant_text"}
[debug] [W3C (e11936e1)] Calling AppiumDriver.findElement() with args: ["id","com.xiaopeng.oobe:id/view_passistant_text","e11936e1-7fb2-46a9-af60-3e7535ea248b"]
[debug] [BaseDriver] Valid locator strategies for this request: xpath, id, class name, accessibility id, css selector, -android uiautomator
[debug] [BaseDriver] Waiting up to 20000 ms for condition
[debug] [W3C (e11936e1)] Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: 'POST /element' cannot be proxied to UiAutomator2 server because the instrumentation process is not running (probably crashed). Check the server log and/or the logcat output for more details
[debug] [W3C (e11936e1)]     at UIA2Proxy.command (C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\jsonwp-proxy\proxy.js:274:13)
[debug] [W3C (e11936e1)]     at processTicksAndRejections (internal/process/task_queues.js:85:5)
[info] [HTTP] <-- POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element 500 3 ms - 886
[info] [HTTP] [info] [HTTP] --> POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element
[info] [HTTP] {"using":"id","value":"com.xiaopeng.oobe:id/view_passistant_text"}
[debug] [W3C (e11936e1)] Calling AppiumDriver.findElement() with args: ["id","com.xiaopeng.oobe:id/view_passistant_text","e11936e1-7fb2-46a9-af60-3e7535ea248b"]
[debug] [BaseDriver] Valid locator strategies for this request: xpath, id, class name, accessibility id, css selector, -android uiautomator
[debug] [BaseDriver] Waiting up to 20000 ms for condition
[debug] [W3C (e11936e1)] Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: 'POST /element' cannot be proxied to UiAutomator2 server because the instrumentation process is not running (probably crashed). Check the server log and/or the logcat output for more details
[debug] [W3C (e11936e1)]     at UIA2Proxy.command (C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\jsonwp-proxy\proxy.js:274:13)
[debug] [W3C (e11936e1)]     at processTicksAndRejections (internal/process/task_queues.js:85:5)
[info] [HTTP] <-- POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element 500 7 ms - 886
[info] [HTTP] [info] [HTTP] --> POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element
[info] [HTTP] {"using":"id","value":"com.xiaopeng.oobe:id/view_passistant_text"}
[debug] [W3C (e11936e1)] Calling AppiumDriver.findElement() with args: ["id","com.xiaopeng.oobe:id/view_passistant_text","e11936e1-7fb2-46a9-af60-3e7535ea248b"]
[debug] [BaseDriver] Valid locator strategies for this request: xpath, id, class name, accessibility id, css selector, -android uiautomator
[debug] [BaseDriver] Waiting up to 20000 ms for condition
[debug] [W3C (e11936e1)] Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: 'POST /element' cannot be proxied to UiAutomator2 server because the instrumentation process is not running (probably crashed). Check the server log and/or the logcat output for more details
[debug] [W3C (e11936e1)]     at UIA2Proxy.command (C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\jsonwp-proxy\proxy.js:274:13)
[debug] [W3C (e11936e1)]     at processTicksAndRejections (internal/process/task_queues.js:85:5)
[info] [HTTP] <-- POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element 500 2 ms - 886
[info] [HTTP] [info] [HTTP] --> POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element
[info] [HTTP] {"using":"id","value":"com.xiaopeng.oobe:id/view_passistant_text"}
[debug] [W3C (e11936e1)] Calling AppiumDriver.findElement() with args: ["id","com.xiaopeng.oobe:id/view_passistant_text","e11936e1-7fb2-46a9-af60-3e7535ea248b"]
[debug] [BaseDriver] Valid locator strategies for this request: xpath, id, class name, accessibility id, css selector, -android uiautomator
[debug] [BaseDriver] Waiting up to 20000 ms for condition
[debug] [W3C (e11936e1)] Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: 'POST /element' cannot be proxied to UiAutomator2 server because the instrumentation process is not running (probably crashed). Check the server log and/or the logcat output for more details
[debug] [W3C (e11936e1)]     at UIA2Proxy.command (C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\jsonwp-proxy\proxy.js:274:13)
[debug] [W3C (e11936e1)]     at processTicksAndRejections (internal/process/task_queues.js:85:5)
[info] [HTTP] <-- POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element 500 6 ms - 886
[info] [HTTP] [info] [HTTP] --> POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element
[info] [HTTP] {"using":"id","value":"com.xiaopeng.oobe:id/view_passistant_text"}
[debug] [W3C (e11936e1)] Calling AppiumDriver.findElement() with args: ["id","com.xiaopeng.oobe:id/view_passistant_text","e11936e1-7fb2-46a9-af60-3e7535ea248b"]
[debug] [BaseDriver] Valid locator strategies for this request: xpath, id, class name, accessibility id, css selector, -android uiautomator
[debug] [BaseDriver] Waiting up to 20000 ms for condition
[debug] [W3C (e11936e1)] Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: 'POST /element' cannot be proxied to UiAutomator2 server because the instrumentation process is not running (probably crashed). Check the server log and/or the logcat output for more details
[debug] [W3C (e11936e1)]     at UIA2Proxy.command (C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\jsonwp-proxy\proxy.js:274:13)
[debug] [W3C (e11936e1)]     at processTicksAndRejections (internal/process/task_queues.js:85:5)
[info] [HTTP] <-- POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element 500 9 ms - 886
[info] [HTTP] [info] [HTTP] --> POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element
[info] [HTTP] {"using":"id","value":"com.xiaopeng.oobe:id/view_passistant_text"}
[debug] [W3C (e11936e1)] Calling AppiumDriver.findElement() with args: ["id","com.xiaopeng.oobe:id/view_passistant_text","e11936e1-7fb2-46a9-af60-3e7535ea248b"]
[debug] [BaseDriver] Valid locator strategies for this request: xpath, id, class name, accessibility id, css selector, -android uiautomator
[debug] [BaseDriver] Waiting up to 20000 ms for condition
[debug] [W3C (e11936e1)] Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: 'POST /element' cannot be proxied to UiAutomator2 server because the instrumentation process is not running (probably crashed). Check the server log and/or the logcat output for more details
[debug] [W3C (e11936e1)]     at UIA2Proxy.command (C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\jsonwp-proxy\proxy.js:274:13)
[debug] [W3C (e11936e1)]     at processTicksAndRejections (internal/process/task_queues.js:85:5)
[info] [HTTP] <-- POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element 500 7 ms - 886
[info] [HTTP] [info] [HTTP] --> POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element
[info] [HTTP] {"using":"id","value":"com.xiaopeng.oobe:id/view_passistant_text"}
[debug] [W3C (e11936e1)] Calling AppiumDriver.findElement() with args: ["id","com.xiaopeng.oobe:id/view_passistant_text","e11936e1-7fb2-46a9-af60-3e7535ea248b"]
[debug] [BaseDriver] Valid locator strategies for this request: xpath, id, class name, accessibility id, css selector, -android uiautomator
[debug] [BaseDriver] Waiting up to 20000 ms for condition
[debug] [W3C (e11936e1)] Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: 'POST /element' cannot be proxied to UiAutomator2 server because the instrumentation process is not running (probably crashed). Check the server log and/or the logcat output for more details
[debug] [W3C (e11936e1)]     at UIA2Proxy.command (C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\jsonwp-proxy\proxy.js:274:13)
[debug] [W3C (e11936e1)]     at processTicksAndRejections (internal/process/task_queues.js:85:5)
[info] [HTTP] <-- POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element 500 3 ms - 886
[info] [HTTP] [info] [HTTP] --> POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element
[info] [HTTP] {"using":"id","value":"com.xiaopeng.oobe:id/view_passistant_text"}
[debug] [W3C (e11936e1)] Calling AppiumDriver.findElement() with args: ["id","com.xiaopeng.oobe:id/view_passistant_text","e11936e1-7fb2-46a9-af60-3e7535ea248b"]
[debug] [BaseDriver] Valid locator strategies for this request: xpath, id, class name, accessibility id, css selector, -android uiautomator
[debug] [BaseDriver] Waiting up to 20000 ms for condition
[debug] [W3C (e11936e1)] Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: 'POST /element' cannot be proxied to UiAutomator2 server because the instrumentation process is not running (probably crashed). Check the server log and/or the logcat output for more details
[debug] [W3C (e11936e1)]     at UIA2Proxy.command (C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\jsonwp-proxy\proxy.js:274:13)
[debug] [W3C (e11936e1)]     at processTicksAndRejections (internal/process/task_queues.js:85:5)
[info] [HTTP] <-- POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element 500 6 ms - 886
[info] [HTTP] [info] [HTTP] --> POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element
[info] [HTTP] {"using":"id","value":"com.xiaopeng.oobe:id/view_passistant_text"}
[debug] [W3C (e11936e1)] Calling AppiumDriver.findElement() with args: ["id","com.xiaopeng.oobe:id/view_passistant_text","e11936e1-7fb2-46a9-af60-3e7535ea248b"]
[debug] [BaseDriver] Valid locator strategies for this request: xpath, id, class name, accessibility id, css selector, -android uiautomator
[debug] [BaseDriver] Waiting up to 20000 ms for condition
[debug] [W3C (e11936e1)] Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: 'POST /element' cannot be proxied to UiAutomator2 server because the instrumentation process is not running (probably crashed). Check the server log and/or the logcat output for more details
[debug] [W3C (e11936e1)]     at UIA2Proxy.command (C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\jsonwp-proxy\proxy.js:274:13)
[debug] [W3C (e11936e1)]     at processTicksAndRejections (internal/process/task_queues.js:85:5)
[info] [HTTP] <-- POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element 500 7 ms - 886
[info] [HTTP] [info] [HTTP] --> POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element
[info] [HTTP] {"using":"id","value":"com.xiaopeng.oobe:id/view_passistant_text"}
[debug] [W3C (e11936e1)] Calling AppiumDriver.findElement() with args: ["id","com.xiaopeng.oobe:id/view_passistant_text","e11936e1-7fb2-46a9-af60-3e7535ea248b"]
[debug] [BaseDriver] Valid locator strategies for this request: xpath, id, class name, accessibility id, css selector, -android uiautomator
[debug] [BaseDriver] Waiting up to 20000 ms for condition
[debug] [W3C (e11936e1)] Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: 'POST /element' cannot be proxied to UiAutomator2 server because the instrumentation process is not running (probably crashed). Check the server log and/or the logcat output for more details
[debug] [W3C (e11936e1)]     at UIA2Proxy.command (C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\jsonwp-proxy\proxy.js:274:13)
[debug] [W3C (e11936e1)]     at processTicksAndRejections (internal/process/task_queues.js:85:5)
[info] [HTTP] <-- POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element 500 7 ms - 886
[info] [HTTP] [info] [HTTP] --> POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element
[info] [HTTP] {"using":"id","value":"com.xiaopeng.oobe:id/view_passistant_text"}
[debug] [W3C (e11936e1)] Calling AppiumDriver.findElement() with args: ["id","com.xiaopeng.oobe:id/view_passistant_text","e11936e1-7fb2-46a9-af60-3e7535ea248b"]
[debug] [BaseDriver] Valid locator strategies for this request: xpath, id, class name, accessibility id, css selector, -android uiautomator
[debug] [BaseDriver] Waiting up to 20000 ms for condition
[debug] [W3C (e11936e1)] Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: 'POST /element' cannot be proxied to UiAutomator2 server because the instrumentation process is not running (probably crashed). Check the server log and/or the logcat output for more details
[debug] [W3C (e11936e1)]     at UIA2Proxy.command (C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\jsonwp-proxy\proxy.js:274:13)
[debug] [W3C (e11936e1)]     at processTicksAndRejections (internal/process/task_queues.js:85:5)
[info] [HTTP] <-- POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element 500 7 ms - 886
[info] [HTTP] [info] [HTTP] --> POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element
[info] [HTTP] {"using":"id","value":"com.xiaopeng.oobe:id/view_passistant_text"}
[debug] [W3C (e11936e1)] Calling AppiumDriver.findElement() with args: ["id","com.xiaopeng.oobe:id/view_passistant_text","e11936e1-7fb2-46a9-af60-3e7535ea248b"]
[debug] [BaseDriver] Valid locator strategies for this request: xpath, id, class name, accessibility id, css selector, -android uiautomator
[debug] [BaseDriver] Waiting up to 20000 ms for condition
[debug] [W3C (e11936e1)] Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: 'POST /element' cannot be proxied to UiAutomator2 server because the instrumentation process is not running (probably crashed). Check the server log and/or the logcat output for more details
[debug] [W3C (e11936e1)]     at UIA2Proxy.command (C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\jsonwp-proxy\proxy.js:274:13)
[debug] [W3C (e11936e1)]     at processTicksAndRejections (internal/process/task_queues.js:85:5)
[info] [HTTP] <-- POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element 500 10 ms - 886
[info] [HTTP] [info] [HTTP] --> POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element
[info] [HTTP] {"using":"id","value":"com.xiaopeng.oobe:id/view_passistant_text"}
[debug] [W3C (e11936e1)] Calling AppiumDriver.findElement() with args: ["id","com.xiaopeng.oobe:id/view_passistant_text","e11936e1-7fb2-46a9-af60-3e7535ea248b"]
[debug] [BaseDriver] Valid locator strategies for this request: xpath, id, class name, accessibility id, css selector, -android uiautomator
[debug] [BaseDriver] Waiting up to 20000 ms for condition
[debug] [W3C (e11936e1)] Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: 'POST /element' cannot be proxied to UiAutomator2 server because the instrumentation process is not running (probably crashed). Check the server log and/or the logcat output for more details
[debug] [W3C (e11936e1)]     at UIA2Proxy.command (C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\jsonwp-proxy\proxy.js:274:13)
[debug] [W3C (e11936e1)]     at processTicksAndRejections (internal/process/task_queues.js:85:5)
[info] [HTTP] <-- POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element 500 2 ms - 886
[info] [HTTP] [info] [HTTP] --> POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element
[info] [HTTP] {"using":"id","value":"com.xiaopeng.oobe:id/view_passistant_text"}
[debug] [W3C (e11936e1)] Calling AppiumDriver.findElement() with args: ["id","com.xiaopeng.oobe:id/view_passistant_text","e11936e1-7fb2-46a9-af60-3e7535ea248b"]
[debug] [BaseDriver] Valid locator strategies for this request: xpath, id, class name, accessibility id, css selector, -android uiautomator
[debug] [BaseDriver] Waiting up to 20000 ms for condition
[debug] [W3C (e11936e1)] Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: 'POST /element' cannot be proxied to UiAutomator2 server because the instrumentation process is not running (probably crashed). Check the server log and/or the logcat output for more details
[debug] [W3C (e11936e1)]     at UIA2Proxy.command (C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\jsonwp-proxy\proxy.js:274:13)
[debug] [W3C (e11936e1)]     at processTicksAndRejections (internal/process/task_queues.js:85:5)
[info] [HTTP] <-- POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element 500 2 ms - 886
[info] [HTTP] [info] [HTTP] --> POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element
[info] [HTTP] {"using":"id","value":"com.xiaopeng.oobe:id/view_passistant_text"}
[debug] [W3C (e11936e1)] Calling AppiumDriver.findElement() with args: ["id","com.xiaopeng.oobe:id/view_passistant_text","e11936e1-7fb2-46a9-af60-3e7535ea248b"]
[debug] [BaseDriver] Valid locator strategies for this request: xpath, id, class name, accessibility id, css selector, -android uiautomator
[debug] [BaseDriver] Waiting up to 20000 ms for condition
[debug] [W3C (e11936e1)] Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: 'POST /element' cannot be proxied to UiAutomator2 server because the instrumentation process is not running (probably crashed). Check the server log and/or the logcat output for more details
[debug] [W3C (e11936e1)]     at UIA2Proxy.command (C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\jsonwp-proxy\proxy.js:274:13)
[debug] [W3C (e11936e1)]     at processTicksAndRejections (internal/process/task_queues.js:85:5)
[info] [HTTP] <-- POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element 500 7 ms - 886
[info] [HTTP] [info] [HTTP] --> POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element
[info] [HTTP] {"using":"id","value":"com.xiaopeng.oobe:id/view_passistant_text"}
[debug] [W3C (e11936e1)] Calling AppiumDriver.findElement() with args: ["id","com.xiaopeng.oobe:id/view_passistant_text","e11936e1-7fb2-46a9-af60-3e7535ea248b"]
[debug] [BaseDriver] Valid locator strategies for this request: xpath, id, class name, accessibility id, css selector, -android uiautomator
[debug] [BaseDriver] Waiting up to 20000 ms for condition
[debug] [W3C (e11936e1)] Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: 'POST /element' cannot be proxied to UiAutomator2 server because the instrumentation process is not running (probably crashed). Check the server log and/or the logcat output for more details
[debug] [W3C (e11936e1)]     at UIA2Proxy.command (C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\jsonwp-proxy\proxy.js:274:13)
[debug] [W3C (e11936e1)]     at processTicksAndRejections (internal/process/task_queues.js:85:5)
[info] [HTTP] <-- POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element 500 3 ms - 886
[info] [HTTP] [info] [HTTP] --> POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element
[info] [HTTP] {"using":"id","value":"com.xiaopeng.oobe:id/view_passistant_text"}
[debug] [W3C (e11936e1)] Calling AppiumDriver.findElement() with args: ["id","com.xiaopeng.oobe:id/view_passistant_text","e11936e1-7fb2-46a9-af60-3e7535ea248b"]
[debug] [BaseDriver] Valid locator strategies for this request: xpath, id, class name, accessibility id, css selector, -android uiautomator
[debug] [BaseDriver] Waiting up to 20000 ms for condition
[debug] [W3C (e11936e1)] Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: 'POST /element' cannot be proxied to UiAutomator2 server because the instrumentation process is not running (probably crashed). Check the server log and/or the logcat output for more details
[debug] [W3C (e11936e1)]     at UIA2Proxy.command (C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\jsonwp-proxy\proxy.js:274:13)
[debug] [W3C (e11936e1)]     at processTicksAndRejections (internal/process/task_queues.js:85:5)
[info] [HTTP] <-- POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element 500 4 ms - 886
[info] [HTTP] [info] [HTTP] --> POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element
[info] [HTTP] {"using":"id","value":"com.xiaopeng.oobe:id/view_passistant_text"}
[debug] [W3C (e11936e1)] Calling AppiumDriver.findElement() with args: ["id","com.xiaopeng.oobe:id/view_passistant_text","e11936e1-7fb2-46a9-af60-3e7535ea248b"]
[debug] [BaseDriver] Valid locator strategies for this request: xpath, id, class name, accessibility id, css selector, -android uiautomator
[debug] [BaseDriver] Waiting up to 20000 ms for condition
[debug] [W3C (e11936e1)] Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: 'POST /element' cannot be proxied to UiAutomator2 server because the instrumentation process is not running (probably crashed). Check the server log and/or the logcat output for more details
[debug] [W3C (e11936e1)]     at UIA2Proxy.command (C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\jsonwp-proxy\proxy.js:274:13)
[debug] [W3C (e11936e1)]     at processTicksAndRejections (internal/process/task_queues.js:85:5)
[info] [HTTP] <-- POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element 500 1 ms - 886
[info] [HTTP] [info] [HTTP] --> POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element
[info] [HTTP] {"using":"id","value":"com.xiaopeng.oobe:id/view_passistant_text"}
[debug] [W3C (e11936e1)] Calling AppiumDriver.findElement() with args: ["id","com.xiaopeng.oobe:id/view_passistant_text","e11936e1-7fb2-46a9-af60-3e7535ea248b"]
[debug] [BaseDriver] Valid locator strategies for this request: xpath, id, class name, accessibility id, css selector, -android uiautomator
[debug] [BaseDriver] Waiting up to 20000 ms for condition
[debug] [W3C (e11936e1)] Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: 'POST /element' cannot be proxied to UiAutomator2 server because the instrumentation process is not running (probably crashed). Check the server log and/or the logcat output for more details
[debug] [W3C (e11936e1)]     at UIA2Proxy.command (C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\jsonwp-proxy\proxy.js:274:13)
[debug] [W3C (e11936e1)]     at processTicksAndRejections (internal/process/task_queues.js:85:5)
[info] [HTTP] <-- POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element 500 2 ms - 886
[info] [HTTP] [info] [HTTP] --> POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element
[info] [HTTP] {"using":"id","value":"com.xiaopeng.oobe:id/view_passistant_text"}
[debug] [W3C (e11936e1)] Calling AppiumDriver.findElement() with args: ["id","com.xiaopeng.oobe:id/view_passistant_text","e11936e1-7fb2-46a9-af60-3e7535ea248b"]
[debug] [BaseDriver] Valid locator strategies for this request: xpath, id, class name, accessibility id, css selector, -android uiautomator
[debug] [BaseDriver] Waiting up to 20000 ms for condition
[debug] [W3C (e11936e1)] Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: 'POST /element' cannot be proxied to UiAutomator2 server because the instrumentation process is not running (probably crashed). Check the server log and/or the logcat output for more details
[debug] [W3C (e11936e1)]     at UIA2Proxy.command (C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\jsonwp-proxy\proxy.js:274:13)
[debug] [W3C (e11936e1)]     at processTicksAndRejections (internal/process/task_queues.js:85:5)
[info] [HTTP] <-- POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element 500 3 ms - 886
[info] [HTTP] [info] [HTTP] --> POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element
[info] [HTTP] {"using":"id","value":"com.xiaopeng.oobe:id/view_passistant_text"}
[debug] [W3C (e11936e1)] Calling AppiumDriver.findElement() with args: ["id","com.xiaopeng.oobe:id/view_passistant_text","e11936e1-7fb2-46a9-af60-3e7535ea248b"]
[debug] [BaseDriver] Valid locator strategies for this request: xpath, id, class name, accessibility id, css selector, -android uiautomator
[debug] [BaseDriver] Waiting up to 20000 ms for condition
[debug] [W3C (e11936e1)] Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: 'POST /element' cannot be proxied to UiAutomator2 server because the instrumentation process is not running (probably crashed). Check the server log and/or the logcat output for more details
[debug] [W3C (e11936e1)]     at UIA2Proxy.command (C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\jsonwp-proxy\proxy.js:274:13)
[debug] [W3C (e11936e1)]     at processTicksAndRejections (internal/process/task_queues.js:85:5)
[info] [HTTP] <-- POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element 500 1 ms - 886
[info] [HTTP] [info] [HTTP] --> POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element
[info] [HTTP] {"using":"id","value":"com.xiaopeng.oobe:id/view_passistant_text"}
[debug] [W3C (e11936e1)] Calling AppiumDriver.findElement() with args: ["id","com.xiaopeng.oobe:id/view_passistant_text","e11936e1-7fb2-46a9-af60-3e7535ea248b"]
[debug] [BaseDriver] Valid locator strategies for this request: xpath, id, class name, accessibility id, css selector, -android uiautomator
[debug] [BaseDriver] Waiting up to 20000 ms for condition
[debug] [W3C (e11936e1)] Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: 'POST /element' cannot be proxied to UiAutomator2 server because the instrumentation process is not running (probably crashed). Check the server log and/or the logcat output for more details
[debug] [W3C (e11936e1)]     at UIA2Proxy.command (C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\jsonwp-proxy\proxy.js:274:13)
[debug] [W3C (e11936e1)]     at processTicksAndRejections (internal/process/task_queues.js:85:5)
[info] [HTTP] <-- POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element 500 1 ms - 886
[info] [HTTP] [info] [HTTP] --> POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element
[info] [HTTP] {"using":"id","value":"com.xiaopeng.oobe:id/view_passistant_text"}
[debug] [W3C (e11936e1)] Calling AppiumDriver.findElement() with args: ["id","com.xiaopeng.oobe:id/view_passistant_text","e11936e1-7fb2-46a9-af60-3e7535ea248b"]
[debug] [BaseDriver] Valid locator strategies for this request: xpath, id, class name, accessibility id, css selector, -android uiautomator
[debug] [BaseDriver] Waiting up to 20000 ms for condition
[debug] [W3C (e11936e1)] Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: 'POST /element' cannot be proxied to UiAutomator2 server because the instrumentation process is not running (probably crashed). Check the server log and/or the logcat output for more details
[debug] [W3C (e11936e1)]     at UIA2Proxy.command (C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\jsonwp-proxy\proxy.js:274:13)
[debug] [W3C (e11936e1)]     at processTicksAndRejections (internal/process/task_queues.js:85:5)
[info] [HTTP] <-- POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element 500 1 ms - 886
[info] [HTTP] [info] [HTTP] --> POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element
[info] [HTTP] {"using":"id","value":"com.xiaopeng.oobe:id/view_passistant_text"}
[debug] [W3C (e11936e1)] Calling AppiumDriver.findElement() with args: ["id","com.xiaopeng.oobe:id/view_passistant_text","e11936e1-7fb2-46a9-af60-3e7535ea248b"]
[debug] [BaseDriver] Valid locator strategies for this request: xpath, id, class name, accessibility id, css selector, -android uiautomator
[debug] [BaseDriver] Waiting up to 20000 ms for condition
[debug] [W3C (e11936e1)] Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: 'POST /element' cannot be proxied to UiAutomator2 server because the instrumentation process is not running (probably crashed). Check the server log and/or the logcat output for more details
[debug] [W3C (e11936e1)]     at UIA2Proxy.command (C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\jsonwp-proxy\proxy.js:274:13)
[debug] [W3C (e11936e1)]     at processTicksAndRejections (internal/process/task_queues.js:85:5)
[info] [HTTP] <-- POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element 500 4 ms - 886
[info] [HTTP] [info] [HTTP] --> POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element
[info] [HTTP] {"using":"id","value":"com.xiaopeng.oobe:id/view_passistant_text"}
[debug] [W3C (e11936e1)] Calling AppiumDriver.findElement() with args: ["id","com.xiaopeng.oobe:id/view_passistant_text","e11936e1-7fb2-46a9-af60-3e7535ea248b"]
[debug] [BaseDriver] Valid locator strategies for this request: xpath, id, class name, accessibility id, css selector, -android uiautomator
[debug] [BaseDriver] Waiting up to 20000 ms for condition
[debug] [W3C (e11936e1)] Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: 'POST /element' cannot be proxied to UiAutomator2 server because the instrumentation process is not running (probably crashed). Check the server log and/or the logcat output for more details
[debug] [W3C (e11936e1)]     at UIA2Proxy.command (C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\jsonwp-proxy\proxy.js:274:13)
[debug] [W3C (e11936e1)]     at processTicksAndRejections (internal/process/task_queues.js:85:5)
[info] [HTTP] <-- POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element 500 1 ms - 886
[info] [HTTP] [info] [HTTP] --> POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element
[info] [HTTP] {"using":"id","value":"com.xiaopeng.oobe:id/view_passistant_text"}
[debug] [W3C (e11936e1)] Calling AppiumDriver.findElement() with args: ["id","com.xiaopeng.oobe:id/view_passistant_text","e11936e1-7fb2-46a9-af60-3e7535ea248b"]
[debug] [BaseDriver] Valid locator strategies for this request: xpath, id, class name, accessibility id, css selector, -android uiautomator
[debug] [BaseDriver] Waiting up to 20000 ms for condition
[debug] [W3C (e11936e1)] Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: 'POST /element' cannot be proxied to UiAutomator2 server because the instrumentation process is not running (probably crashed). Check the server log and/or the logcat output for more details
[debug] [W3C (e11936e1)]     at UIA2Proxy.command (C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\jsonwp-proxy\proxy.js:274:13)
[debug] [W3C (e11936e1)]     at processTicksAndRejections (internal/process/task_queues.js:85:5)
[info] [HTTP] <-- POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element 500 4 ms - 886
[info] [HTTP] [info] [HTTP] --> POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element
[info] [HTTP] {"using":"id","value":"com.xiaopeng.oobe:id/view_passistant_text"}
[debug] [W3C (e11936e1)] Calling AppiumDriver.findElement() with args: ["id","com.xiaopeng.oobe:id/view_passistant_text","e11936e1-7fb2-46a9-af60-3e7535ea248b"]
[debug] [BaseDriver] Valid locator strategies for this request: xpath, id, class name, accessibility id, css selector, -android uiautomator
[debug] [BaseDriver] Waiting up to 20000 ms for condition
[debug] [W3C (e11936e1)] Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: 'POST /element' cannot be proxied to UiAutomator2 server because the instrumentation process is not running (probably crashed). Check the server log and/or the logcat output for more details
[debug] [W3C (e11936e1)]     at UIA2Proxy.command (C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\jsonwp-proxy\proxy.js:274:13)
[debug] [W3C (e11936e1)]     at processTicksAndRejections (internal/process/task_queues.js:85:5)
[info] [HTTP] <-- POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element 500 2 ms - 886
[info] [HTTP] [info] [HTTP] --> POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element
[info] [HTTP] {"using":"id","value":"com.xiaopeng.oobe:id/view_passistant_text"}
[debug] [W3C (e11936e1)] Calling AppiumDriver.findElement() with args: ["id","com.xiaopeng.oobe:id/view_passistant_text","e11936e1-7fb2-46a9-af60-3e7535ea248b"]
[debug] [BaseDriver] Valid locator strategies for this request: xpath, id, class name, accessibility id, css selector, -android uiautomator
[debug] [BaseDriver] Waiting up to 20000 ms for condition
[debug] [W3C (e11936e1)] Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: 'POST /element' cannot be proxied to UiAutomator2 server because the instrumentation process is not running (probably crashed). Check the server log and/or the logcat output for more details
[debug] [W3C (e11936e1)]     at UIA2Proxy.command (C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\jsonwp-proxy\proxy.js:274:13)
[debug] [W3C (e11936e1)]     at processTicksAndRejections (internal/process/task_queues.js:85:5)
[info] [HTTP] <-- POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element 500 9 ms - 886
[info] [HTTP] [info] [HTTP] --> POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element
[info] [HTTP] {"using":"id","value":"com.xiaopeng.oobe:id/view_passistant_text"}
[debug] [W3C (e11936e1)] Calling AppiumDriver.findElement() with args: ["id","com.xiaopeng.oobe:id/view_passistant_text","e11936e1-7fb2-46a9-af60-3e7535ea248b"]
[debug] [BaseDriver] Valid locator strategies for this request: xpath, id, class name, accessibility id, css selector, -android uiautomator
[debug] [BaseDriver] Waiting up to 20000 ms for condition
[debug] [W3C (e11936e1)] Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: 'POST /element' cannot be proxied to UiAutomator2 server because the instrumentation process is not running (probably crashed). Check the server log and/or the logcat output for more details
[debug] [W3C (e11936e1)]     at UIA2Proxy.command (C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\jsonwp-proxy\proxy.js:274:13)
[debug] [W3C (e11936e1)]     at processTicksAndRejections (internal/process/task_queues.js:85:5)
[info] [HTTP] <-- POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element 500 3 ms - 886
[info] [HTTP] [info] [HTTP] --> POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element
[info] [HTTP] {"using":"id","value":"com.xiaopeng.oobe:id/view_passistant_text"}
[debug] [W3C (e11936e1)] Calling AppiumDriver.findElement() with args: ["id","com.xiaopeng.oobe:id/view_passistant_text","e11936e1-7fb2-46a9-af60-3e7535ea248b"]
[debug] [BaseDriver] Valid locator strategies for this request: xpath, id, class name, accessibility id, css selector, -android uiautomator
[debug] [BaseDriver] Waiting up to 20000 ms for condition
[debug] [W3C (e11936e1)] Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: 'POST /element' cannot be proxied to UiAutomator2 server because the instrumentation process is not running (probably crashed). Check the server log and/or the logcat output for more details
[debug] [W3C (e11936e1)]     at UIA2Proxy.command (C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\jsonwp-proxy\proxy.js:274:13)
[debug] [W3C (e11936e1)]     at processTicksAndRejections (internal/process/task_queues.js:85:5)
[info] [HTTP] <-- POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element 500 1 ms - 886
[info] [HTTP] [info] [HTTP] --> POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element
[info] [HTTP] {"using":"id","value":"com.xiaopeng.oobe:id/view_passistant_text"}
[debug] [W3C (e11936e1)] Calling AppiumDriver.findElement() with args: ["id","com.xiaopeng.oobe:id/view_passistant_text","e11936e1-7fb2-46a9-af60-3e7535ea248b"]
[debug] [BaseDriver] Valid locator strategies for this request: xpath, id, class name, accessibility id, css selector, -android uiautomator
[debug] [BaseDriver] Waiting up to 20000 ms for condition
[debug] [W3C (e11936e1)] Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: 'POST /element' cannot be proxied to UiAutomator2 server because the instrumentation process is not running (probably crashed). Check the server log and/or the logcat output for more details
[debug] [W3C (e11936e1)]     at UIA2Proxy.command (C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\jsonwp-proxy\proxy.js:274:13)
[debug] [W3C (e11936e1)]     at processTicksAndRejections (internal/process/task_queues.js:85:5)
[info] [HTTP] <-- POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element 500 1 ms - 886
[info] [HTTP] [info] [HTTP] --> POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element
[info] [HTTP] {"using":"id","value":"com.xiaopeng.oobe:id/view_passistant_text"}
[debug] [W3C (e11936e1)] Calling AppiumDriver.findElement() with args: ["id","com.xiaopeng.oobe:id/view_passistant_text","e11936e1-7fb2-46a9-af60-3e7535ea248b"]
[debug] [BaseDriver] Valid locator strategies for this request: xpath, id, class name, accessibility id, css selector, -android uiautomator
[debug] [BaseDriver] Waiting up to 20000 ms for condition
[debug] [W3C (e11936e1)] Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: 'POST /element' cannot be proxied to UiAutomator2 server because the instrumentation process is not running (probably crashed). Check the server log and/or the logcat output for more details
[debug] [W3C (e11936e1)]     at UIA2Proxy.command (C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\jsonwp-proxy\proxy.js:274:13)
[debug] [W3C (e11936e1)]     at processTicksAndRejections (internal/process/task_queues.js:85:5)
[info] [HTTP] <-- POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element 500 2 ms - 886
[info] [HTTP] [info] [HTTP] --> POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element
[info] [HTTP] {"using":"id","value":"com.xiaopeng.oobe:id/view_passistant_text"}
[debug] [W3C (e11936e1)] Calling AppiumDriver.findElement() with args: ["id","com.xiaopeng.oobe:id/view_passistant_text","e11936e1-7fb2-46a9-af60-3e7535ea248b"]
[debug] [BaseDriver] Valid locator strategies for this request: xpath, id, class name, accessibility id, css selector, -android uiautomator
[debug] [BaseDriver] Waiting up to 20000 ms for condition
[debug] [W3C (e11936e1)] Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: 'POST /element' cannot be proxied to UiAutomator2 server because the instrumentation process is not running (probably crashed). Check the server log and/or the logcat output for more details
[debug] [W3C (e11936e1)]     at UIA2Proxy.command (C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\jsonwp-proxy\proxy.js:274:13)
[debug] [W3C (e11936e1)]     at processTicksAndRejections (internal/process/task_queues.js:85:5)
[info] [HTTP] <-- POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element 500 6 ms - 886
[info] [HTTP] [info] [HTTP] --> POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element
[info] [HTTP] {"using":"id","value":"com.xiaopeng.oobe:id/view_passistant_text"}
[debug] [W3C (e11936e1)] Calling AppiumDriver.findElement() with args: ["id","com.xiaopeng.oobe:id/view_passistant_text","e11936e1-7fb2-46a9-af60-3e7535ea248b"]
[debug] [BaseDriver] Valid locator strategies for this request: xpath, id, class name, accessibility id, css selector, -android uiautomator
[debug] [BaseDriver] Waiting up to 20000 ms for condition
[debug] [W3C (e11936e1)] Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: 'POST /element' cannot be proxied to UiAutomator2 server because the instrumentation process is not running (probably crashed). Check the server log and/or the logcat output for more details
[debug] [W3C (e11936e1)]     at UIA2Proxy.command (C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\jsonwp-proxy\proxy.js:274:13)
[debug] [W3C (e11936e1)]     at processTicksAndRejections (internal/process/task_queues.js:85:5)
[info] [HTTP] <-- POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element 500 1 ms - 886
[info] [HTTP] [info] [HTTP] --> POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element
[info] [HTTP] {"using":"id","value":"com.xiaopeng.oobe:id/view_passistant_text"}
[debug] [W3C (e11936e1)] Calling AppiumDriver.findElement() with args: ["id","com.xiaopeng.oobe:id/view_passistant_text","e11936e1-7fb2-46a9-af60-3e7535ea248b"]
[debug] [BaseDriver] Valid locator strategies for this request: xpath, id, class name, accessibility id, css selector, -android uiautomator
[debug] [BaseDriver] Waiting up to 20000 ms for condition
[debug] [W3C (e11936e1)] Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: 'POST /element' cannot be proxied to UiAutomator2 server because the instrumentation process is not running (probably crashed). Check the server log and/or the logcat output for more details
[debug] [W3C (e11936e1)]     at UIA2Proxy.command (C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\jsonwp-proxy\proxy.js:274:13)
[debug] [W3C (e11936e1)]     at processTicksAndRejections (internal/process/task_queues.js:85:5)
[info] [HTTP] <-- POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element 500 2 ms - 886
[info] [HTTP] [info] [HTTP] --> POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element
[info] [HTTP] {"using":"id","value":"com.xiaopeng.oobe:id/view_passistant_text"}
[debug] [W3C (e11936e1)] Calling AppiumDriver.findElement() with args: ["id","com.xiaopeng.oobe:id/view_passistant_text","e11936e1-7fb2-46a9-af60-3e7535ea248b"]
[debug] [BaseDriver] Valid locator strategies for this request: xpath, id, class name, accessibility id, css selector, -android uiautomator
[debug] [BaseDriver] Waiting up to 20000 ms for condition
[debug] [W3C (e11936e1)] Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: 'POST /element' cannot be proxied to UiAutomator2 server because the instrumentation process is not running (probably crashed). Check the server log and/or the logcat output for more details
[debug] [W3C (e11936e1)]     at UIA2Proxy.command (C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\jsonwp-proxy\proxy.js:274:13)
[debug] [W3C (e11936e1)]     at processTicksAndRejections (internal/process/task_queues.js:85:5)
[info] [HTTP] <-- POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element 500 9 ms - 886
[info] [HTTP] [info] [HTTP] --> POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element
[info] [HTTP] {"using":"id","value":"com.xiaopeng.oobe:id/view_passistant_text"}
[debug] [W3C (e11936e1)] Calling AppiumDriver.findElement() with args: ["id","com.xiaopeng.oobe:id/view_passistant_text","e11936e1-7fb2-46a9-af60-3e7535ea248b"]
[debug] [BaseDriver] Valid locator strategies for this request: xpath, id, class name, accessibility id, css selector, -android uiautomator
[debug] [BaseDriver] Waiting up to 20000 ms for condition
[debug] [W3C (e11936e1)] Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: 'POST /element' cannot be proxied to UiAutomator2 server because the instrumentation process is not running (probably crashed). Check the server log and/or the logcat output for more details
[debug] [W3C (e11936e1)]     at UIA2Proxy.command (C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\jsonwp-proxy\proxy.js:274:13)
[debug] [W3C (e11936e1)]     at processTicksAndRejections (internal/process/task_queues.js:85:5)
[info] [HTTP] <-- POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element 500 2 ms - 886
[info] [HTTP] [info] [HTTP] --> POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element
[info] [HTTP] {"using":"id","value":"com.xiaopeng.oobe:id/view_passistant_text"}
[debug] [W3C (e11936e1)] Calling AppiumDriver.findElement() with args: ["id","com.xiaopeng.oobe:id/view_passistant_text","e11936e1-7fb2-46a9-af60-3e7535ea248b"]
[debug] [BaseDriver] Valid locator strategies for this request: xpath, id, class name, accessibility id, css selector, -android uiautomator
[debug] [BaseDriver] Waiting up to 20000 ms for condition
[debug] [W3C (e11936e1)] Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: 'POST /element' cannot be proxied to UiAutomator2 server because the instrumentation process is not running (probably crashed). Check the server log and/or the logcat output for more details
[debug] [W3C (e11936e1)]     at UIA2Proxy.command (C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\jsonwp-proxy\proxy.js:274:13)
[debug] [W3C (e11936e1)]     at processTicksAndRejections (internal/process/task_queues.js:85:5)
[info] [HTTP] <-- POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element 500 5 ms - 886
[info] [HTTP] [info] [HTTP] --> POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element
[info] [HTTP] {"using":"id","value":"com.xiaopeng.oobe:id/view_passistant_text"}
[debug] [W3C (e11936e1)] Calling AppiumDriver.findElement() with args: ["id","com.xiaopeng.oobe:id/view_passistant_text","e11936e1-7fb2-46a9-af60-3e7535ea248b"]
[debug] [BaseDriver] Valid locator strategies for this request: xpath, id, class name, accessibility id, css selector, -android uiautomator
[debug] [BaseDriver] Waiting up to 20000 ms for condition
[debug] [W3C (e11936e1)] Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: 'POST /element' cannot be proxied to UiAutomator2 server because the instrumentation process is not running (probably crashed). Check the server log and/or the logcat output for more details
[debug] [W3C (e11936e1)]     at UIA2Proxy.command (C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\jsonwp-proxy\proxy.js:274:13)
[debug] [W3C (e11936e1)]     at processTicksAndRejections (internal/process/task_queues.js:85:5)
[info] [HTTP] <-- POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element 500 1 ms - 886
[info] [HTTP] [info] [HTTP] --> POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element
[info] [HTTP] {"using":"id","value":"com.xiaopeng.oobe:id/view_passistant_text"}
[debug] [W3C (e11936e1)] Calling AppiumDriver.findElement() with args: ["id","com.xiaopeng.oobe:id/view_passistant_text","e11936e1-7fb2-46a9-af60-3e7535ea248b"]
[debug] [BaseDriver] Valid locator strategies for this request: xpath, id, class name, accessibility id, css selector, -android uiautomator
[debug] [BaseDriver] Waiting up to 20000 ms for condition
[debug] [W3C (e11936e1)] Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: 'POST /element' cannot be proxied to UiAutomator2 server because the instrumentation process is not running (probably crashed). Check the server log and/or the logcat output for more details
[debug] [W3C (e11936e1)]     at UIA2Proxy.command (C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\jsonwp-proxy\proxy.js:274:13)
[debug] [W3C (e11936e1)]     at processTicksAndRejections (internal/process/task_queues.js:85:5)
[info] [HTTP] <-- POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element 500 4 ms - 886
[info] [HTTP] [info] [HTTP] --> POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element
[info] [HTTP] {"using":"id","value":"com.xiaopeng.oobe:id/view_passistant_text"}
[debug] [W3C (e11936e1)] Calling AppiumDriver.findElement() with args: ["id","com.xiaopeng.oobe:id/view_passistant_text","e11936e1-7fb2-46a9-af60-3e7535ea248b"]
[debug] [BaseDriver] Valid locator strategies for this request: xpath, id, class name, accessibility id, css selector, -android uiautomator
[debug] [BaseDriver] Waiting up to 20000 ms for condition
[debug] [W3C (e11936e1)] Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: 'POST /element' cannot be proxied to UiAutomator2 server because the instrumentation process is not running (probably crashed). Check the server log and/or the logcat output for more details
[debug] [W3C (e11936e1)]     at UIA2Proxy.command (C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\jsonwp-proxy\proxy.js:274:13)
[debug] [W3C (e11936e1)]     at processTicksAndRejections (internal/process/task_queues.js:85:5)
[info] [HTTP] <-- POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element 500 2 ms - 886
[info] [HTTP] [info] [HTTP] --> POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element
[info] [HTTP] {"using":"id","value":"com.xiaopeng.oobe:id/view_passistant_text"}
[debug] [W3C (e11936e1)] Calling AppiumDriver.findElement() with args: ["id","com.xiaopeng.oobe:id/view_passistant_text","e11936e1-7fb2-46a9-af60-3e7535ea248b"]
[debug] [BaseDriver] Valid locator strategies for this request: xpath, id, class name, accessibility id, css selector, -android uiautomator
[debug] [BaseDriver] Waiting up to 20000 ms for condition
[debug] [W3C (e11936e1)] Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: 'POST /element' cannot be proxied to UiAutomator2 server because the instrumentation process is not running (probably crashed). Check the server log and/or the logcat output for more details
[debug] [W3C (e11936e1)]     at UIA2Proxy.command (C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\jsonwp-proxy\proxy.js:274:13)
[debug] [W3C (e11936e1)]     at processTicksAndRejections (internal/process/task_queues.js:85:5)
[info] [HTTP] <-- POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element 500 1 ms - 886
[info] [HTTP] [info] [HTTP] --> POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element
[info] [HTTP] {"using":"id","value":"com.xiaopeng.oobe:id/view_passistant_text"}
[debug] [W3C (e11936e1)] Calling AppiumDriver.findElement() with args: ["id","com.xiaopeng.oobe:id/view_passistant_text","e11936e1-7fb2-46a9-af60-3e7535ea248b"]
[debug] [BaseDriver] Valid locator strategies for this request: xpath, id, class name, accessibility id, css selector, -android uiautomator
[debug] [BaseDriver] Waiting up to 20000 ms for condition
[debug] [W3C (e11936e1)] Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: 'POST /element' cannot be proxied to UiAutomator2 server because the instrumentation process is not running (probably crashed). Check the server log and/or the logcat output for more details
[debug] [W3C (e11936e1)]     at UIA2Proxy.command (C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\jsonwp-proxy\proxy.js:274:13)
[debug] [W3C (e11936e1)]     at processTicksAndRejections (internal/process/task_queues.js:85:5)
[info] [HTTP] <-- POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element 500 1 ms - 886
[info] [HTTP] [info] [HTTP] --> POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element
[info] [HTTP] {"using":"id","value":"com.xiaopeng.oobe:id/view_passistant_text"}
[debug] [W3C (e11936e1)] Calling AppiumDriver.findElement() with args: ["id","com.xiaopeng.oobe:id/view_passistant_text","e11936e1-7fb2-46a9-af60-3e7535ea248b"]
[debug] [BaseDriver] Valid locator strategies for this request: xpath, id, class name, accessibility id, css selector, -android uiautomator
[debug] [BaseDriver] Waiting up to 20000 ms for condition
[debug] [W3C (e11936e1)] Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: 'POST /element' cannot be proxied to UiAutomator2 server because the instrumentation process is not running (probably crashed). Check the server log and/or the logcat output for more details
[debug] [W3C (e11936e1)]     at UIA2Proxy.command (C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\jsonwp-proxy\proxy.js:274:13)
[debug] [W3C (e11936e1)]     at processTicksAndRejections (internal/process/task_queues.js:85:5)
[info] [HTTP] <-- POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element 500 9 ms - 886
[info] [HTTP] [info] [HTTP] --> POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element
[info] [HTTP] {"using":"id","value":"com.xiaopeng.oobe:id/view_passistant_text"}
[debug] [W3C (e11936e1)] Calling AppiumDriver.findElement() with args: ["id","com.xiaopeng.oobe:id/view_passistant_text","e11936e1-7fb2-46a9-af60-3e7535ea248b"]
[debug] [BaseDriver] Valid locator strategies for this request: xpath, id, class name, accessibility id, css selector, -android uiautomator
[debug] [BaseDriver] Waiting up to 20000 ms for condition
[debug] [W3C (e11936e1)] Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: 'POST /element' cannot be proxied to UiAutomator2 server because the instrumentation process is not running (probably crashed). Check the server log and/or the logcat output for more details
[debug] [W3C (e11936e1)]     at UIA2Proxy.command (C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\jsonwp-proxy\proxy.js:274:13)
[debug] [W3C (e11936e1)]     at processTicksAndRejections (internal/process/task_queues.js:85:5)
[info] [HTTP] <-- POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element 500 6 ms - 886
[info] [HTTP] [info] [HTTP] --> POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element
[info] [HTTP] {"using":"id","value":"com.xiaopeng.oobe:id/view_passistant_text"}
[debug] [W3C (e11936e1)] Calling AppiumDriver.findElement() with args: ["id","com.xiaopeng.oobe:id/view_passistant_text","e11936e1-7fb2-46a9-af60-3e7535ea248b"]
[debug] [BaseDriver] Valid locator strategies for this request: xpath, id, class name, accessibility id, css selector, -android uiautomator
[debug] [BaseDriver] Waiting up to 20000 ms for condition
[debug] [W3C (e11936e1)] Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: 'POST /element' cannot be proxied to UiAutomator2 server because the instrumentation process is not running (probably crashed). Check the server log and/or the logcat output for more details
[debug] [W3C (e11936e1)]     at UIA2Proxy.command (C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\jsonwp-proxy\proxy.js:274:13)
[debug] [W3C (e11936e1)]     at processTicksAndRejections (internal/process/task_queues.js:85:5)
[info] [HTTP] <-- POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element 500 1 ms - 886
[info] [HTTP] [info] [HTTP] --> POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element
[info] [HTTP] {"using":"id","value":"com.xiaopeng.oobe:id/view_passistant_text"}
[debug] [W3C (e11936e1)] Calling AppiumDriver.findElement() with args: ["id","com.xiaopeng.oobe:id/view_passistant_text","e11936e1-7fb2-46a9-af60-3e7535ea248b"]
[debug] [BaseDriver] Valid locator strategies for this request: xpath, id, class name, accessibility id, css selector, -android uiautomator
[debug] [BaseDriver] Waiting up to 20000 ms for condition
[debug] [W3C (e11936e1)] Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: 'POST /element' cannot be proxied to UiAutomator2 server because the instrumentation process is not running (probably crashed). Check the server log and/or the logcat output for more details
[debug] [W3C (e11936e1)]     at UIA2Proxy.command (C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\jsonwp-proxy\proxy.js:274:13)
[debug] [W3C (e11936e1)]     at processTicksAndRejections (internal/process/task_queues.js:85:5)
[info] [HTTP] <-- POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element 500 1 ms - 886
[info] [HTTP] [info] [HTTP] --> POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element
[info] [HTTP] {"using":"id","value":"com.xiaopeng.oobe:id/view_passistant_text"}
[debug] [W3C (e11936e1)] Calling AppiumDriver.findElement() with args: ["id","com.xiaopeng.oobe:id/view_passistant_text","e11936e1-7fb2-46a9-af60-3e7535ea248b"]
[debug] [BaseDriver] Valid locator strategies for this request: xpath, id, class name, accessibility id, css selector, -android uiautomator
[debug] [BaseDriver] Waiting up to 20000 ms for condition
[debug] [W3C (e11936e1)] Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: 'POST /element' cannot be proxied to UiAutomator2 server because the instrumentation process is not running (probably crashed). Check the server log and/or the logcat output for more details
[debug] [W3C (e11936e1)]     at UIA2Proxy.command (C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\jsonwp-proxy\proxy.js:274:13)
[debug] [W3C (e11936e1)]     at processTicksAndRejections (internal/process/task_queues.js:85:5)
[info] [HTTP] <-- POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element 500 9 ms - 886
[info] [HTTP] [info] [HTTP] --> POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element
[info] [HTTP] {"using":"id","value":"com.xiaopeng.oobe:id/view_passistant_text"}
[debug] [W3C (e11936e1)] Calling AppiumDriver.findElement() with args: ["id","com.xiaopeng.oobe:id/view_passistant_text","e11936e1-7fb2-46a9-af60-3e7535ea248b"]
[debug] [BaseDriver] Valid locator strategies for this request: xpath, id, class name, accessibility id, css selector, -android uiautomator
[debug] [BaseDriver] Waiting up to 20000 ms for condition
[debug] [W3C (e11936e1)] Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: 'POST /element' cannot be proxied to UiAutomator2 server because the instrumentation process is not running (probably crashed). Check the server log and/or the logcat output for more details
[debug] [W3C (e11936e1)]     at UIA2Proxy.command (C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\jsonwp-proxy\proxy.js:274:13)
[debug] [W3C (e11936e1)]     at processTicksAndRejections (internal/process/task_queues.js:85:5)
[info] [HTTP] <-- POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element 500 6 ms - 886
[info] [HTTP] [info] [HTTP] --> POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element
[info] [HTTP] {"using":"id","value":"com.xiaopeng.oobe:id/view_passistant_text"}
[debug] [W3C (e11936e1)] Calling AppiumDriver.findElement() with args: ["id","com.xiaopeng.oobe:id/view_passistant_text","e11936e1-7fb2-46a9-af60-3e7535ea248b"]
[debug] [BaseDriver] Valid locator strategies for this request: xpath, id, class name, accessibility id, css selector, -android uiautomator
[debug] [BaseDriver] Waiting up to 20000 ms for condition
[debug] [W3C (e11936e1)] Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: 'POST /element' cannot be proxied to UiAutomator2 server because the instrumentation process is not running (probably crashed). Check the server log and/or the logcat output for more details
[debug] [W3C (e11936e1)]     at UIA2Proxy.command (C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\jsonwp-proxy\proxy.js:274:13)
[debug] [W3C (e11936e1)]     at processTicksAndRejections (internal/process/task_queues.js:85:5)
[info] [HTTP] <-- POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element 500 2 ms - 886
[info] [HTTP] [info] [HTTP] --> POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element
[info] [HTTP] {"using":"id","value":"com.xiaopeng.oobe:id/view_passistant_text"}
[debug] [W3C (e11936e1)] Calling AppiumDriver.findElement() with args: ["id","com.xiaopeng.oobe:id/view_passistant_text","e11936e1-7fb2-46a9-af60-3e7535ea248b"]
[debug] [BaseDriver] Valid locator strategies for this request: xpath, id, class name, accessibility id, css selector, -android uiautomator
[debug] [BaseDriver] Waiting up to 20000 ms for condition
[debug] [W3C (e11936e1)] Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: 'POST /element' cannot be proxied to UiAutomator2 server because the instrumentation process is not running (probably crashed). Check the server log and/or the logcat output for more details
[debug] [W3C (e11936e1)]     at UIA2Proxy.command (C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\jsonwp-proxy\proxy.js:274:13)
[debug] [W3C (e11936e1)]     at processTicksAndRejections (internal/process/task_queues.js:85:5)
[info] [HTTP] <-- POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element 500 3 ms - 886
[info] [HTTP] [info] [HTTP] --> POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element
[info] [HTTP] {"using":"id","value":"com.xiaopeng.oobe:id/view_passistant_text"}
[debug] [W3C (e11936e1)] Calling AppiumDriver.findElement() with args: ["id","com.xiaopeng.oobe:id/view_passistant_text","e11936e1-7fb2-46a9-af60-3e7535ea248b"]
[debug] [BaseDriver] Valid locator strategies for this request: xpath, id, class name, accessibility id, css selector, -android uiautomator
[debug] [BaseDriver] Waiting up to 20000 ms for condition
[debug] [W3C (e11936e1)] Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: 'POST /element' cannot be proxied to UiAutomator2 server because the instrumentation process is not running (probably crashed). Check the server log and/or the logcat output for more details
[debug] [W3C (e11936e1)]     at UIA2Proxy.command (C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\jsonwp-proxy\proxy.js:274:13)
[debug] [W3C (e11936e1)]     at processTicksAndRejections (internal/process/task_queues.js:85:5)
[info] [HTTP] <-- POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element 500 6 ms - 886
[info] [HTTP] [info] [HTTP] --> POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element
[info] [HTTP] {"using":"id","value":"com.xiaopeng.oobe:id/view_passistant_text"}
[debug] [W3C (e11936e1)] Calling AppiumDriver.findElement() with args: ["id","com.xiaopeng.oobe:id/view_passistant_text","e11936e1-7fb2-46a9-af60-3e7535ea248b"]
[debug] [BaseDriver] Valid locator strategies for this request: xpath, id, class name, accessibility id, css selector, -android uiautomator
[debug] [BaseDriver] Waiting up to 20000 ms for condition
[debug] [W3C (e11936e1)] Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: 'POST /element' cannot be proxied to UiAutomator2 server because the instrumentation process is not running (probably crashed). Check the server log and/or the logcat output for more details
[debug] [W3C (e11936e1)]     at UIA2Proxy.command (C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\jsonwp-proxy\proxy.js:274:13)
[debug] [W3C (e11936e1)]     at processTicksAndRejections (internal/process/task_queues.js:85:5)
[info] [HTTP] <-- POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element 500 4 ms - 886
[info] [HTTP] [info] [HTTP] --> POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element
[info] [HTTP] {"using":"id","value":"com.xiaopeng.oobe:id/view_passistant_text"}
[debug] [W3C (e11936e1)] Calling AppiumDriver.findElement() with args: ["id","com.xiaopeng.oobe:id/view_passistant_text","e11936e1-7fb2-46a9-af60-3e7535ea248b"]
[debug] [BaseDriver] Valid locator strategies for this request: xpath, id, class name, accessibility id, css selector, -android uiautomator
[debug] [BaseDriver] Waiting up to 20000 ms for condition
[debug] [W3C (e11936e1)] Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: 'POST /element' cannot be proxied to UiAutomator2 server because the instrumentation process is not running (probably crashed). Check the server log and/or the logcat output for more details
[debug] [W3C (e11936e1)]     at UIA2Proxy.command (C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\jsonwp-proxy\proxy.js:274:13)
[debug] [W3C (e11936e1)]     at processTicksAndRejections (internal/process/task_queues.js:85:5)
[info] [HTTP] <-- POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element 500 2 ms - 886
[info] [HTTP] [info] [HTTP] --> POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element
[info] [HTTP] {"using":"id","value":"com.xiaopeng.oobe:id/view_passistant_text"}
[debug] [W3C (e11936e1)] Calling AppiumDriver.findElement() with args: ["id","com.xiaopeng.oobe:id/view_passistant_text","e11936e1-7fb2-46a9-af60-3e7535ea248b"]
[debug] [BaseDriver] Valid locator strategies for this request: xpath, id, class name, accessibility id, css selector, -android uiautomator
[debug] [BaseDriver] Waiting up to 20000 ms for condition
[debug] [W3C (e11936e1)] Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: 'POST /element' cannot be proxied to UiAutomator2 server because the instrumentation process is not running (probably crashed). Check the server log and/or the logcat output for more details
[debug] [W3C (e11936e1)]     at UIA2Proxy.command (C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\jsonwp-proxy\proxy.js:274:13)
[debug] [W3C (e11936e1)]     at processTicksAndRejections (internal/process/task_queues.js:85:5)
[info] [HTTP] <-- POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element 500 1 ms - 886
[info] [HTTP] [info] [HTTP] --> POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element
[info] [HTTP] {"using":"id","value":"com.xiaopeng.oobe:id/view_passistant_text"}
[debug] [W3C (e11936e1)] Calling AppiumDriver.findElement() with args: ["id","com.xiaopeng.oobe:id/view_passistant_text","e11936e1-7fb2-46a9-af60-3e7535ea248b"]
[debug] [BaseDriver] Valid locator strategies for this request: xpath, id, class name, accessibility id, css selector, -android uiautomator
[debug] [BaseDriver] Waiting up to 20000 ms for condition
[debug] [W3C (e11936e1)] Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: 'POST /element' cannot be proxied to UiAutomator2 server because the instrumentation process is not running (probably crashed). Check the server log and/or the logcat output for more details
[debug] [W3C (e11936e1)]     at UIA2Proxy.command (C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\jsonwp-proxy\proxy.js:274:13)
[debug] [W3C (e11936e1)]     at processTicksAndRejections (internal/process/task_queues.js:85:5)
[info] [HTTP] <-- POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element 500 4 ms - 886
[info] [HTTP] [info] [HTTP] --> POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element
[info] [HTTP] {"using":"id","value":"com.xiaopeng.oobe:id/view_passistant_text"}
[debug] [W3C (e11936e1)] Calling AppiumDriver.findElement() with args: ["id","com.xiaopeng.oobe:id/view_passistant_text","e11936e1-7fb2-46a9-af60-3e7535ea248b"]
[debug] [BaseDriver] Valid locator strategies for this request: xpath, id, class name, accessibility id, css selector, -android uiautomator
[debug] [BaseDriver] Waiting up to 20000 ms for condition
[debug] [W3C (e11936e1)] Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: 'POST /element' cannot be proxied to UiAutomator2 server because the instrumentation process is not running (probably crashed). Check the server log and/or the logcat output for more details
[debug] [W3C (e11936e1)]     at UIA2Proxy.command (C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\jsonwp-proxy\proxy.js:274:13)
[debug] [W3C (e11936e1)]     at processTicksAndRejections (internal/process/task_queues.js:85:5)
[info] [HTTP] <-- POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element 500 5 ms - 886
[info] [HTTP] [info] [HTTP] --> POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element
[info] [HTTP] {"using":"id","value":"com.xiaopeng.oobe:id/view_passistant_text"}
[debug] [W3C (e11936e1)] Calling AppiumDriver.findElement() with args: ["id","com.xiaopeng.oobe:id/view_passistant_text","e11936e1-7fb2-46a9-af60-3e7535ea248b"]
[debug] [BaseDriver] Valid locator strategies for this request: xpath, id, class name, accessibility id, css selector, -android uiautomator
[debug] [BaseDriver] Waiting up to 20000 ms for condition
[debug] [W3C (e11936e1)] Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: 'POST /element' cannot be proxied to UiAutomator2 server because the instrumentation process is not running (probably crashed). Check the server log and/or the logcat output for more details
[debug] [W3C (e11936e1)]     at UIA2Proxy.command (C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\jsonwp-proxy\proxy.js:274:13)
[debug] [W3C (e11936e1)]     at processTicksAndRejections (internal/process/task_queues.js:85:5)
[info] [HTTP] <-- POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element 500 6 ms - 886
[info] [HTTP] [info] [HTTP] --> POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element
[info] [HTTP] {"using":"id","value":"com.xiaopeng.oobe:id/view_passistant_text"}
[debug] [W3C (e11936e1)] Calling AppiumDriver.findElement() with args: ["id","com.xiaopeng.oobe:id/view_passistant_text","e11936e1-7fb2-46a9-af60-3e7535ea248b"]
[debug] [BaseDriver] Valid locator strategies for this request: xpath, id, class name, accessibility id, css selector, -android uiautomator
[debug] [BaseDriver] Waiting up to 20000 ms for condition
[debug] [W3C (e11936e1)] Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: 'POST /element' cannot be proxied to UiAutomator2 server because the instrumentation process is not running (probably crashed). Check the server log and/or the logcat output for more details
[debug] [W3C (e11936e1)]     at UIA2Proxy.command (C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\jsonwp-proxy\proxy.js:274:13)
[debug] [W3C (e11936e1)]     at processTicksAndRejections (internal/process/task_queues.js:85:5)
[info] [HTTP] <-- POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element 500 6 ms - 886
[info] [HTTP] [info] [HTTP] --> POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element
[info] [HTTP] {"using":"id","value":"com.xiaopeng.oobe:id/view_passistant_text"}
[debug] [W3C (e11936e1)] Calling AppiumDriver.findElement() with args: ["id","com.xiaopeng.oobe:id/view_passistant_text","e11936e1-7fb2-46a9-af60-3e7535ea248b"]
[debug] [BaseDriver] Valid locator strategies for this request: xpath, id, class name, accessibility id, css selector, -android uiautomator
[debug] [BaseDriver] Waiting up to 20000 ms for condition
[debug] [W3C (e11936e1)] Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: 'POST /element' cannot be proxied to UiAutomator2 server because the instrumentation process is not running (probably crashed). Check the server log and/or the logcat output for more details
[debug] [W3C (e11936e1)]     at UIA2Proxy.command (C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\jsonwp-proxy\proxy.js:274:13)
[debug] [W3C (e11936e1)]     at processTicksAndRejections (internal/process/task_queues.js:85:5)
[info] [HTTP] <-- POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element 500 5 ms - 886
[info] [HTTP] [info] [HTTP] --> POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element
[info] [HTTP] {"using":"id","value":"com.xiaopeng.oobe:id/view_passistant_text"}
[debug] [W3C (e11936e1)] Calling AppiumDriver.findElement() with args: ["id","com.xiaopeng.oobe:id/view_passistant_text","e11936e1-7fb2-46a9-af60-3e7535ea248b"]
[debug] [BaseDriver] Valid locator strategies for this request: xpath, id, class name, accessibility id, css selector, -android uiautomator
[debug] [BaseDriver] Waiting up to 20000 ms for condition
[debug] [W3C (e11936e1)] Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: 'POST /element' cannot be proxied to UiAutomator2 server because the instrumentation process is not running (probably crashed). Check the server log and/or the logcat output for more details
[debug] [W3C (e11936e1)]     at UIA2Proxy.command (C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\jsonwp-proxy\proxy.js:274:13)
[debug] [W3C (e11936e1)]     at processTicksAndRejections (internal/process/task_queues.js:85:5)
[info] [HTTP] <-- POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element 500 6 ms - 886
[info] [HTTP] [info] [HTTP] --> POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element
[info] [HTTP] {"using":"id","value":"com.xiaopeng.oobe:id/view_passistant_text"}
[debug] [W3C (e11936e1)] Calling AppiumDriver.findElement() with args: ["id","com.xiaopeng.oobe:id/view_passistant_text","e11936e1-7fb2-46a9-af60-3e7535ea248b"]
[debug] [BaseDriver] Valid locator strategies for this request: xpath, id, class name, accessibility id, css selector, -android uiautomator
[debug] [BaseDriver] Waiting up to 20000 ms for condition
[debug] [W3C (e11936e1)] Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: 'POST /element' cannot be proxied to UiAutomator2 server because the instrumentation process is not running (probably crashed). Check the server log and/or the logcat output for more details
[debug] [W3C (e11936e1)]     at UIA2Proxy.command (C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\jsonwp-proxy\proxy.js:274:13)
[debug] [W3C (e11936e1)]     at processTicksAndRejections (internal/process/task_queues.js:85:5)
[info] [HTTP] <-- POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element 500 6 ms - 886
[info] [HTTP] [info] [HTTP] --> POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element
[info] [HTTP] {"using":"id","value":"com.xiaopeng.oobe:id/view_passistant_text"}
[debug] [W3C (e11936e1)] Calling AppiumDriver.findElement() with args: ["id","com.xiaopeng.oobe:id/view_passistant_text","e11936e1-7fb2-46a9-af60-3e7535ea248b"]
[debug] [BaseDriver] Valid locator strategies for this request: xpath, id, class name, accessibility id, css selector, -android uiautomator
[debug] [BaseDriver] Waiting up to 20000 ms for condition
[debug] [W3C (e11936e1)] Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: 'POST /element' cannot be proxied to UiAutomator2 server because the instrumentation process is not running (probably crashed). Check the server log and/or the logcat output for more details
[debug] [W3C (e11936e1)]     at UIA2Proxy.command (C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\jsonwp-proxy\proxy.js:274:13)
[debug] [W3C (e11936e1)]     at processTicksAndRejections (internal/process/task_queues.js:85:5)
[info] [HTTP] <-- POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element 500 6 ms - 886
[info] [HTTP] [info] [HTTP] --> POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element
[info] [HTTP] {"using":"id","value":"com.xiaopeng.oobe:id/view_passistant_text"}
[debug] [W3C (e11936e1)] Calling AppiumDriver.findElement() with args: ["id","com.xiaopeng.oobe:id/view_passistant_text","e11936e1-7fb2-46a9-af60-3e7535ea248b"]
[debug] [BaseDriver] Valid locator strategies for this request: xpath, id, class name, accessibility id, css selector, -android uiautomator
[debug] [BaseDriver] Waiting up to 20000 ms for condition
[debug] [W3C (e11936e1)] Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: 'POST /element' cannot be proxied to UiAutomator2 server because the instrumentation process is not running (probably crashed). Check the server log and/or the logcat output for more details
[debug] [W3C (e11936e1)]     at UIA2Proxy.command (C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\jsonwp-proxy\proxy.js:274:13)
[debug] [W3C (e11936e1)]     at processTicksAndRejections (internal/process/task_queues.js:85:5)
[info] [HTTP] <-- POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element 500 8 ms - 886
[info] [HTTP] [info] [HTTP] --> POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element
[info] [HTTP] {"using":"id","value":"com.xiaopeng.oobe:id/view_passistant_text"}
[debug] [W3C (e11936e1)] Calling AppiumDriver.findElement() with args: ["id","com.xiaopeng.oobe:id/view_passistant_text","e11936e1-7fb2-46a9-af60-3e7535ea248b"]
[debug] [BaseDriver] Valid locator strategies for this request: xpath, id, class name, accessibility id, css selector, -android uiautomator
[debug] [BaseDriver] Waiting up to 20000 ms for condition
[debug] [W3C (e11936e1)] Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: 'POST /element' cannot be proxied to UiAutomator2 server because the instrumentation process is not running (probably crashed). Check the server log and/or the logcat output for more details
[debug] [W3C (e11936e1)]     at UIA2Proxy.command (C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\jsonwp-proxy\proxy.js:274:13)
[debug] [W3C (e11936e1)]     at processTicksAndRejections (internal/process/task_queues.js:85:5)
[info] [HTTP] <-- POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element 500 6 ms - 886
[info] [HTTP] [info] [HTTP] --> POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element
[info] [HTTP] {"using":"id","value":"com.xiaopeng.oobe:id/view_passistant_text"}
[debug] [W3C (e11936e1)] Calling AppiumDriver.findElement() with args: ["id","com.xiaopeng.oobe:id/view_passistant_text","e11936e1-7fb2-46a9-af60-3e7535ea248b"]
[debug] [BaseDriver] Valid locator strategies for this request: xpath, id, class name, accessibility id, css selector, -android uiautomator
[debug] [BaseDriver] Waiting up to 20000 ms for condition
[debug] [W3C (e11936e1)] Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: 'POST /element' cannot be proxied to UiAutomator2 server because the instrumentation process is not running (probably crashed). Check the server log and/or the logcat output for more details
[debug] [W3C (e11936e1)]     at UIA2Proxy.command (C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\jsonwp-proxy\proxy.js:274:13)
[debug] [W3C (e11936e1)]     at processTicksAndRejections (internal/process/task_queues.js:85:5)
[info] [HTTP] <-- POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element 500 7 ms - 886
[info] [HTTP] [info] [HTTP] --> POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element
[info] [HTTP] {"using":"id","value":"com.xiaopeng.oobe:id/view_passistant_text"}
[debug] [W3C (e11936e1)] Calling AppiumDriver.findElement() with args: ["id","com.xiaopeng.oobe:id/view_passistant_text","e11936e1-7fb2-46a9-af60-3e7535ea248b"]
[debug] [BaseDriver] Valid locator strategies for this request: xpath, id, class name, accessibility id, css selector, -android uiautomator
[debug] [BaseDriver] Waiting up to 20000 ms for condition
[debug] [W3C (e11936e1)] Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: 'POST /element' cannot be proxied to UiAutomator2 server because the instrumentation process is not running (probably crashed). Check the server log and/or the logcat output for more details
[debug] [W3C (e11936e1)]     at UIA2Proxy.command (C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\jsonwp-proxy\proxy.js:274:13)
[debug] [W3C (e11936e1)]     at processTicksAndRejections (internal/process/task_queues.js:85:5)
[info] [HTTP] <-- POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element 500 7 ms - 886
[info] [HTTP] [info] [HTTP] --> POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element
[info] [HTTP] {"using":"id","value":"com.xiaopeng.oobe:id/view_passistant_text"}
[debug] [W3C (e11936e1)] Calling AppiumDriver.findElement() with args: ["id","com.xiaopeng.oobe:id/view_passistant_text","e11936e1-7fb2-46a9-af60-3e7535ea248b"]
[debug] [BaseDriver] Valid locator strategies for this request: xpath, id, class name, accessibility id, css selector, -android uiautomator
[debug] [BaseDriver] Waiting up to 20000 ms for condition
[debug] [W3C (e11936e1)] Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: 'POST /element' cannot be proxied to UiAutomator2 server because the instrumentation process is not running (probably crashed). Check the server log and/or the logcat output for more details
[debug] [W3C (e11936e1)]     at UIA2Proxy.command (C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\jsonwp-proxy\proxy.js:274:13)
[debug] [W3C (e11936e1)]     at processTicksAndRejections (internal/process/task_queues.js:85:5)
[info] [HTTP] <-- POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element 500 3 ms - 886
[info] [HTTP] [info] [HTTP] --> POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element
[info] [HTTP] {"using":"id","value":"com.xiaopeng.oobe:id/view_passistant_text"}
[debug] [W3C (e11936e1)] Calling AppiumDriver.findElement() with args: ["id","com.xiaopeng.oobe:id/view_passistant_text","e11936e1-7fb2-46a9-af60-3e7535ea248b"]
[debug] [BaseDriver] Valid locator strategies for this request: xpath, id, class name, accessibility id, css selector, -android uiautomator
[debug] [BaseDriver] Waiting up to 20000 ms for condition
[debug] [W3C (e11936e1)] Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: 'POST /element' cannot be proxied to UiAutomator2 server because the instrumentation process is not running (probably crashed). Check the server log and/or the logcat output for more details
[debug] [W3C (e11936e1)]     at UIA2Proxy.command (C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\jsonwp-proxy\proxy.js:274:13)
[debug] [W3C (e11936e1)]     at processTicksAndRejections (internal/process/task_queues.js:85:5)
[info] [HTTP] <-- POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element 500 6 ms - 886
[info] [HTTP] [info] [HTTP] --> POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element
[info] [HTTP] {"using":"id","value":"com.xiaopeng.oobe:id/view_passistant_text"}
[debug] [W3C (e11936e1)] Calling AppiumDriver.findElement() with args: ["id","com.xiaopeng.oobe:id/view_passistant_text","e11936e1-7fb2-46a9-af60-3e7535ea248b"]
[debug] [BaseDriver] Valid locator strategies for this request: xpath, id, class name, accessibility id, css selector, -android uiautomator
[debug] [BaseDriver] Waiting up to 20000 ms for condition
[debug] [W3C (e11936e1)] Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: 'POST /element' cannot be proxied to UiAutomator2 server because the instrumentation process is not running (probably crashed). Check the server log and/or the logcat output for more details
[debug] [W3C (e11936e1)]     at UIA2Proxy.command (C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\jsonwp-proxy\proxy.js:274:13)
[debug] [W3C (e11936e1)]     at processTicksAndRejections (internal/process/task_queues.js:85:5)
[info] [HTTP] <-- POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element 500 6 ms - 886
[info] [HTTP] [info] [HTTP] --> POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element
[info] [HTTP] {"using":"id","value":"com.xiaopeng.oobe:id/view_passistant_text"}
[debug] [W3C (e11936e1)] Calling AppiumDriver.findElement() with args: ["id","com.xiaopeng.oobe:id/view_passistant_text","e11936e1-7fb2-46a9-af60-3e7535ea248b"]
[debug] [BaseDriver] Valid locator strategies for this request: xpath, id, class name, accessibility id, css selector, -android uiautomator
[debug] [BaseDriver] Waiting up to 20000 ms for condition
[debug] [W3C (e11936e1)] Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: 'POST /element' cannot be proxied to UiAutomator2 server because the instrumentation process is not running (probably crashed). Check the server log and/or the logcat output for more details
[debug] [W3C (e11936e1)]     at UIA2Proxy.command (C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\jsonwp-proxy\proxy.js:274:13)
[debug] [W3C (e11936e1)]     at processTicksAndRejections (internal/process/task_queues.js:85:5)
[info] [HTTP] <-- POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element 500 6 ms - 886
[info] [HTTP] [info] [HTTP] --> POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element
[info] [HTTP] {"using":"id","value":"com.xiaopeng.oobe:id/view_passistant_text"}
[debug] [W3C (e11936e1)] Calling AppiumDriver.findElement() with args: ["id","com.xiaopeng.oobe:id/view_passistant_text","e11936e1-7fb2-46a9-af60-3e7535ea248b"]
[debug] [BaseDriver] Valid locator strategies for this request: xpath, id, class name, accessibility id, css selector, -android uiautomator
[debug] [BaseDriver] Waiting up to 20000 ms for condition
[debug] [W3C (e11936e1)] Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: 'POST /element' cannot be proxied to UiAutomator2 server because the instrumentation process is not running (probably crashed). Check the server log and/or the logcat output for more details
[debug] [W3C (e11936e1)]     at UIA2Proxy.command (C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\jsonwp-proxy\proxy.js:274:13)
[debug] [W3C (e11936e1)]     at processTicksAndRejections (internal/process/task_queues.js:85:5)
[info] [HTTP] <-- POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element 500 6 ms - 886
[info] [HTTP] [info] [HTTP] --> POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element
[info] [HTTP] {"using":"id","value":"com.xiaopeng.oobe:id/view_passistant_text"}
[debug] [W3C (e11936e1)] Calling AppiumDriver.findElement() with args: ["id","com.xiaopeng.oobe:id/view_passistant_text","e11936e1-7fb2-46a9-af60-3e7535ea248b"]
[debug] [BaseDriver] Valid locator strategies for this request: xpath, id, class name, accessibility id, css selector, -android uiautomator
[debug] [BaseDriver] Waiting up to 20000 ms for condition
[debug] [W3C (e11936e1)] Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: 'POST /element' cannot be proxied to UiAutomator2 server because the instrumentation process is not running (probably crashed). Check the server log and/or the logcat output for more details
[debug] [W3C (e11936e1)]     at UIA2Proxy.command (C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\jsonwp-proxy\proxy.js:274:13)
[debug] [W3C (e11936e1)]     at processTicksAndRejections (internal/process/task_queues.js:85:5)
[info] [HTTP] <-- POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element 500 1 ms - 886
[info] [HTTP] [info] [HTTP] --> POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element
[info] [HTTP] {"using":"id","value":"com.xiaopeng.oobe:id/view_passistant_text"}
[debug] [W3C (e11936e1)] Calling AppiumDriver.findElement() with args: ["id","com.xiaopeng.oobe:id/view_passistant_text","e11936e1-7fb2-46a9-af60-3e7535ea248b"]
[debug] [BaseDriver] Valid locator strategies for this request: xpath, id, class name, accessibility id, css selector, -android uiautomator
[debug] [BaseDriver] Waiting up to 20000 ms for condition
[debug] [W3C (e11936e1)] Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: 'POST /element' cannot be proxied to UiAutomator2 server because the instrumentation process is not running (probably crashed). Check the server log and/or the logcat output for more details
[debug] [W3C (e11936e1)]     at UIA2Proxy.command (C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\jsonwp-proxy\proxy.js:274:13)
[debug] [W3C (e11936e1)]     at processTicksAndRejections (internal/process/task_queues.js:85:5)
[info] [HTTP] <-- POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element 500 6 ms - 886
[info] [HTTP] [info] [HTTP] --> POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element
[info] [HTTP] {"using":"id","value":"com.xiaopeng.oobe:id/view_passistant_text"}
[debug] [W3C (e11936e1)] Calling AppiumDriver.findElement() with args: ["id","com.xiaopeng.oobe:id/view_passistant_text","e11936e1-7fb2-46a9-af60-3e7535ea248b"]
[debug] [BaseDriver] Valid locator strategies for this request: xpath, id, class name, accessibility id, css selector, -android uiautomator
[debug] [BaseDriver] Waiting up to 20000 ms for condition
[debug] [W3C (e11936e1)] Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: 'POST /element' cannot be proxied to UiAutomator2 server because the instrumentation process is not running (probably crashed). Check the server log and/or the logcat output for more details
[debug] [W3C (e11936e1)]     at UIA2Proxy.command (C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\jsonwp-proxy\proxy.js:274:13)
[debug] [W3C (e11936e1)]     at processTicksAndRejections (internal/process/task_queues.js:85:5)
[info] [HTTP] <-- POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element 500 3 ms - 886
[info] [HTTP] [info] [HTTP] --> POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element
[info] [HTTP] {"using":"id","value":"com.xiaopeng.oobe:id/view_passistant_text"}
[debug] [W3C (e11936e1)] Calling AppiumDriver.findElement() with args: ["id","com.xiaopeng.oobe:id/view_passistant_text","e11936e1-7fb2-46a9-af60-3e7535ea248b"]
[debug] [BaseDriver] Valid locator strategies for this request: xpath, id, class name, accessibility id, css selector, -android uiautomator
[debug] [BaseDriver] Waiting up to 20000 ms for condition
[debug] [W3C (e11936e1)] Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: 'POST /element' cannot be proxied to UiAutomator2 server because the instrumentation process is not running (probably crashed). Check the server log and/or the logcat output for more details
[debug] [W3C (e11936e1)]     at UIA2Proxy.command (C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\jsonwp-proxy\proxy.js:274:13)
[debug] [W3C (e11936e1)]     at processTicksAndRejections (internal/process/task_queues.js:85:5)
[info] [HTTP] <-- POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element 500 2 ms - 886
[info] [HTTP] [info] [HTTP] --> POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element
[info] [HTTP] {"using":"id","value":"com.xiaopeng.oobe:id/view_passistant_text"}
[debug] [W3C (e11936e1)] Calling AppiumDriver.findElement() with args: ["id","com.xiaopeng.oobe:id/view_passistant_text","e11936e1-7fb2-46a9-af60-3e7535ea248b"]
[debug] [BaseDriver] Valid locator strategies for this request: xpath, id, class name, accessibility id, css selector, -android uiautomator
[debug] [BaseDriver] Waiting up to 20000 ms for condition
[debug] [W3C (e11936e1)] Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: 'POST /element' cannot be proxied to UiAutomator2 server because the instrumentation process is not running (probably crashed). Check the server log and/or the logcat output for more details
[debug] [W3C (e11936e1)]     at UIA2Proxy.command (C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\jsonwp-proxy\proxy.js:274:13)
[debug] [W3C (e11936e1)]     at processTicksAndRejections (internal/process/task_queues.js:85:5)
[info] [HTTP] <-- POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element 500 1 ms - 886
[info] [HTTP] [info] [HTTP] --> POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element
[info] [HTTP] {"using":"id","value":"com.xiaopeng.oobe:id/view_passistant_text"}
[debug] [W3C (e11936e1)] Calling AppiumDriver.findElement() with args: ["id","com.xiaopeng.oobe:id/view_passistant_text","e11936e1-7fb2-46a9-af60-3e7535ea248b"]
[debug] [BaseDriver] Valid locator strategies for this request: xpath, id, class name, accessibility id, css selector, -android uiautomator
[debug] [BaseDriver] Waiting up to 20000 ms for condition
[debug] [W3C (e11936e1)] Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: 'POST /element' cannot be proxied to UiAutomator2 server because the instrumentation process is not running (probably crashed). Check the server log and/or the logcat output for more details
[debug] [W3C (e11936e1)]     at UIA2Proxy.command (C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\jsonwp-proxy\proxy.js:274:13)
[debug] [W3C (e11936e1)]     at processTicksAndRejections (internal/process/task_queues.js:85:5)
[info] [HTTP] <-- POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element 500 2 ms - 886
[info] [HTTP] [info] [HTTP] --> POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element
[info] [HTTP] {"using":"id","value":"com.xiaopeng.oobe:id/view_passistant_text"}
[debug] [W3C (e11936e1)] Calling AppiumDriver.findElement() with args: ["id","com.xiaopeng.oobe:id/view_passistant_text","e11936e1-7fb2-46a9-af60-3e7535ea248b"]
[debug] [BaseDriver] Valid locator strategies for this request: xpath, id, class name, accessibility id, css selector, -android uiautomator
[debug] [BaseDriver] Waiting up to 20000 ms for condition
[debug] [W3C (e11936e1)] Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: 'POST /element' cannot be proxied to UiAutomator2 server because the instrumentation process is not running (probably crashed). Check the server log and/or the logcat output for more details
[debug] [W3C (e11936e1)]     at UIA2Proxy.command (C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\jsonwp-proxy\proxy.js:274:13)
[debug] [W3C (e11936e1)]     at processTicksAndRejections (internal/process/task_queues.js:85:5)
[info] [HTTP] <-- POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element 500 6 ms - 886
[info] [HTTP] [info] [HTTP] --> POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element
[info] [HTTP] {"using":"id","value":"com.xiaopeng.oobe:id/view_passistant_text"}
[debug] [W3C (e11936e1)] Calling AppiumDriver.findElement() with args: ["id","com.xiaopeng.oobe:id/view_passistant_text","e11936e1-7fb2-46a9-af60-3e7535ea248b"]
[debug] [BaseDriver] Valid locator strategies for this request: xpath, id, class name, accessibility id, css selector, -android uiautomator
[debug] [BaseDriver] Waiting up to 20000 ms for condition
[debug] [W3C (e11936e1)] Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: 'POST /element' cannot be proxied to UiAutomator2 server because the instrumentation process is not running (probably crashed). Check the server log and/or the logcat output for more details
[debug] [W3C (e11936e1)]     at UIA2Proxy.command (C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\jsonwp-proxy\proxy.js:274:13)
[debug] [W3C (e11936e1)]     at processTicksAndRejections (internal/process/task_queues.js:85:5)
[info] [HTTP] <-- POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element 500 6 ms - 886
[info] [HTTP] [info] [HTTP] --> POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element
[info] [HTTP] {"using":"id","value":"com.xiaopeng.oobe:id/view_passistant_text"}
[debug] [W3C (e11936e1)] Calling AppiumDriver.findElement() with args: ["id","com.xiaopeng.oobe:id/view_passistant_text","e11936e1-7fb2-46a9-af60-3e7535ea248b"]
[debug] [BaseDriver] Valid locator strategies for this request: xpath, id, class name, accessibility id, css selector, -android uiautomator
[debug] [BaseDriver] Waiting up to 20000 ms for condition
[debug] [W3C (e11936e1)] Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: 'POST /element' cannot be proxied to UiAutomator2 server because the instrumentation process is not running (probably crashed). Check the server log and/or the logcat output for more details
[debug] [W3C (e11936e1)]     at UIA2Proxy.command (C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\jsonwp-proxy\proxy.js:274:13)
[debug] [W3C (e11936e1)]     at processTicksAndRejections (internal/process/task_queues.js:85:5)
[info] [HTTP] <-- POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element 500 6 ms - 886
[info] [HTTP] [info] [HTTP] --> POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element
[info] [HTTP] {"using":"id","value":"com.xiaopeng.oobe:id/view_passistant_text"}
[debug] [W3C (e11936e1)] Calling AppiumDriver.findElement() with args: ["id","com.xiaopeng.oobe:id/view_passistant_text","e11936e1-7fb2-46a9-af60-3e7535ea248b"]
[debug] [BaseDriver] Valid locator strategies for this request: xpath, id, class name, accessibility id, css selector, -android uiautomator
[debug] [BaseDriver] Waiting up to 20000 ms for condition
[debug] [W3C (e11936e1)] Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: 'POST /element' cannot be proxied to UiAutomator2 server because the instrumentation process is not running (probably crashed). Check the server log and/or the logcat output for more details
[debug] [W3C (e11936e1)]     at UIA2Proxy.command (C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\jsonwp-proxy\proxy.js:274:13)
[debug] [W3C (e11936e1)]     at processTicksAndRejections (internal/process/task_queues.js:85:5)
[info] [HTTP] <-- POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element 500 6 ms - 886
[info] [HTTP] [info] [HTTP] --> POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element
[info] [HTTP] {"using":"id","value":"com.xiaopeng.oobe:id/view_passistant_text"}
[debug] [W3C (e11936e1)] Calling AppiumDriver.findElement() with args: ["id","com.xiaopeng.oobe:id/view_passistant_text","e11936e1-7fb2-46a9-af60-3e7535ea248b"]
[debug] [BaseDriver] Valid locator strategies for this request: xpath, id, class name, accessibility id, css selector, -android uiautomator
[debug] [BaseDriver] Waiting up to 20000 ms for condition
[debug] [W3C (e11936e1)] Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: 'POST /element' cannot be proxied to UiAutomator2 server because the instrumentation process is not running (probably crashed). Check the server log and/or the logcat output for more details
[debug] [W3C (e11936e1)]     at UIA2Proxy.command (C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\jsonwp-proxy\proxy.js:274:13)
[debug] [W3C (e11936e1)]     at processTicksAndRejections (internal/process/task_queues.js:85:5)
[info] [HTTP] <-- POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element 500 6 ms - 886
[info] [HTTP] [info] [HTTP] --> POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element
[info] [HTTP] {"using":"id","value":"com.xiaopeng.oobe:id/view_passistant_text"}
[debug] [W3C (e11936e1)] Calling AppiumDriver.findElement() with args: ["id","com.xiaopeng.oobe:id/view_passistant_text","e11936e1-7fb2-46a9-af60-3e7535ea248b"]
[debug] [BaseDriver] Valid locator strategies for this request: xpath, id, class name, accessibility id, css selector, -android uiautomator
[debug] [BaseDriver] Waiting up to 20000 ms for condition
[debug] [W3C (e11936e1)] Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: 'POST /element' cannot be proxied to UiAutomator2 server because the instrumentation process is not running (probably crashed). Check the server log and/or the logcat output for more details
[debug] [W3C (e11936e1)]     at UIA2Proxy.command (C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\jsonwp-proxy\proxy.js:274:13)
[debug] [W3C (e11936e1)]     at processTicksAndRejections (internal/process/task_queues.js:85:5)
[info] [HTTP] <-- POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element 500 4 ms - 886
[info] [HTTP] [info] [HTTP] --> POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element
[info] [HTTP] {"using":"id","value":"com.xiaopeng.oobe:id/view_passistant_text"}
[debug] [W3C (e11936e1)] Calling AppiumDriver.findElement() with args: ["id","com.xiaopeng.oobe:id/view_passistant_text","e11936e1-7fb2-46a9-af60-3e7535ea248b"]
[debug] [BaseDriver] Valid locator strategies for this request: xpath, id, class name, accessibility id, css selector, -android uiautomator
[debug] [BaseDriver] Waiting up to 20000 ms for condition
[debug] [W3C (e11936e1)] Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: 'POST /element' cannot be proxied to UiAutomator2 server because the instrumentation process is not running (probably crashed). Check the server log and/or the logcat output for more details
[debug] [W3C (e11936e1)]     at UIA2Proxy.command (C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\jsonwp-proxy\proxy.js:274:13)
[debug] [W3C (e11936e1)]     at processTicksAndRejections (internal/process/task_queues.js:85:5)
[info] [HTTP] <-- POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element 500 6 ms - 886
[info] [HTTP] [info] [HTTP] --> POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element
[info] [HTTP] {"using":"id","value":"com.xiaopeng.oobe:id/view_passistant_text"}
[debug] [W3C (e11936e1)] Calling AppiumDriver.findElement() with args: ["id","com.xiaopeng.oobe:id/view_passistant_text","e11936e1-7fb2-46a9-af60-3e7535ea248b"]
[debug] [BaseDriver] Valid locator strategies for this request: xpath, id, class name, accessibility id, css selector, -android uiautomator
[debug] [BaseDriver] Waiting up to 20000 ms for condition
[debug] [W3C (e11936e1)] Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: 'POST /element' cannot be proxied to UiAutomator2 server because the instrumentation process is not running (probably crashed). Check the server log and/or the logcat output for more details
[debug] [W3C (e11936e1)]     at UIA2Proxy.command (C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\jsonwp-proxy\proxy.js:274:13)
[debug] [W3C (e11936e1)]     at processTicksAndRejections (internal/process/task_queues.js:85:5)
[info] [HTTP] <-- POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element 500 7 ms - 886
[info] [HTTP] [info] [HTTP] --> POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element
[info] [HTTP] {"using":"id","value":"com.xiaopeng.oobe:id/view_passistant_text"}
[debug] [W3C (e11936e1)] Calling AppiumDriver.findElement() with args: ["id","com.xiaopeng.oobe:id/view_passistant_text","e11936e1-7fb2-46a9-af60-3e7535ea248b"]
[debug] [BaseDriver] Valid locator strategies for this request: xpath, id, class name, accessibility id, css selector, -android uiautomator
[debug] [BaseDriver] Waiting up to 20000 ms for condition
[debug] [W3C (e11936e1)] Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: 'POST /element' cannot be proxied to UiAutomator2 server because the instrumentation process is not running (probably crashed). Check the server log and/or the logcat output for more details
[debug] [W3C (e11936e1)]     at UIA2Proxy.command (C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\jsonwp-proxy\proxy.js:274:13)
[debug] [W3C (e11936e1)]     at processTicksAndRejections (internal/process/task_queues.js:85:5)
[info] [HTTP] <-- POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element 500 7 ms - 886
[info] [HTTP] [info] [HTTP] --> POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element
[info] [HTTP] {"using":"id","value":"com.xiaopeng.oobe:id/view_passistant_text"}
[debug] [W3C (e11936e1)] Calling AppiumDriver.findElement() with args: ["id","com.xiaopeng.oobe:id/view_passistant_text","e11936e1-7fb2-46a9-af60-3e7535ea248b"]
[debug] [BaseDriver] Valid locator strategies for this request: xpath, id, class name, accessibility id, css selector, -android uiautomator
[debug] [BaseDriver] Waiting up to 20000 ms for condition
[debug] [W3C (e11936e1)] Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: 'POST /element' cannot be proxied to UiAutomator2 server because the instrumentation process is not running (probably crashed). Check the server log and/or the logcat output for more details
[debug] [W3C (e11936e1)]     at UIA2Proxy.command (C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\jsonwp-proxy\proxy.js:274:13)
[debug] [W3C (e11936e1)]     at processTicksAndRejections (internal/process/task_queues.js:85:5)
[info] [HTTP] <-- POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element 500 7 ms - 886
[info] [HTTP] [info] [HTTP] --> POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element
[info] [HTTP] {"using":"id","value":"com.xiaopeng.oobe:id/view_passistant_text"}
[debug] [W3C (e11936e1)] Calling AppiumDriver.findElement() with args: ["id","com.xiaopeng.oobe:id/view_passistant_text","e11936e1-7fb2-46a9-af60-3e7535ea248b"]
[debug] [BaseDriver] Valid locator strategies for this request: xpath, id, class name, accessibility id, css selector, -android uiautomator
[debug] [BaseDriver] Waiting up to 20000 ms for condition
[debug] [W3C (e11936e1)] Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: 'POST /element' cannot be proxied to UiAutomator2 server because the instrumentation process is not running (probably crashed). Check the server log and/or the logcat output for more details
[debug] [W3C (e11936e1)]     at UIA2Proxy.command (C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\jsonwp-proxy\proxy.js:274:13)
[debug] [W3C (e11936e1)]     at processTicksAndRejections (internal/process/task_queues.js:85:5)
[info] [HTTP] <-- POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element 500 4 ms - 886
[info] [HTTP] [info] [HTTP] --> POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element
[info] [HTTP] {"using":"id","value":"com.xiaopeng.oobe:id/view_passistant_text"}
[debug] [W3C (e11936e1)] Calling AppiumDriver.findElement() with args: ["id","com.xiaopeng.oobe:id/view_passistant_text","e11936e1-7fb2-46a9-af60-3e7535ea248b"]
[debug] [BaseDriver] Valid locator strategies for this request: xpath, id, class name, accessibility id, css selector, -android uiautomator
[debug] [BaseDriver] Waiting up to 20000 ms for condition
[debug] [W3C (e11936e1)] Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: 'POST /element' cannot be proxied to UiAutomator2 server because the instrumentation process is not running (probably crashed). Check the server log and/or the logcat output for more details
[debug] [W3C (e11936e1)]     at UIA2Proxy.command (C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\jsonwp-proxy\proxy.js:274:13)
[debug] [W3C (e11936e1)]     at processTicksAndRejections (internal/process/task_queues.js:85:5)
[info] [HTTP] <-- POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element 500 1 ms - 886
[info] [HTTP] [info] [HTTP] --> POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element
[info] [HTTP] {"using":"id","value":"com.xiaopeng.oobe:id/view_passistant_text"}
[debug] [W3C (e11936e1)] Calling AppiumDriver.findElement() with args: ["id","com.xiaopeng.oobe:id/view_passistant_text","e11936e1-7fb2-46a9-af60-3e7535ea248b"]
[debug] [BaseDriver] Valid locator strategies for this request: xpath, id, class name, accessibility id, css selector, -android uiautomator
[debug] [BaseDriver] Waiting up to 20000 ms for condition
[debug] [W3C (e11936e1)] Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: 'POST /element' cannot be proxied to UiAutomator2 server because the instrumentation process is not running (probably crashed). Check the server log and/or the logcat output for more details
[debug] [W3C (e11936e1)]     at UIA2Proxy.command (C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\jsonwp-proxy\proxy.js:274:13)
[debug] [W3C (e11936e1)]     at processTicksAndRejections (internal/process/task_queues.js:85:5)
[info] [HTTP] <-- POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element 500 4 ms - 886
[info] [HTTP] [info] [HTTP] --> POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element
[info] [HTTP] {"using":"id","value":"com.xiaopeng.oobe:id/view_passistant_text"}
[debug] [W3C (e11936e1)] Calling AppiumDriver.findElement() with args: ["id","com.xiaopeng.oobe:id/view_passistant_text","e11936e1-7fb2-46a9-af60-3e7535ea248b"]
[debug] [BaseDriver] Valid locator strategies for this request: xpath, id, class name, accessibility id, css selector, -android uiautomator
[debug] [BaseDriver] Waiting up to 20000 ms for condition
[debug] [W3C (e11936e1)] Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: 'POST /element' cannot be proxied to UiAutomator2 server because the instrumentation process is not running (probably crashed). Check the server log and/or the logcat output for more details
[debug] [W3C (e11936e1)]     at UIA2Proxy.command (C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\jsonwp-proxy\proxy.js:274:13)
[debug] [W3C (e11936e1)]     at processTicksAndRejections (internal/process/task_queues.js:85:5)
[info] [HTTP] <-- POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element 500 2 ms - 886
[info] [HTTP] [info] [HTTP] --> POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element
[info] [HTTP] {"using":"id","value":"com.xiaopeng.oobe:id/view_passistant_text"}
[debug] [W3C (e11936e1)] Calling AppiumDriver.findElement() with args: ["id","com.xiaopeng.oobe:id/view_passistant_text","e11936e1-7fb2-46a9-af60-3e7535ea248b"]
[debug] [BaseDriver] Valid locator strategies for this request: xpath, id, class name, accessibility id, css selector, -android uiautomator
[debug] [BaseDriver] Waiting up to 20000 ms for condition
[debug] [W3C (e11936e1)] Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: 'POST /element' cannot be proxied to UiAutomator2 server because the instrumentation process is not running (probably crashed). Check the server log and/or the logcat output for more details
[debug] [W3C (e11936e1)]     at UIA2Proxy.command (C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\jsonwp-proxy\proxy.js:274:13)
[debug] [W3C (e11936e1)]     at processTicksAndRejections (internal/process/task_queues.js:85:5)
[info] [HTTP] <-- POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element 500 1 ms - 886
[info] [HTTP] [info] [HTTP] --> POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element
[info] [HTTP] {"using":"id","value":"com.xiaopeng.oobe:id/view_passistant_text"}
[debug] [W3C (e11936e1)] Calling AppiumDriver.findElement() with args: ["id","com.xiaopeng.oobe:id/view_passistant_text","e11936e1-7fb2-46a9-af60-3e7535ea248b"]
[debug] [BaseDriver] Valid locator strategies for this request: xpath, id, class name, accessibility id, css selector, -android uiautomator
[debug] [BaseDriver] Waiting up to 20000 ms for condition
[debug] [W3C (e11936e1)] Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: 'POST /element' cannot be proxied to UiAutomator2 server because the instrumentation process is not running (probably crashed). Check the server log and/or the logcat output for more details
[debug] [W3C (e11936e1)]     at UIA2Proxy.command (C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\jsonwp-proxy\proxy.js:274:13)
[debug] [W3C (e11936e1)]     at processTicksAndRejections (internal/process/task_queues.js:85:5)
[info] [HTTP] <-- POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element 500 3 ms - 886
[info] [HTTP] [info] [HTTP] --> POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element
[info] [HTTP] {"using":"id","value":"com.xiaopeng.oobe:id/view_passistant_text"}
[debug] [W3C (e11936e1)] Calling AppiumDriver.findElement() with args: ["id","com.xiaopeng.oobe:id/view_passistant_text","e11936e1-7fb2-46a9-af60-3e7535ea248b"]
[debug] [BaseDriver] Valid locator strategies for this request: xpath, id, class name, accessibility id, css selector, -android uiautomator
[debug] [BaseDriver] Waiting up to 20000 ms for condition
[debug] [W3C (e11936e1)] Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: 'POST /element' cannot be proxied to UiAutomator2 server because the instrumentation process is not running (probably crashed). Check the server log and/or the logcat output for more details
[debug] [W3C (e11936e1)]     at UIA2Proxy.command (C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\jsonwp-proxy\proxy.js:274:13)
[debug] [W3C (e11936e1)]     at processTicksAndRejections (internal/process/task_queues.js:85:5)
[info] [HTTP] <-- POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element 500 1 ms - 886
[info] [HTTP] [info] [HTTP] --> POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element
[info] [HTTP] {"using":"id","value":"com.xiaopeng.oobe:id/view_passistant_text"}
[debug] [W3C (e11936e1)] Calling AppiumDriver.findElement() with args: ["id","com.xiaopeng.oobe:id/view_passistant_text","e11936e1-7fb2-46a9-af60-3e7535ea248b"]
[debug] [BaseDriver] Valid locator strategies for this request: xpath, id, class name, accessibility id, css selector, -android uiautomator
[debug] [BaseDriver] Waiting up to 20000 ms for condition
[debug] [W3C (e11936e1)] Encountered internal error running command: UnknownError: An unknown server-side error occurred while processing the command. Original error: 'POST /element' cannot be proxied to UiAutomator2 server because the instrumentation process is not running (probably crashed). Check the server log and/or the logcat output for more details
[debug] [W3C (e11936e1)]     at UIA2Proxy.command (C:\Users\Xpeng\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-base-driver\lib\jsonwp-proxy\proxy.js:274:13)
[debug] [W3C (e11936e1)]     at processTicksAndRejections (internal/process/task_queues.js:85:5)
[info] [HTTP] <-- POST /wd/hub/session/e11936e1-7fb2-46a9-af60-3e7535ea248b/element 500 7 ms - 886
[info] [HTTP]