Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Error: The instrumentation process cannot be initialized. #12607

Closed
reinaldorossetti opened this issue May 8, 2019 · 24 comments
Closed

Error: The instrumentation process cannot be initialized. #12607

reinaldorossetti opened this issue May 8, 2019 · 24 comments
Labels
UIAutomator2 specific to uiautomator2 driver

Comments

@reinaldorossetti
Copy link

reinaldorossetti commented May 8, 2019 •
edited

The problem

I'm have this error in appium version 1.11 upper, in version 1.10.1 works very well, the same error in windows, linux and mac.

Error: The instrumentation process cannot be initialized. Make sure the application under test does not crash and investigate the logcat output.

An unknown server-side error occurred while processing the command. Original error: The instrumentation process cannot be initialized. Make sure the application under test does not crash and investigate the logcat output. (Selenium::WebDriver::Error::UnknownError)
UnknownError: An unknown server-side error occurred while processing the command. Original error: The instrumentation process cannot be initialized. Make sure the application under test does not crash and investigate the logcat output.
at getResponseForW3CError (/usr/local/lib/node_modules/appium/node_modules/appium-base-driver/lib/protocol/errors.js:826:9)
at asyncHandler (/usr/local/lib/node_modules/appium/node_modules/appium-base-driver/lib/protocol/protocol.js:447:37)
at

Briefly describe the issue you are experiencing (or the feature you want to see added to Appium). Tell us what you were trying to do and what happened instead. Remember, this is not a place to ask questions. For that, go to http://discuss.appium.io!

Environment

  • Appium version (or git revision) that exhibits the issue: 1.12.1, 1.13.0
  • Last Appium version that did not exhibit the issue (if applicable): 1.10.1
  • Desktop OS/version used to run Appium: Appium console only
  • Node.js version (unless using Appium.app|exe): 8.10
  • Npm or Yarn package manager: 3.5.2
  • Mobile platform/version under test:
    Name: Nexus_5_API_27
    CPU/ABI: Google Play Intel Atom (x86)
    Path: /home/reinaldorossetti/.android/avd/Nexus_5_API_27.avd
    Target: google_apis_playstore [Google Play] (API level 27)
    Android SDK 26.1.1
    Skin: nexus_5
  • Real device or emulator/simulator: Emulator
  • Appium CLI or Appium.app|exe: appium node

Java:
openjdk version "1.8.0_191"
OpenJDK Runtime Environment (build 1.8.0_191-8u191-b12-2ubuntu0.18.04.1-b12)
OpenJDK 64-Bit Server VM (build 25.191-b12, mixed mode)

Details

If necessary, describe the problem you have been experiencing in more detail.

Link to Appium logs

https://gist.github.com/reinaldorossetti/a8c75b679ac613571bb3b5d5ec9b0ae0

Code To Reproduce Issue [ Good To Have ]

Please remember that with sample code it's easier to reproduce the bug and it's much faster to fix it.

Please git clone https://github.com/appium/appium and from the sample-code directory, use one of your favourite languages and sample apps to reproduce the issue.

In case a similar scenario is missing in sample-code, please submit a PR with one of the sample apps provided.

** Appium started as sudo and adb uninstall io.appium.uiautomator2.server as Success
reinaldorossetti@reinaldorossetti-Notebook:~$ adb uninstall io.appium.uiautomator2.server.test
Success
@mykola-mokhnach
Copy link
Collaborator

[UiAutomator2] 'skipServerInstallation' is set. Attempting to use UIAutomator2 server from the device
[UiAutomator2] Waiting up to 60000ms for UiAutomator2 to be online...
[debug] [ADB] Creating ADB subprocess with args: ["-P",5037,"-s","emulator-5554","shell","am","instrument","-w","io.appium.uiautomator2.server.test/androidx.test.runner.AndroidJUnitRunner"]
[debug] [Instrumentation] android.util.AndroidException: INSTRUMENTATION_FAILED: io.appium.uiautomator2.server.test/androidx.test.runner.AndroidJUnitRunner
[debug] [Instrumentation] at com.android.commands.am.Instrument.run(Instrument.java:421)

Are you sure the UIA2 server is installed on the device?

@mykola-mokhnach mykola-mokhnach added the Needs Info typically non-actionable; needs author to respond label May 8, 2019
@reinaldorossetti
Copy link
Author

reinaldorossetti commented May 8, 2019 •
edited

[UiAutomator2] 'skipServerInstallation' is set. Attempting to use UIAutomator2 server from the device
[UiAutomator2] Waiting up to 60000ms for UiAutomator2 to be online...
[debug] [ADB] Creating ADB subprocess with args: ["-P",5037,"-s","emulator-5554","shell","am","instrument","-w","io.appium.uiautomator2.server.test/androidx.test.runner.AndroidJUnitRunner"]
[debug] [Instrumentation] android.util.AndroidException: INSTRUMENTATION_FAILED: io.appium.uiautomator2.server.test/androidx.test.runner.AndroidJUnitRunner
[debug] [Instrumentation] at com.android.commands.am.Instrument.run(Instrument.java:421)

Are you sure the UIA2 server is installed on the device? Yes, the same works en version 1.10.1, I am use uiautomator 2, you have command that show?

@mykola-mokhnach
Copy link
Collaborator

The server installation is disabled explicitly, so I don't think it is an Appium issue. It just does what is supposed to do, e. g. if you want to control server version on your own then please do it.

@reinaldorossetti
Copy link
Author

reinaldorossetti commented May 8, 2019 •
edited

disabled

the same works in version 1.10.1, this is problem in appium or automator2 driver. The same environment.

@mykola-mokhnach mykola-mokhnach added NotABug UIAutomator2 specific to uiautomator2 driver and removed Needs Info typically non-actionable; needs author to respond labels May 8, 2019
@reinaldorossetti
Copy link
Author

reinaldorossetti commented May 8, 2019 •
edited

How to update UIAutomator2 inside appium? or downgrade version of UIAutomator2? I want to try to get back the driver version to see if it works in version 1.13.

@mykola-mokhnach
Copy link
Collaborator

you cannot, since UIA2 has dependencies on other modules. You must downgrade the whole Appium package

@reinaldorossetti
Copy link
Author

reinaldorossetti commented May 9, 2019 •
edited

you cannot, since UIA2 has dependencies on other modules. You must downgrade the whole Appium package

Thanks very much for support,
Is there any way to solve the problem?
Have you tested these new versions on that OS and Android, Emulator and Java, in which versions?

@mykola-mokhnach
Copy link
Collaborator

Is there any way to solve the problem?

I don't see any problems there - the exception is expected. Like I said above you either keep skipping server install and then manage it on your own or let Appium to manage it.

@mykola-mokhnach
Copy link
Collaborator

Closed as not an issue

@boris779
Copy link

boris779 commented Jul 3, 2019 •
edited

Can someone explained that please? I got the same problem and I do not understand why this expected. I just want to run a test in chrome.

` capabilities.browserName = "chrome"
capabilities.version = "9"

            capabilities.setCapability("noReset", false)
            capabilities.setCapability(MobileCapabilityType.UDID, System.getProperty("device.id", "emulator-5554"))
            capabilities.setCapability(MobileCapabilityType.PLATFORM_NAME, "Android")
            capabilities.setCapability(MobileCapabilityType.DEVICE_NAME, "Android_Device_Appium")
            capabilities.setCapability(MobileCapabilityType.AUTOMATION_NAME, "UiAutomator2")
            capabilities.setCapability(MobileCapabilityType.NEW_COMMAND_TIMEOUT, 12000)`

Cannot work with the device in my tests.

@prakashatul1
Copy link

Just change the emulator/simulator on the device you are running your tests on. Worked for me

@sdjnaik
Copy link

sdjnaik commented Dec 7, 2019

This issue is occurring even with real device. Can you someone mention resolution steps.

Appium version: 1.15.1
OS: Windows
Platform: Android

@amrsa1
Copy link

amrsa1 commented Dec 11, 2019

same issue happening so often especially when u try to run inspector session on remote device with another appium installed on the remote server

@hanhmh1203
Copy link

An unknown server-side error occurred while processing the command. Original error: The instrumentation process cannot be initialized within 60000ms timeout. Make sure the application under test does not crash and investigate the logcat output. You could also try to increase the value of 'uiautomator2ServerLaunchTimeout' capability.

don't know why :(

@yukinotenshi
Copy link

I got the same error when using physical device and switching between different appium servers (on different computer). The solution that I got is to uninstall the Appium Settings app from the device and restart the appium process again.

@gimnguyen
Copy link

I got the same error pls support

C:\WINDOWS\system32>appium [Appium] Welcome to Appium v1.16.0 [Appium] Appium REST http interface listener started on 0.0.0.0:4723 [HTTP] --> POST /wd/hub/session [HTTP] {"desiredCapabilities":{"appActivity":"com.sendo.module.home.view.SplashScreen1Activity","appPackage":"com.sendo","nativeWebScreenshot":true,"automationName":"uiautomator2","unicodeKeyboard":false,"platformName":"Android","resetKeyboard":false},"capabilities":{"firstMatch":[{"appium:appActivity":"com.sendo.module.home.view.SplashScreen1Activity","appium:appPackage":"com.sendo","appium:automationName":"uiautomator2","appium:nativeWebScreenshot":true,"platformName":"android","appium:resetKeyboard":false,"appium:unicodeKeyboard":false}]}} [debug] [W3C] Calling AppiumDriver.createSession() with args: [{"appActivity":"com.sendo.module.home.view.SplashScreen1Activity","appPackage":"com.sendo","nativeWebScreenshot":true,"automationName":"uiautomator2","unicodeKeyboard":false,"platformName":"Android","resetKeyboard":false},null,{"firstMatch":[{"appium:appActivity":"com.sendo.module.home.view.SplashScreen1Activity","appium:appPackage":"com.sendo","appium:automationName":"uiautomator2","appium:nativeWebScreenshot":true,"platformName":"android","appium:resetKeyboard":false,"appium:unicodeKeyboard":false}]}] [debug] [BaseDriver] Event 'newSessionRequested' logged at 1583312990437 (16:09:50 GMT+0700 (Indochina Time)) [Appium] Appium v1.16.0 creating new AndroidUiautomator2Driver (v1.40.0) session [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:appActivity": "com.sendo.module.home.view.SplashScreen1Activity", [debug] [BaseDriver] "appium:appPackage": "com.sendo", [debug] [BaseDriver] "appium:automationName": "uiautomator2", [debug] [BaseDriver] "appium:nativeWebScreenshot": true, [debug] [BaseDriver] "appium:resetKeyboard": false, [debug] [BaseDriver] "appium:unicodeKeyboard": false [debug] [BaseDriver] }, [debug] [BaseDriver] "firstMatch": [ [debug] [BaseDriver] {} [debug] [BaseDriver] ] [debug] [BaseDriver] } [BaseDriver] Session created with session id: 32cf965a-233c-4ec0-b108-8bffde521b5b [UiAutomator2] Starting 'com.sendo' directly on the device [ADB] Found 1 'build-tools' folders under 'D:\sdk' (newest first): [ADB] D:/sdk/build-tools/29.0.3 [ADB] Using 'adb.exe' from 'D:\sdk\platform-tools\adb.exe' [AndroidDriver] Retrieving device list [debug] [ADB] Trying to find a connected android device [debug] [ADB] Getting connected devices... [debug] [ADB] Connected devices: [{"udid":"b84caccb","state":"device"}] [AndroidDriver] Using device: b84caccb [ADB] Using 'adb.exe' from 'D:\sdk\platform-tools\adb.exe' [debug] [ADB] Setting device id to b84caccb [debug] [ADB] Running 'D:\sdk\platform-tools\adb.exe -P 5037 -s b84caccb shell getprop ro.build.version.sdk' [debug] [ADB] Current device property 'ro.build.version.sdk': 25 [debug] [ADB] Device API level: 25 [AndroidDriver] No app sent in, not parsing package/activity [debug] [ADB] Running 'D:\sdk\platform-tools\adb.exe -P 5037 -s b84caccb wait-for-device' [debug] [ADB] Running 'D:\sdk\platform-tools\adb.exe -P 5037 -s b84caccb shell echo ping' [debug] [AndroidDriver] Pushing settings apk to device... [debug] [ADB] Getting install status for io.appium.settings [debug] [ADB] Running 'D:\sdk\platform-tools\adb.exe -P 5037 -s b84caccb shell dumpsys package io.appium.settings' [debug] [ADB] 'io.appium.settings' is installed [debug] [ADB] Getting package info for 'io.appium.settings' [debug] [ADB] Running 'D:\sdk\platform-tools\adb.exe -P 5037 -s b84caccb shell dumpsys package io.appium.settings' [debug] [ADB] The version name of the installed 'io.appium.settings' is greater or equal to the application version name ('2.15.0' >= '2.15.0') [debug] [ADB] There is no need to install/upgrade 'C:\Users\quangnv\AppData\Roaming\npm\node_modules\appium\node_modules\io.appium.settings\apks\settings_apk-debug.apk' [debug] [ADB] Getting IDs of all 'io.appium.settings' processes [debug] [ADB] Running 'D:\sdk\platform-tools\adb.exe -P 5037 -s b84caccb shell 'pgrep --help; echo $?'' [debug] [ADB] Running 'D:\sdk\platform-tools\adb.exe -P 5037 -s b84caccb shell pgrep \^appium\\.settings\$' [debug] [ADB] Running 'D:\sdk\platform-tools\adb.exe -P 5037 -s b84caccb 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 'D:\sdk\platform-tools\adb.exe -P 5037 -s b84caccb shell pgrep \^appium\\.settings\$' [debug] [ADB] Running 'D:\sdk\platform-tools\adb.exe -P 5037 -s b84caccb shell appops set io.appium.settings android\:mock_location allow' [debug] [Logcat] Starting logcat capture [debug] [UiAutomator2] Forwarding UiAutomator2 Server port 6790 to 8200 [debug] [ADB] Forwarding system: 8200 to device: 6790 [debug] [ADB] Running 'D:\sdk\platform-tools\adb.exe -P 5037 -s b84caccb forward tcp\:8200 tcp\:6790' [debug] [ADB] Getting install status for io.appium.uiautomator2.server [debug] [ADB] Running 'D:\sdk\platform-tools\adb.exe -P 5037 -s b84caccb shell dumpsys package io.appium.uiautomator2.server' [debug] [ADB] 'io.appium.uiautomator2.server' is not installed [debug] [ADB] App 'C:\Users\quangnv\AppData\Roaming\npm\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-v4.5.2.apk' is not installed [debug] [UiAutomator2] io.appium.uiautomator2.server installation state: notInstalled [debug] [ADB] Checking app cert for C:\Users\quangnv\AppData\Roaming\npm\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-v4.5.2.apk [ADB] Using 'apksigner.bat' from 'D:\sdk\build-tools\29.0.3\apksigner.bat' [debug] [ADB] Starting 'D:\sdk\build-tools\29.0.3\apksigner.bat' with args '["verify","--print-certs","C:\\Users\\quangnv\\AppData\\Roaming\\npm\\node_modules\\appium\\node_modules\\appium-uiautomator2-server\\apks\\appium-uiautomator2-server-v4.5.2.apk"]' [debug] [ADB] 'C:\Users\quangnv\AppData\Roaming\npm\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-v4.5.2.apk' is signed with non-default certificate [ADB] Using 'zipalign.exe' from 'D:\sdk\build-tools\29.0.3\zipalign.exe' [debug] [ADB] C:\Users\quangnv\AppData\Roaming\npm\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-v4.5.2.apk' is already zip-aligned. Doing nothing [debug] [ADB] Signing 'C:\Users\quangnv\AppData\Roaming\npm\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-v4.5.2.apk' with default cert [debug] [ADB] Starting 'D:\sdk\build-tools\29.0.3\apksigner.bat' with args '["sign","--key","C:\\Users\\quangnv\\AppData\\Roaming\\npm\\node_modules\\appium\\node_modules\\appium-adb\\keys\\testkey.pk8","--cert","C:\\Users\\quangnv\\AppData\\Roaming\\npm\\node_modules\\appium\\node_modules\\appium-adb\\keys\\testkey.x509.pem","C:\\Users\\quangnv\\AppData\\Roaming\\npm\\node_modules\\appium\\node_modules\\appium-uiautomator2-server\\apks\\appium-uiautomator2-server-v4.5.2.apk"]' [debug] [ADB] Getting install status for io.appium.uiautomator2.server.test [debug] [ADB] Running 'D:\sdk\platform-tools\adb.exe -P 5037 -s b84caccb 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\quangnv\AppData\Roaming\npm\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-debug-androidTest.apk [debug] [ADB] Starting 'D:\sdk\build-tools\29.0.3\apksigner.bat' with args '["verify","--print-certs","C:\\Users\\quangnv\\AppData\\Roaming\\npm\\node_modules\\appium\\node_modules\\appium-uiautomator2-server\\apks\\appium-uiautomator2-server-debug-androidTest.apk"]' [debug] [ADB] 'C:\Users\quangnv\AppData\Roaming\npm\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-debug-androidTest.apk' is signed with non-default certificate [debug] [ADB] C:\Users\quangnv\AppData\Roaming\npm\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-debug-androidTest.apk' is already zip-aligned. Doing nothing [debug] [ADB] Signing 'C:\Users\quangnv\AppData\Roaming\npm\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-debug-androidTest.apk' with default cert [debug] [ADB] Starting 'D:\sdk\build-tools\29.0.3\apksigner.bat' with args '["sign","--key","C:\\Users\\quangnv\\AppData\\Roaming\\npm\\node_modules\\appium\\node_modules\\appium-adb\\keys\\testkey.pk8","--cert","C:\\Users\\quangnv\\AppData\\Roaming\\npm\\node_modules\\appium\\node_modules\\appium-adb\\keys\\testkey.x509.pem","C:\\Users\\quangnv\\AppData\\Roaming\\npm\\node_modules\\appium\\node_modules\\appium-uiautomator2-server\\apks\\appium-uiautomator2-server-debug-androidTest.apk"]' [UiAutomator2] Server packages are going to be (re)installed [debug] [ADB] Running 'D:\sdk\platform-tools\adb.exe -P 5037 -s b84caccb shell 'ls -t -1 /data/local/tmp/appium_cache 2>&1 || echo _ERROR_'' [debug] [ADB] The count of applications in the cache: 8 [ADB] The application at 'C:\Users\quangnv\AppData\Roaming\npm\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-v4.5.2.apk' is already cached to '/data/local/tmp/appium_cache/c4d04c1433ecbf8b791b15c7eeb8d8cb0f1b1376.apk' [debug] [ADB] Running 'D:\sdk\platform-tools\adb.exe -P 5037 -s b84caccb shell pm install -r /data/local/tmp/appium_cache/c4d04c1433ecbf8b791b15c7eeb8d8cb0f1b1376.apk' [ADB] The installation of 'appium-uiautomator2-server-v4.5.2.apk' took 3.349s [debug] [ADB] Install command stdout: Success [debug] [ADB] Running 'D:\sdk\platform-tools\adb.exe -P 5037 -s b84caccb shell 'ls -t -1 /data/local/tmp/appium_cache 2>&1 || echo _ERROR_'' [debug] [ADB] The count of applications in the cache: 8 [ADB] The application at 'C:\Users\quangnv\AppData\Roaming\npm\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-debug-androidTest.apk' is already cached to '/data/local/tmp/appium_cache/a1376d3266a5723afda7da2573599b54ad3b2cd1.apk' [debug] [ADB] Running 'D:\sdk\platform-tools\adb.exe -P 5037 -s b84caccb shell pm install -r /data/local/tmp/appium_cache/a1376d3266a5723afda7da2573599b54ad3b2cd1.apk' [ADB] The installation of 'appium-uiautomator2-server-debug-androidTest.apk' took 2.790s [debug] [ADB] Install command stdout: Success [debug] [UiAutomator2] Waiting up to 30000ms for services to be available [debug] [ADB] Running 'D:\sdk\platform-tools\adb.exe -P 5037 -s b84caccb shell pm list instrumentation' [debug] [UiAutomator2] Instrumentation target 'io.appium.uiautomator2.server.test/androidx.test.runner.AndroidJUnitRunner' is available [debug] [UiAutomator2] No app capability. Assuming it is already on the device [debug] [ADB] Getting install status for com.sendo [debug] [ADB] Running 'D:\sdk\platform-tools\adb.exe -P 5037 -s b84caccb shell dumpsys package com.sendo' [debug] [ADB] 'com.sendo' is installed [debug] [ADB] Running 'D:\sdk\platform-tools\adb.exe -P 5037 -s b84caccb shell am force-stop com.sendo' [debug] [ADB] Running 'D:\sdk\platform-tools\adb.exe -P 5037 -s b84caccb shell pm clear com.sendo' [debug] [AndroidDriver] Performed fast reset on the installed 'com.sendo' application (stop and clear) [debug] [UiAutomator2] Performing shallow cleanup of automation leftovers [debug] [UiAutomator2] No obsolete sessions have been detected (Error: socket hang up) [debug] [ADB] Running 'D:\sdk\platform-tools\adb.exe -P 5037 -s b84caccb shell am force-stop io.appium.uiautomator2.server.test' [UiAutomator2] Starting UIAutomator2 server 4.5.2 [UiAutomator2] Using UIAutomator2 server from 'C:\Users\quangnv\AppData\Roaming\npm\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-v4.5.2.apk' and test from 'C:\Users\quangnv\AppData\Roaming\npm\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-debug-androidTest.apk' [UiAutomator2] Waiting up to 30000ms for UiAutomator2 to be online... [debug] [ADB] Creating ADB subprocess with args: ["-P",5037,"-s","b84caccb","shell","am","instrument","-w","io.appium.uiautomator2.server.test/androidx.test.runner.AndroidJUnitRunner"] [debug] [Instrumentation] java.lang.SecurityException: Permission Denial: starting instrumentation ComponentInfo{io.appium.uiautomator2.server.test/androidx.test.runner.AndroidJUnitRunner} from pid=13897, uid=13897 not allowed because package io.appium.uiautomator2.server.test does not have a signature matching the target io.appium.uiautomator2.server [debug] [Instrumentation] INSTRUMENTATION_STATUS: id=ActivityManagerService [debug] [Instrumentation] INSTRUMENTATION_STATUS: Error=Permission Denial: starting instrumentation ComponentInfo{io.appium.uiautomator2.server.test/androidx.test.runner.AndroidJUnitRunner} from pid=13897, uid=13897 not allowed because package io.appium.uiautomator2.server.test does not have a signature matching the target io.appium.uiautomator2.server [debug] [Instrumentation] INSTRUMENTATION_STATUS_CODE: -1 [debug] [Instrumentation] at android.os.Parcel.readException(Parcel.java:1710) [debug] [Instrumentation] at android.os.Parcel.readException(Parcel.java:1663) [debug] [Instrumentation] at android.app.ActivityManagerProxy.startInstrumentation(ActivityManagerNative.java:4693) [debug] [Instrumentation] at com.android.commands.am.Am.runInstrument(Am.java:899) [debug] [Instrumentation] at com.android.commands.am.Am.onRun(Am.java:400) [debug] [Instrumentation] at com.android.internal.os.BaseCommand.run(BaseCommand.java:51) [debug] [Instrumentation] at com.android.commands.am.Am.main(Am.java:121) [debug] [Instrumentation] at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method) [debug] [Instrumentation] at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:364) [debug] [Instrumentation] The process has exited with code 1 [UiAutomator2] The instrumentation process has been unexpectedly terminated. Retrying UiAutomator2 startup (#1 of 1) [debug] [UiAutomator2] Performing strict cleanup of automation leftovers [debug] [UiAutomator2] No obsolete sessions have been detected (Error: socket hang up) [debug] [ADB] Running 'D:\sdk\platform-tools\adb.exe -P 5037 -s b84caccb shell am force-stop io.appium.uiautomator2.server.test' [debug] [ADB] Attempting to kill all uiautomator processes [debug] [ADB] Getting IDs of all 'uiautomator' processes [debug] [ADB] Running 'D:\sdk\platform-tools\adb.exe -P 5037 -s b84caccb shell pgrep \^uiautomator\$' [ADB] No 'uiautomator' process has been found [UiAutomator2] Waiting up to 30000ms for UiAutomator2 to be online... [debug] [ADB] Creating ADB subprocess with args: ["-P",5037,"-s","b84caccb","shell","am","instrument","-w","io.appium.uiautomator2.server.test/androidx.test.runner.AndroidJUnitRunner"] [debug] [Instrumentation] java.lang.SecurityException: Permission Denial: starting instrumentation ComponentInfo{io.appium.uiautomator2.server.test/androidx.test.runner.AndroidJUnitRunner} from pid=13952, uid=13952 not allowed because package io.appium.uiautomator2.server.test does not have a signature matching the target io.appium.uiautomator2.server [debug] [Instrumentation] INSTRUMENTATION_STATUS: id=ActivityManagerService [debug] [Instrumentation] INSTRUMENTATION_STATUS: Error=Permission Denial: starting instrumentation ComponentInfo{io.appium.uiautomator2.server.test/androidx.test.runner.AndroidJUnitRunner} from pid=13952, uid=13952 not allowed because package io.appium.uiautomator2.server.test does not have a signature matching the target io.appium.uiautomator2.server [debug] [Instrumentation] INSTRUMENTATION_STATUS_CODE: -1 [debug] [Instrumentation] at android.os.Parcel.readException(Parcel.java:1710) [debug] [Instrumentation] at android.os.Parcel.readException(Parcel.java:1663) [debug] [Instrumentation] at android.app.ActivityManagerProxy.startInstrumentation(ActivityManagerNative.java:4693) [debug] [Instrumentation] at com.android.commands.am.Am.runInstrument(Am.java:899) [debug] [Instrumentation] at com.android.commands.am.Am.onRun(Am.java:400) [debug] [Instrumentation] at com.android.internal.os.BaseCommand.run(BaseCommand.java:51) [debug] [Instrumentation] at com.android.commands.am.Am.main(Am.java:121) [debug] [Instrumentation] at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method) [debug] [Instrumentation] at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:364) [debug] [Instrumentation] The process has exited with code 1 [UiAutomator2] The instrumentation process cannot be initialized. Make sure the application under test does not crash and investigate the logcat output. [debug] [UiAutomator2] Deleting UiAutomator2 session [debug] [UiAutomator2] Deleting UiAutomator2 server session [debug] [WD Proxy] Matched '/' to command name 'deleteSession' [UiAutomator2] Did not get confirmation UiAutomator2 deleteSession worked; Error was: UnknownError: An unknown server-side error occurred while processing the command. Original error: Trying to proxy a session command without session id [debug] [ADB] Running 'D:\sdk\platform-tools\adb.exe -P 5037 -s b84caccb shell am force-stop com.sendo' [debug] [Logcat] Stopping logcat capture [debug] [ADB] Removing forwarded port socket connection: 8200 [debug] [ADB] Running 'D:\sdk\platform-tools\adb.exe -P 5037 -s b84caccb forward --remove tcp\:8200' [debug] [BaseDriver] Event 'newSessionStarted' logged at 1583313010884 (16:10:10 GMT+0700 (Indochina Time)) [debug] [W3C] Encountered internal error running command: Error: The instrumentation process cannot be initialized. Make sure the application under test does not crash and investigate the logcat output. [debug] [W3C] at Object.errorAndThrow (C:\Users\quangnv\AppData\Roaming\npm\node_modules\appium\node_modules\appium-support\lib\logging.js:74:35) [debug] [W3C] at UiAutomator2Server.startSession (C:\Users\quangnv\AppData\Roaming\npm\node_modules\appium\node_modules\appium-uiautomator2-driver\lib\uiautomator2.js:231:13) [debug] [W3C] at AndroidUiautomator2Driver.startUiAutomator2Session (C:\Users\quangnv\AppData\Roaming\npm\node_modules\appium\node_modules\appium-uiautomator2-driver\lib\driver.js:362:5) [debug] [W3C] at AndroidUiautomator2Driver.createSession (C:\Users\quangnv\AppData\Roaming\npm\node_modules\appium\node_modules\appium-uiautomator2-driver\lib\driver.js:208:7) [debug] [W3C] at AppiumDriver.createSession (C:\Users\quangnv\AppData\Roaming\npm\node_modules\appium\lib\appium.js:358:35) [HTTP] <-- POST /wd/hub/session 500 20529 ms - 839

@sumitvani
Copy link

[UiAutomator2] 'skipServerInstallation' is set. Attempting to use UIAutomator2 server from the device
[UiAutomator2] Waiting up to 60000ms for UiAutomator2 to be online...
[debug] [ADB] Creating ADB subprocess with args: ["-P",5037,"-s","emulator-5554","shell","am","instrument","-w","io.appium.uiautomator2.server.test/androidx.test.runner.AndroidJUnitRunner"]
[debug] [Instrumentation] android.util.AndroidException: INSTRUMENTATION_FAILED: io.appium.uiautomator2.server.test/androidx.test.runner.AndroidJUnitRunner
[debug] [Instrumentation] at com.android.commands.am.Instrument.run(Instrument.java:421)

Are you sure the UIA2 server is installed on the device?

If not then how I can install UIA?

@VinothArasu
Copy link

HI , Am getting the below error, While i run my appium via protractor, Can anyone please help

[info] �[35m[Appium]�[39m Welcome to Appium v1.15.1
[info] �[35m[Appium]�[39m Non-default server args:
[info] �[35m[Appium]�[39m allowInsecure: {
[info] �[35m[Appium]�[39m }
[info] �[35m[Appium]�[39m denyInsecure: {
[info] �[35m[Appium]�[39m }
[info] �[35m[Appium]�[39m Appium REST http interface listener started on 0.0.0.0:4723[info] �[35m[HTTP]�[39m �[37m-->�[39m �[37mPOST�[39m �[37m/wd/hub/session�[39m
[info] �[35m[HTTP]�[39m �[90m{"desiredCapabilities":{"browserName":"chrome","platformName":"android","deviceName":"6b426af90906","count":1}}�[39m
[debug] �[35m[MJSONWP]�[39m Calling AppiumDriver.createSession() with args: [{"browserName":"chrome","platformName":"android","deviceName":"6b426af90906","count":1},null,null]
[debug] �[35m[BaseDriver]�[39m Event 'newSessionRequested' logged at 1588146025329 (13:10:25 GMT+0530 (India Standard Time))
[warn] �[35m[Appium]�[39m
[warn] �[35m[Appium]�[39m ======================================================================
[warn] �[35m[Appium]�[39m DEPRECATION WARNING:
[warn] �[35m[Appium]�[39m
[warn] �[35m[Appium]�[39m The 'automationName' capability was not provided in the desired
[warn] �[35m[Appium]�[39m capabilities for this Android session
[warn] �[35m[Appium]�[39m
[warn] �[35m[Appium]�[39m Setting 'automationName=UiAutomator2' by default and using the
[warn] �[35m[Appium]�[39m UiAutomator2 Driver
[warn] �[35m[Appium]�[39m
[warn] �[35m[Appium]�[39m The next major version of Appium (2.x) will require the
[warn] �[35m[Appium]�[39m 'automationName' capability to be set for all sessions on all
[warn] �[35m[Appium]�[39m platforms
[warn] �[35m[Appium]�[39m
[warn] �[35m[Appium]�[39m In previous versions (Appium <= 1.13.x), the default was
[warn] �[35m[Appium]�[39m 'automationName=UiAutomator1'
[warn] �[35m[Appium]�[39m
[warn] �[35m[Appium]�[39m If you wish to use that automation instead of UiAutomator2, please
[warn] �[35m[Appium]�[39m add 'automationName=UiAutomator1' to your desired capabilities
[warn] �[35m[Appium]�[39m
[warn] �[35m[Appium]�[39m For more information about drivers, please visit
[warn] �[35m[Appium]�[39m http://appium.io/docs/en/about-appium/intro/ and explore the
[warn] �[35m[Appium]�[39m 'Drivers' menu
[warn] �[35m[Appium]�[39m
[warn] �[35m[Appium]�[39m ======================================================================
[warn] �[35m[Appium]�[39m
[info] �[35m[Appium]�[39m Appium v1.15.1 creating new AndroidUiautomator2Driver (v1.37.2) session
[debug] �[35m[BaseDriver]�[39m Creating session with MJSONWP desired capabilities: {
[debug] �[35m[BaseDriver]�[39m "browserName": "chrome",
[debug] �[35m[BaseDriver]�[39m "platformName": "android",
[debug] �[35m[BaseDriver]�[39m "deviceName": "6b426af90906",
[debug] �[35m[BaseDriver]�[39m "count": 1
[debug] �[35m[BaseDriver]�[39m }
[warn] �[35m[BaseDriver]�[39m The following capabilities were provided, but are not recognized by Appium:
[warn] �[35m[BaseDriver]�[39m count
[info] �[35m[BaseDriver]�[39m Session created with session id: bad912cd-7f67-4a61-b652-c16c94c13dd4
[info] �[35m[UiAutomator2]�[39m We're going to run a Chrome-based session
[info] �[35m[UiAutomator2]�[39m Chrome-type package and activity are com.android.chrome and com.google.android.apps.chrome.Main
[info] �[35m[UiAutomator2]�[39m Starting 'com.android.chrome' directly on the device[info] �[35m[ADB]�[39m Using 'adb.exe' from 'C:\Users\z029678\Desktop\Appium\platform-tools\adb.exe'
[info] �[35m[AndroidDriver]�[39m Retrieving device list
[debug] �[35m[ADB]�[39m Trying to find a connected android device
[debug] �[35m[ADB]�[39m Getting connected devices...
[debug] �[35m[ADB]�[39m Connected devices: [{"udid":"6b426af90906","state":"device"}]
[info] �[35m[AndroidDriver]�[39m Using device: 6b426af90906
[info] �[35m[ADB]�[39m Using 'adb.exe' from 'C:\Users\z029678\Desktop\Appium\platform-tools\adb.exe'
[debug] �[35m[ADB]�[39m Setting device id to 6b426af90906
[debug] �[35m[ADB]�[39m Running 'C:\Users\z029678\Desktop\Appium\platform-tools\adb.exe -P 5037 -s 6b426af90906 shell getprop ro.build.version.sdk'[debug] �[35m[ADB]�[39m Current device property 'ro.build.version.sdk': 28
[debug] �[35m[ADB]�[39m Running 'C:\Users\z029678\Desktop\Appium\platform-tools\adb.exe -P 5037 -s 6b426af90906 shell getprop ro.build.version.release'[debug] �[35m[ADB]�[39m Current device property 'ro.build.version.release': 9
[debug] �[35m[ADB]�[39m Device API level: 28
[warn] �[35m[UiAutomator2]�[39m Relaxing hidden api policy
[debug] �[35m[ADB]�[39m Running 'C:\Users\z029678\Desktop\Appium\platform-tools\adb.exe -P 5037 -s 6b426af90906 shell settings put global hidden_api_policy_pre_p_apps 1'[debug] �[35m[ADB]�[39m Running 'C:\Users\z029678\Desktop\Appium\platform-tools\adb.exe -P 5037 -s 6b426af90906 shell settings put global hidden_api_policy_p_apps 1'[debug] �[35m[ADB]�[39m Running 'C:\Users\z029678\Desktop\Appium\platform-tools\adb.exe -P 5037 -s 6b426af90906 shell settings put global hidden_api_policy 1'
[warn] �[35m[AndroidDriver]�[39m No app sent in, not parsing package/activity
[debug] �[35m[ADB]�[39m Running 'C:\Users\z029678\Desktop\Appium\platform-tools\adb.exe -P 5037 -s 6b426af90906 wait-for-device'[debug] �[35m[ADB]�[39m Running 'C:\Users\z029678\Desktop\Appium\platform-tools\adb.exe -P 5037 -s 6b426af90906 shell echo ping'[debug] �[35m[AndroidDriver]�[39m Pushing settings apk to device...
[debug] �[35m[ADB]�[39m Getting install status for io.appium.settings
[debug] �[35m[ADB]�[39m Running 'C:\Users\z029678\Desktop\Appium\platform-tools\adb.exe -P 5037 -s 6b426af90906 shell dumpsys package io.appium.settings'[debug] �[35m[ADB]�[39m 'io.appium.settings' is installed
[debug] �[35m[ADB]�[39m Getting package info for 'io.appium.settings'
[debug] �[35m[ADB]�[39m Running 'C:\Users\z029678\Desktop\Appium\platform-tools\adb.exe -P 5037 -s 6b426af90906 shell dumpsys package io.appium.settings'[info] �[35m[ADB]�[39m Cannot extract apk info using apkanalyzer. Falling back to aapt. Original error: Could not find 'apkanalyzer.bat' in ["C:\Users\z029678\Desktop\Appium\platform-tools\apkanalyzer.bat","C:\Users\z029678\Desktop\Appium\emulator\apkanalyzer.bat","C:\Users\z029678\Desktop\Appium\tools\apkanalyzer.bat","C:\Users\z029678\Desktop\Appium\tools\bin\apkanalyzer.bat","C:\Users\z029678\Desktop\Appium\build-tools\29.0.3\apkanalyzer.bat"]. Do you have Android Build Tools installed at 'C:\Users\z029678\Desktop\Appium'?
[info] �[35m[ADB]�[39m Using 'aapt.exe' from 'C:\Users\z029678\Desktop\Appium\build-tools\29.0.3\aapt.exe'
[debug] �[35m[ADB]�[39m The version name of the installed 'io.appium.settings' is greater or equal to the application version name ('2.14.2' >= '2.14.2')
[debug] �[35m[ADB]�[39m There is no need to install/upgrade 'C:\Program Files\Appium\resources\app\node_modules\appium\node_modules\io.appium.settings\apks\settings_apk-debug.apk'
[debug] �[35m[ADB]�[39m Getting IDs of all 'io.appium.settings' processes
[debug] �[35m[ADB]�[39m Running 'C:\Users\z029678\Desktop\Appium\platform-tools\adb.exe -P 5037 -s 6b426af90906 shell 'pgrep --help; echo $?''[debug] �[35m[ADB]�[39m Running 'C:\Users\z029678\Desktop\Appium\platform-tools\adb.exe -P 5037 -s 6b426af90906 shell pgrep -f io\.appium\.settings'[debug] �[35m[AndroidDriver]�[39m io.appium.settings is already running. There is no need to reset its permissions.
[debug] �[35m[ADB]�[39m Running 'C:\Users\z029678\Desktop\Appium\platform-tools\adb.exe -P 5037 -s 6b426af90906 shell appops set io.appium.settings android:mock_location allow'[debug] �[35m[Logcat]�[39m Starting logcat capture[info] �[35m[UiAutomator2]�[39m Server package at 'C:\Program Files\Appium\resources\app\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-v4.3.0.apk' is not writeable. Will copy it into the temporary location at 'C:\Users\z029678\AppData\Local\Temp\2020329-3220-1q1t6w8.wzex' as a workaround. Consider making this file writeable manually in order to improve the performance of session startup.
[info] �[35m[UiAutomator2]�[39m Server package at 'C:\Program Files\Appium\resources\app\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-debug-androidTest.apk' is not writeable. Will copy it into the temporary location at 'C:\Users\z029678\AppData\Local\Temp\2020329-3220-1q1t6w8.wzex' as a workaround. Consider making this file writeable manually in order to improve the performance of session startup.
[debug] �[35m[ADB]�[39m Getting install status for io.appium.uiautomator2.server
[debug] �[35m[ADB]�[39m Running 'C:\Users\z029678\Desktop\Appium\platform-tools\adb.exe -P 5037 -s 6b426af90906 shell dumpsys package io.appium.uiautomator2.server'[debug] �[35m[ADB]�[39m 'io.appium.uiautomator2.server' is installed
[debug] �[35m[ADB]�[39m Getting package info for 'io.appium.uiautomator2.server'
[debug] �[35m[ADB]�[39m Running 'C:\Users\z029678\Desktop\Appium\platform-tools\adb.exe -P 5037 -s 6b426af90906 shell dumpsys package io.appium.uiautomator2.server'[info] �[35m[ADB]�[39m Cannot extract apk info using apkanalyzer. Falling back to aapt. Original error: Could not find 'apkanalyzer.bat' in ["C:\Users\z029678\Desktop\Appium\platform-tools\apkanalyzer.bat","C:\Users\z029678\Desktop\Appium\emulator\apkanalyzer.bat","C:\Users\z029678\Desktop\Appium\tools\apkanalyzer.bat","C:\Users\z029678\Desktop\Appium\tools\bin\apkanalyzer.bat","C:\Users\z029678\Desktop\Appium\build-tools\29.0.3\apkanalyzer.bat"]. Do you have Android Build Tools installed at 'C:\Users\z029678\Desktop\Appium'?[debug] �[35m[ADB]�[39m apksigner stdout: Signer #1 certificate DN: EMAILADDRESS=android@android.com, CN=Android, OU=Android, O=Android, L=Mountain View, ST=California, C=US
[debug] �[35m[ADB]�[39m Signer #1 certificate SHA-256 digest: a40da80a59d170caa950cf15c18c454d47a39b26989d8b640ecd745ba71bf5dc
[debug] �[35m[ADB]�[39m Signer #1 certificate SHA-1 digest: 61ed377e85d386a8dfee6b864bd85b0bfaa5af81
[debug] �[35m[ADB]�[39m Signer #1 certificate MD5 digest: e89b158e4bcf988ebd09eb83f5378e87
[debug] �[35m[ADB]�[39m
[debug] �[35m[ADB]�[39m apksigner stderr: ERROR: Registry editing has been disabled by your administrator.
[debug] �[35m[ADB]�[39m
[debug] �[35m[ADB]�[39m 'C:\Users\z029678\AppData\Local\Temp\2020329-3220-1q1t6w8.wzex\appium-uiautomator2-server-v4.3.0.apk' is already signed.
[debug] �[35m[ADB]�[39m Getting install status for io.appium.uiautomator2.server.test
[debug] �[35m[ADB]�[39m Running 'C:\Users\z029678\Desktop\Appium\platform-tools\adb.exe -P 5037 -s 6b426af90906 shell dumpsys package io.appium.uiautomator2.server.test'[debug] �[35m[ADB]�[39m 'io.appium.uiautomator2.server.test' is installed
[debug] �[35m[ADB]�[39m Checking app cert for C:\Users\z029678\AppData\Local\Temp\2020329-3220-1q1t6w8.wzex\appium-uiautomator2-server-debug-androidTest.apk
[debug] �[35m[ADB]�[39m Starting 'C:\Users\z029678\Desktop\Appium\build-tools\29.0.3\apksigner.bat' with args '["verify","--print-certs","C:\Users\z029678\AppData\Local\Temp\2020329-3220-1q1t6w8.wzex\appium-uiautomator2-server-debug-androidTest.apk"]'[debug] �[35m[ADB]�[39m apksigner stdout: Signer #1 certificate DN: CN=Android Debug, O=Android, C=US
[debug] �[35m[ADB]�[39m Signer #1 certificate SHA-256 digest: 3e4f2ab66d641bbbd363421151755f8b12b66ea37a5db43c52116596b7392a8e
[debug] �[35m[ADB]�[39m Signer #1 certificate SHA-1 digest: e24fc8971c0aad07d1df6cc62af7fb0d48b45b60
[debug] �[35m[ADB]�[39m Signer #1 certificate MD5 digest: 5623d53469c7f7147b52ace9d09901eb
[debug] �[35m[ADB]�[39m
[debug] �[35m[ADB]�[39m apksigner stderr: ERROR: Registry editing has been disabled by your administrator.
[debug] �[35m[ADB]�[39m
[debug] �[35m[ADB]�[39m 'C:\Users\z029678\AppData\Local\Temp\2020329-3220-1q1t6w8.wzex\appium-uiautomator2-server-debug-androidTest.apk' is signed with non-default certificate
[info] �[35m[ADB]�[39m Using 'zipalign.exe' from 'C:\Users\z029678\Desktop\Appium\build-tools\29.0.3\zipalign.exe'
[debug] �[35m[ADB]�[39m C:\Users\z029678\AppData\Local\Temp\2020329-3220-1q1t6w8.wzex\appium-uiautomator2-server-debug-androidTest.apk' is already zip-aligned. Doing nothing
[debug] �[35m[ADB]�[39m Signing 'C:\Users\z029678\AppData\Local\Temp\2020329-3220-1q1t6w8.wzex\appium-uiautomator2-server-debug-androidTest.apk' with default cert
[debug] �[35m[ADB]�[39m Starting 'C:\Users\z029678\Desktop\Appium\build-tools\29.0.3\apksigner.bat' with args '["sign","--key","C:\Program Files\Appium\resources\app\node_modules\appium\node_modules\appium-adb\keys\testkey.pk8","--cert","C:\Program Files\Appium\resources\app\node_modules\appium\node_modules\appium-adb\keys\testkey.x509.pem","C:\Users\z029678\AppData\Local\Temp\2020329-3220-1q1t6w8.wzex\appium-uiautomator2-server-debug-androidTest.apk"]'[debug] �[35m[ADB]�[39m apksigner stderr: ERROR: Registry editing has been disabled by your administrator.
[debug] �[35m[ADB]�[39m
[info] �[35m[UiAutomator2]�[39m Server packages are going to be (re)installed
[info] �[35m[UiAutomator2]�[39m Full packages reinstall is going to be performed
[debug] �[35m[ADB]�[39m Uninstalling io.appium.uiautomator2.server
[debug] �[35m[ADB]�[39m Getting install status for io.appium.uiautomator2.server
[debug] �[35m[ADB]�[39m Running 'C:\Users\z029678\Desktop\Appium\platform-tools\adb.exe -P 5037 -s 6b426af90906 shell dumpsys package io.appium.uiautomator2.server'[debug] �[35m[ADB]�[39m 'io.appium.uiautomator2.server' is installed
[debug] �[35m[ADB]�[39m Running 'C:\Users\z029678\Desktop\Appium\platform-tools\adb.exe -P 5037 -s 6b426af90906 shell am force-stop io.appium.uiautomator2.server'[debug] �[35m[Instrumentation]�[39m INSTRUMENTATION_RESULT: shortMsg=Process crashed.
[debug] �[35m[Instrumentation]�[39m INSTRUMENTATION_CODE: 0
[debug] �[35m[ADB]�[39m Running 'C:\Users\z029678\Desktop\Appium\platform-tools\adb.exe -P 5037 -s 6b426af90906 uninstall io.appium.uiautomator2.server'
[debug] �[35m[Instrumentation]�[39m The process has exited with code 0[debug] �[35m[ADB]�[39m 'adb uninstall io.appium.uiautomator2.server' command output: Success
[info] �[35m[ADB]�[39m io.appium.uiautomator2.server was successfully uninstalled
[debug] �[35m[ADB]�[39m Running 'C:\Users\z029678\Desktop\Appium\platform-tools\adb.exe -P 5037 -s 6b426af90906 shell 'ls -t -1 /data/local/tmp/appium_cache 2>&1 || echo ERROR''[debug] �[35m[ADB]�[39m The count of applications in the cache: 3
[info] �[35m[ADB]�[39m The application at 'C:\Users\z029678\AppData\Local\Temp\2020329-3220-1q1t6w8.wzex\appium-uiautomator2-server-v4.3.0.apk' is already cached to '/data/local/tmp/appium_cache/0cc1725a60a05dbb5d0d09256f2fc6ece7e3b10f.apk'
[debug] �[35m[ADB]�[39m Running 'C:\Users\z029678\Desktop\Appium\platform-tools\adb.exe -P 5037 -s 6b426af90906 shell pm install -r /data/local/tmp/appium_cache/0cc1725a60a05dbb5d0d09256f2fc6ece7e3b10f.apk'[info] �[35m[ADB]�[39m The installation of 'appium-uiautomator2-server-v4.3.0.apk' took 8.419s
[debug] �[35m[ADB]�[39m Install command stdout: Success
[debug] �[35m[ADB]�[39m Uninstalling io.appium.uiautomator2.server.test
[debug] �[35m[ADB]�[39m Getting install status for io.appium.uiautomator2.server.test
[debug] �[35m[ADB]�[39m Running 'C:\Users\z029678\Desktop\Appium\platform-tools\adb.exe -P 5037 -s 6b426af90906 shell dumpsys package io.appium.uiautomator2.server.test'[debug] �[35m[ADB]�[39m 'io.appium.uiautomator2.server.test' is installed
[debug] �[35m[ADB]�[39m Running 'C:\Users\z029678\Desktop\Appium\platform-tools\adb.exe -P 5037 -s 6b426af90906 shell am force-stop io.appium.uiautomator2.server.test'[debug] �[35m[ADB]�[39m Running 'C:\Users\z029678\Desktop\Appium\platform-tools\adb.exe -P 5037 -s 6b426af90906 uninstall io.appium.uiautomator2.server.test'[debug] �[35m[ADB]�[39m 'adb uninstall io.appium.uiautomator2.server.test' command output: Success
[info] �[35m[ADB]�[39m io.appium.uiautomator2.server.test was successfully uninstalled[debug] �[35m[ADB]�[39m The count of applications in the cache: 3
[info] �[35m[ADB]�[39m The application at 'C:\Users\z029678\AppData\Local\Temp\2020329-3220-1q1t6w8.wzex\appium-uiautomator2-server-debug-androidTest.apk' is already cached to '/data/local/tmp/appium_cache/cd247f042368990c9f33b2d7bf2390d8cf4f4e24.apk'
[debug] �[35m[ADB]�[39m Running 'C:\Users\z029678\Desktop\Appium\platform-tools\adb.exe -P 5037 -s 6b426af90906 shell pm install -r /data/local/tmp/appium_cache/cd247f042368990c9f33b2d7bf2390d8cf4f4e24.apk'[info] �[35m[ADB]�[39m The installation of 'appium-uiautomator2-server-debug-androidTest.apk' took 5.984s
[debug] �[35m[ADB]�[39m Install command stdout: Success
[debug] �[35m[UiAutomator2]�[39m Waiting up to 30000ms for services to be available
[debug] �[35m[ADB]�[39m Running 'C:\Users\z029678\Desktop\Appium\platform-tools\adb.exe -P 5037 -s 6b426af90906 shell pm list instrumentation'[debug] �[35m[UiAutomator2]�[39m Instrumentation target 'io.appium.uiautomator2.server.test/androidx.test.runner.AndroidJUnitRunner' is available
[debug] �[35m[UiAutomator2]�[39m Forwarding UiAutomator2 Server port 6790 to 8200
[debug] �[35m[ADB]�[39m Forwarding system: 8200 to device: 6790
[debug] �[35m[ADB]�[39m Running 'C:\Users\z029678\Desktop\Appium\platform-tools\adb.exe -P 5037 -s 6b426af90906 forward tcp:8200 tcp:6790'[debug] �[35m[UiAutomator2]�[39m No app capability. Assuming it is already on the device
[debug] �[35m[ADB]�[39m Getting install status for com.android.chrome
[debug] �[35m[ADB]�[39m Running 'C:\Users\z029678\Desktop\Appium\platform-tools\adb.exe -P 5037 -s 6b426af90906 shell dumpsys package com.android.chrome'[debug] �[35m[ADB]�[39m 'com.android.chrome' is installed
[debug] �[35m[ADB]�[39m Running 'C:\Users\z029678\Desktop\Appium\platform-tools\adb.exe -P 5037 -s 6b426af90906 shell am force-stop com.android.chrome'[debug] �[35m[ADB]�[39m Running 'C:\Users\z029678\Desktop\Appium\platform-tools\adb.exe -P 5037 -s 6b426af90906 shell pm clear com.android.chrome'[debug] �[35m[AndroidDriver]�[39m Performed fast reset on the installed 'com.android.chrome' application (stop and clear)
[debug] �[35m[UiAutomator2]�[39m Performing shallow cleanup of automation leftovers[debug] �[35m[UiAutomator2]�[39m No obsolete sessions have been detected (Error: ETIMEDOUT)
[debug] �[35m[ADB]�[39m Running 'C:\Users\z029678\Desktop\Appium\platform-tools\adb.exe -P 5037 -s 6b426af90906 shell am force-stop io.appium.uiautomator2.server.test'[info] �[35m[UiAutomator2]�[39m Starting UIAutomator2 server 4.3.0
[info] �[35m[UiAutomator2]�[39m Using UIAutomator2 server from 'C:\Program Files\Appium\resources\app\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-v4.3.0.apk' and test from 'C:\Program Files\Appium\resources\app\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-debug-androidTest.apk'
[info] �[35m[UiAutomator2]�[39m Waiting up to 30000ms for UiAutomator2 to be online...
[debug] �[35m[ADB]�[39m Creating ADB subprocess with args: ["-P",5037,"-s","6b426af90906","shell","am","instrument","-w","io.appium.uiautomator2.server.test/androidx.test.runner.AndroidJUnitRunner"][debug] �[35m[WD Proxy]�[39m Matched '/status' to command name 'getStatus'
[debug] �[35m[WD Proxy]�[39m Proxying [GET /status] to [GET http://localhost:8200/wd/hub/status] with no body[debug] �[35m[Instrumentation]�[39m io.appium.uiautomator2.server.test.AppiumUiAutomator2Server:[info] �[35m[WD Proxy]�[39m Got an unexpected response with status undefined: {"errno":"ETIMEDOUT","code":"ETIMEDOUT","syscall":"connect","address":"10.244.3.249","port":3128}[debug] �[35m[WD Proxy]�[39m Matched '/status' to command name 'getStatus'
[debug] �[35m[WD Proxy]�[39m Proxying [GET /status] to [GET http://localhost:8200/wd/hub/status] with no body[info] �[35m[WD Proxy]�[39m Got an unexpected response with status undefined: {"errno":"ETIMEDOUT","code":"ETIMEDOUT","syscall":"connect","address":"10.244.3.249","port":3128}
[error] �[35m[UiAutomator2]�[39m Error: The instrumentation process cannot be initialized within 30000ms timeout. Make sure the application under test does not crash and investigate the logcat output. You could also try to increase the value of 'uiautomator2ServerLaunchTimeout' capability.
[error] �[35m[UiAutomator2]�[39m at Object.wrappedLogger.errorAndThrow (C:\Program Files\Appium\resources\app\node_modules\appium\node_modules\appium-support\lib\logging.js:79:13)
[error] �[35m[UiAutomator2]�[39m at UiAutomator2Server.errorAndThrow [as startSession] (C:\Program Files\Appium\resources\app\node_modules\appium\node_modules\appium-uiautomator2-driver\lib\uiautomator2.js:216:15)
[debug] �[35m[UiAutomator2]�[39m Deleting UiAutomator2 session
[debug] �[35m[UiAutomator2]�[39m Deleting UiAutomator2 server session
[debug] �[35m[WD Proxy]�[39m Matched '/' to command name 'deleteSession'
[warn] �[35m[UiAutomator2]�[39m Did not get confirmation UiAutomator2 deleteSession worked; Error was: UnknownError: An unknown server-side error occurred while processing the command. Original error: Trying to proxy a session command without session id
[debug] �[35m[Logcat]�[39m Stopping logcat capture
[debug] �[35m[ADB]�[39m Removing forwarded port socket connection: 8200
[debug] �[35m[ADB]�[39m Running 'C:\Users\z029678\Desktop\Appium\platform-tools\adb.exe -P 5037 -s 6b426af90906 forward --remove tcp:8200'[info] �[35m[UiAutomator2]�[39m Restoring hidden api policy to the device default configuration
[debug] �[35m[ADB]�[39m Running 'C:\Users\z029678\Desktop\Appium\platform-tools\adb.exe -P 5037 -s 6b426af90906 shell settings delete global hidden_api_policy_pre_p_apps'[debug] �[35m[ADB]�[39m Running 'C:\Users\z029678\Desktop\Appium\platform-tools\adb.exe -P 5037 -s 6b426af90906 shell settings delete global hidden_api_policy_p_apps'[debug] �[35m[ADB]�[39m Running 'C:\Users\z029678\Desktop\Appium\platform-tools\adb.exe -P 5037 -s 6b426af90906 shell settings delete global hidden_api_policy'[debug] �[35m[BaseDriver]�[39m Event 'newSessionStarted' logged at 1588146102137 (13:11:42 GMT+0530 (India Standard Time))
[debug] �[35m[MJSONWP]�[39m Encountered internal error running command: Error: The instrumentation process cannot be initialized within 30000ms timeout. Make sure the application under test does not crash and investigate the logcat output. You could also try to increase the value of 'uiautomator2ServerLaunchTimeout' capability.
[debug] �[35m[MJSONWP]�[39m at Object.wrappedLogger.errorAndThrow (C:\Program Files\Appium\resources\app\node_modules\appium\node_modules\appium-support\lib\logging.js:79:13)
[debug] �[35m[MJSONWP]�[39m at UiAutomator2Server.errorAndThrow [as startSession] (C:\Program Files\Appium\resources\app\node_modules\appium\node_modules\appium-uiautomator2-driver\lib\uiautomator2.js:216:15)
[info] �[35m[HTTP]�[39m �[37m<-- POST /wd/hub/session �[39m�[31m500�[39m �[90m76810 ms - 388�[39m
[info] �[35m[HTTP]�[39m �[90m�[39m

@KazuCocoa
Copy link
Member

[debug] �[35m[ADB]�[39m Starting 'C:\Users\z029678\Desktop\Appium\build-tools\29.0.3\apksigner.bat' with args '["sign","--key","C:\Program Files\Appium\resources\app\node_modules\appium\node_modules\appium-adb\keys\testkey.pk8","--cert","C:\Program Files\Appium\resources\app\node_modules\appium\node_modules\appium-adb\keys\testkey.x509.pem","C:\Users\z029678\AppData\Local\Temp\2020329-3220-1q1t6w8.wzex\appium-uiautomator2-server-debug-androidTest.apk"]'[debug] �[35m[ADB]�[39m apksigner stderr: ERROR: Registry editing has been disabled by your administrator.

Something permission error on your local had?

[debug] �[35m[ADB]�[39m C:\Users\z029678\AppData\Local\Temp\2020329-3220-1q1t6w8.wzex\appium-uiautomator2-server-debug-androidTest.apk' is already zip-aligned. Doing nothing
[debug] �[35m[ADB]�[39m Signing 'C:\Users\z029678\AppData\Local\Temp\2020329-3220-1q1t6w8.wzex\appium-uiautomator2-server-debug-androidTest.apk' with default cert
[debug] �[35m[ADB]�[39m Starting 'C:\Users\z029678\Desktop\Appium\build-tools\29.0.3\apksigner.bat' with args '["sign","--key","C:\Program Files\Appium\resources\app\node_modules\appium\node_modules\appium-adb\keys\testkey.pk8","--cert","C:\Program Files\Appium\resources\app\node_modules\appium\node_modules\appium-adb\keys\testkey.x509.pem","C:\Users\z029678\AppData\Local\Temp\2020329-3220-1q1t6w8.wzex\appium-uiautomator2-server-debug-androidTest.apk"]'[debug] �[35m[ADB]�[39m apksigner stderr: ERROR: Registry editing has been disabled by your administrator.
[debug] �[35m[ADB]�[39m
[info] �[35m[UiAutomator2]�[39m Server packages are going to be (re)installed
[info] �[35m[UiAutomator2]�[39m Full packages reinstall is going to be performed
[debug] �[35m[ADB]�[39m Uninstalling io.appium.uiautomator2.server
[debug] �[35m[ADB]�[39m Getting install status for io.appium.uiautomator2.server
[debug] �[35m[ADB]�[39m Running 'C:\Users\z029678\Desktop\Appium\platform-tools\adb.exe -P 5037 -s 6b426af90906 shell dumpsys package io.appium.uiautomator2.server'[debug] �[35m[ADB]�[39m 'io.appium.uiautomator2.server' is installed
[debug] �[35m[ADB]�[39m Running 'C:\Users\z029678\Desktop\Appium\platform-tools\adb.exe -P 5037 -s 6b426af90906 shell am force-stop io.appium.uiautomator2.server'[debug] �[35m[Instrumentation]�[39m INSTRUMENTATION_RESULT: shortMsg=Process crashed.
[debug] �[35m[Instrumentation]�[39m INSTRUMENTATION_CODE: 0
[debug] �[35m[ADB]�[39m Running 'C:\Users\z029678\Desktop\Appium\platform-tools\adb.exe -P 5037 -s 6b426af90906 uninstall io.appium.uiautomator2.server'

@VinothArasu
Copy link

HI KazuCocoa,

sorry for the above post, after connected to my organisation network. Am getting an different error screen in Appium .. Could you please have a look

[info] �[35m[Appium]�[39m Welcome to Appium v1.15.1
[info] �[35m[Appium]�[39m Non-default server args:
[info] �[35m[Appium]�[39m sessionOverride: true
[info] �[35m[Appium]�[39m allowInsecure: {
[info] �[35m[Appium]�[39m }
[info] �[35m[Appium]�[39m denyInsecure: {
[info] �[35m[Appium]�[39m }
[info] �[35m[Appium]�[39m Appium REST http interface listener started on 0.0.0.0:4723[info] �[35m[HTTP]�[39m �[37m-->�[39m �[37mPOST�[39m �[37m/wd/hub/session�[39m
[info] �[35m[HTTP]�[39m �[90m{"desiredCapabilities":{"browserName":"chrome","platformName":"android","deviceName":"6b426af90906","count":1}}�[39m
[debug] �[35m[MJSONWP]�[39m Calling AppiumDriver.createSession() with args: [{"browserName":"chrome","platformName":"android","deviceName":"6b426af90906","count":1},null,null]
[debug] �[35m[BaseDriver]�[39m Event 'newSessionRequested' logged at 1588172934277 (20:38:54 GMT+0530 (India Standard Time))
[warn] �[35m[Appium]�[39m
[warn] �[35m[Appium]�[39m ======================================================================
[warn] �[35m[Appium]�[39m DEPRECATION WARNING:
[warn] �[35m[Appium]�[39m
[warn] �[35m[Appium]�[39m The 'automationName' capability was not provided in the desired
[warn] �[35m[Appium]�[39m capabilities for this Android session
[warn] �[35m[Appium]�[39m
[warn] �[35m[Appium]�[39m Setting 'automationName=UiAutomator2' by default and using the
[warn] �[35m[Appium]�[39m UiAutomator2 Driver
[warn] �[35m[Appium]�[39m
[warn] �[35m[Appium]�[39m The next major version of Appium (2.x) will require the
[warn] �[35m[Appium]�[39m 'automationName' capability to be set for all sessions on all
[warn] �[35m[Appium]�[39m platforms
[warn] �[35m[Appium]�[39m
[warn] �[35m[Appium]�[39m In previous versions (Appium <= 1.13.x), the default was
[warn] �[35m[Appium]�[39m 'automationName=UiAutomator1'
[warn] �[35m[Appium]�[39m
[warn] �[35m[Appium]�[39m If you wish to use that automation instead of UiAutomator2, please
[warn] �[35m[Appium]�[39m add 'automationName=UiAutomator1' to your desired capabilities
[warn] �[35m[Appium]�[39m
[warn] �[35m[Appium]�[39m For more information about drivers, please visit
[warn] �[35m[Appium]�[39m http://appium.io/docs/en/about-appium/intro/ and explore the
[warn] �[35m[Appium]�[39m 'Drivers' menu
[warn] �[35m[Appium]�[39m
[warn] �[35m[Appium]�[39m ======================================================================
[warn] �[35m[Appium]�[39m
[info] �[35m[Appium]�[39m Appium v1.15.1 creating new AndroidUiautomator2Driver (v1.37.2) session
[debug] �[35m[BaseDriver]�[39m Creating session with MJSONWP desired capabilities: {
[debug] �[35m[BaseDriver]�[39m "browserName": "chrome",
[debug] �[35m[BaseDriver]�[39m "platformName": "android",
[debug] �[35m[BaseDriver]�[39m "deviceName": "6b426af90906",
[debug] �[35m[BaseDriver]�[39m "count": 1
[debug] �[35m[BaseDriver]�[39m }
[warn] �[35m[BaseDriver]�[39m The following capabilities were provided, but are not recognized by Appium:
[warn] �[35m[BaseDriver]�[39m count
[info] �[35m[BaseDriver]�[39m Session created with session id: 57c9db63-79ff-4365-9250-7826bf028b03
[info] �[35m[UiAutomator2]�[39m We're going to run a Chrome-based session
[info] �[35m[UiAutomator2]�[39m Chrome-type package and activity are com.android.chrome and com.google.android.apps.chrome.Main
[info] �[35m[UiAutomator2]�[39m Starting 'com.android.chrome' directly on the device[info] �[35m[ADB]�[39m Using 'adb.exe' from 'C:\Users\z029678\Desktop\Appium\platform-tools\adb.exe'
[info] �[35m[AndroidDriver]�[39m Retrieving device list
[debug] �[35m[ADB]�[39m Trying to find a connected android device
[debug] �[35m[ADB]�[39m Getting connected devices...[debug] �[35m[ADB]�[39m Connected devices: [{"udid":"6b426af90906","state":"device"}]
[info] �[35m[AndroidDriver]�[39m Using device: 6b426af90906
[info] �[35m[ADB]�[39m Using 'adb.exe' from 'C:\Users\z029678\Desktop\Appium\platform-tools\adb.exe'
[debug] �[35m[ADB]�[39m Setting device id to 6b426af90906
[debug] �[35m[ADB]�[39m Running 'C:\Users\z029678\Desktop\Appium\platform-tools\adb.exe -P 5037 -s 6b426af90906 shell getprop ro.build.version.sdk'[debug] �[35m[ADB]�[39m Current device property 'ro.build.version.sdk': 28
[debug] �[35m[ADB]�[39m Running 'C:\Users\z029678\Desktop\Appium\platform-tools\adb.exe -P 5037 -s 6b426af90906 shell getprop ro.build.version.release'
[debug] �[35m[ADB]�[39m Current device property 'ro.build.version.release': 9
[debug] �[35m[ADB]�[39m Device API level: 28
[warn] �[35m[UiAutomator2]�[39m Relaxing hidden api policy
[debug] �[35m[ADB]�[39m Running 'C:\Users\z029678\Desktop\Appium\platform-tools\adb.exe -P 5037 -s 6b426af90906 shell settings put global hidden_api_policy_pre_p_apps 1'[debug] �[35m[ADB]�[39m Running 'C:\Users\z029678\Desktop\Appium\platform-tools\adb.exe -P 5037 -s 6b426af90906 shell settings put global hidden_api_policy_p_apps 1'[debug] �[35m[ADB]�[39m Running 'C:\Users\z029678\Desktop\Appium\platform-tools\adb.exe -P 5037 -s 6b426af90906 shell settings put global hidden_api_policy 1'
[warn] �[35m[AndroidDriver]�[39m No app sent in, not parsing package/activity
[debug] �[35m[ADB]�[39m Running 'C:\Users\z029678\Desktop\Appium\platform-tools\adb.exe -P 5037 -s 6b426af90906 wait-for-device'[debug] �[35m[ADB]�[39m Running 'C:\Users\z029678\Desktop\Appium\platform-tools\adb.exe -P 5037 -s 6b426af90906 shell echo ping'
[debug] �[35m[AndroidDriver]�[39m Pushing settings apk to device...
[debug] �[35m[ADB]�[39m Getting install status for io.appium.settings
[debug] �[35m[ADB]�[39m Running 'C:\Users\z029678\Desktop\Appium\platform-tools\adb.exe -P 5037 -s 6b426af90906 shell dumpsys package io.appium.settings'[debug] �[35m[ADB]�[39m 'io.appium.settings' is installed
[debug] �[35m[ADB]�[39m Getting package info for 'io.appium.settings'
[debug] �[35m[ADB]�[39m Running 'C:\Users\z029678\Desktop\Appium\platform-tools\adb.exe -P 5037 -s 6b426af90906 shell dumpsys package io.appium.settings'[info] �[35m[ADB]�[39m Cannot extract apk info using apkanalyzer. Falling back to aapt. Original error: Could not find 'apkanalyzer.bat' in ["C:\Users\z029678\Desktop\Appium\platform-tools\apkanalyzer.bat","C:\Users\z029678\Desktop\Appium\emulator\apkanalyzer.bat","C:\Users\z029678\Desktop\Appium\tools\apkanalyzer.bat","C:\Users\z029678\Desktop\Appium\tools\bin\apkanalyzer.bat","C:\Users\z029678\Desktop\Appium\build-tools\29.0.3\apkanalyzer.bat"]. Do you have Android Build Tools installed at 'C:\Users\z029678\Desktop\Appium'?
[info] �[35m[ADB]�[39m Using 'aapt.exe' from 'C:\Users\z029678\Desktop\Appium\build-tools\29.0.3\aapt.exe'
[debug] �[35m[ADB]�[39m The version name of the installed 'io.appium.settings' is greater or equal to the application version name ('2.14.2' >= '2.14.2')
[debug] �[35m[ADB]�[39m There is no need to install/upgrade 'C:\Program Files\Appium\resources\app\node_modules\appium\node_modules\io.appium.settings\apks\settings_apk-debug.apk'
[debug] �[35m[ADB]�[39m Getting IDs of all 'io.appium.settings' processes
[debug] �[35m[ADB]�[39m Running 'C:\Users\z029678\Desktop\Appium\platform-tools\adb.exe -P 5037 -s 6b426af90906 shell 'pgrep --help; echo $?''[debug] �[35m[ADB]�[39m Running 'C:\Users\z029678\Desktop\Appium\platform-tools\adb.exe -P 5037 -s 6b426af90906 shell pgrep -f io\.appium\.settings'[debug] �[35m[AndroidDriver]�[39m io.appium.settings is already running. There is no need to reset its permissions.
[debug] �[35m[ADB]�[39m Running 'C:\Users\z029678\Desktop\Appium\platform-tools\adb.exe -P 5037 -s 6b426af90906 shell appops set io.appium.settings android:mock_location allow'
[debug] �[35m[Logcat]�[39m Starting logcat capture[info] �[35m[UiAutomator2]�[39m Server package at 'C:\Program Files\Appium\resources\app\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-v4.3.0.apk' is not writeable. Will copy it into the temporary location at 'C:\Users\z029678\AppData\Local\Temp\2020329-12244-1guzlvk.xddz' as a workaround. Consider making this file writeable manually in order to improve the performance of session startup.
[info] �[35m[UiAutomator2]�[39m Server package at 'C:\Program Files\Appium\resources\app\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-debug-androidTest.apk' is not writeable. Will copy it into the temporary location at 'C:\Users\z029678\AppData\Local\Temp\2020329-12244-1guzlvk.xddz' as a workaround. Consider making this file writeable manually in order to improve the performance of session startup.
[debug] �[35m[ADB]�[39m Getting install status for io.appium.uiautomator2.server
[debug] �[35m[ADB]�[39m Running 'C:\Users\z029678\Desktop\Appium\platform-tools\adb.exe -P 5037 -s 6b426af90906 shell dumpsys package io.appium.uiautomator2.server'[debug] �[35m[ADB]�[39m 'io.appium.uiautomator2.server' is installed
[debug] �[35m[ADB]�[39m Getting package info for 'io.appium.uiautomator2.server'
[debug] �[35m[ADB]�[39m Running 'C:\Users\z029678\Desktop\Appium\platform-tools\adb.exe -P 5037 -s 6b426af90906 shell dumpsys package io.appium.uiautomator2.server'
[info] �[35m[ADB]�[39m Cannot extract apk info using apkanalyzer. Falling back to aapt. Original error: Could not find 'apkanalyzer.bat' in ["C:\Users\z029678\Desktop\Appium\platform-tools\apkanalyzer.bat","C:\Users\z029678\Desktop\Appium\emulator\apkanalyzer.bat","C:\Users\z029678\Desktop\Appium\tools\apkanalyzer.bat","C:\Users\z029678\Desktop\Appium\tools\bin\apkanalyzer.bat","C:\Users\z029678\Desktop\Appium\build-tools\29.0.3\apkanalyzer.bat"]. Do you have Android Build Tools installed at 'C:\Users\z029678\Desktop\Appium'?
[debug] �[35m[ADB]�[39m The version name of the installed 'io.appium.uiautomator2.server' is greater or equal to the application version name ('4.3.0' >= '4.3.0')
[debug] �[35m[UiAutomator2]�[39m io.appium.uiautomator2.server installation state: sameVersionInstalled
[debug] �[35m[ADB]�[39m Checking app cert for C:\Users\z029678\AppData\Local\Temp\2020329-12244-1guzlvk.xddz\appium-uiautomator2-server-v4.3.0.apk
[info] �[35m[ADB]�[39m Using 'apksigner.bat' from 'C:\Users\z029678\Desktop\Appium\build-tools\29.0.3\apksigner.bat'
[debug] �[35m[ADB]�[39m Starting 'C:\Users\z029678\Desktop\Appium\build-tools\29.0.3\apksigner.bat' with args '["verify","--print-certs","C:\Users\z029678\AppData\Local\Temp\2020329-12244-1guzlvk.xddz\appium-uiautomator2-server-v4.3.0.apk"]'[debug] �[35m[ADB]�[39m apksigner stdout: Signer #1 certificate DN: EMAILADDRESS=android@android.com, CN=Android, OU=Android, O=Android, L=Mountain View, ST=California, C=US
[debug] �[35m[ADB]�[39m Signer #1 certificate SHA-256 digest: a40da80a59d170caa950cf15c18c454d47a39b26989d8b640ecd745ba71bf5dc
[debug] �[35m[ADB]�[39m Signer #1 certificate SHA-1 digest: 61ed377e85d386a8dfee6b864bd85b0bfaa5af81
[debug] �[35m[ADB]�[39m Signer #1 certificate MD5 digest: e89b158e4bcf988ebd09eb83f5378e87
[debug] �[35m[ADB]�[39m
[debug] �[35m[ADB]�[39m apksigner stderr: ERROR: Registry editing has been disabled by your administrator.
[debug] �[35m[ADB]�[39m
[debug] �[35m[ADB]�[39m 'C:\Users\z029678\AppData\Local\Temp\2020329-12244-1guzlvk.xddz\appium-uiautomator2-server-v4.3.0.apk' is already signed.
[debug] �[35m[ADB]�[39m Getting install status for io.appium.uiautomator2.server.test
[debug] �[35m[ADB]�[39m Running 'C:\Users\z029678\Desktop\Appium\platform-tools\adb.exe -P 5037 -s 6b426af90906 shell dumpsys package io.appium.uiautomator2.server.test'[debug] �[35m[ADB]�[39m 'io.appium.uiautomator2.server.test' is installed
[debug] �[35m[ADB]�[39m Checking app cert for C:\Users\z029678\AppData\Local\Temp\2020329-12244-1guzlvk.xddz\appium-uiautomator2-server-debug-androidTest.apk
[debug] �[35m[ADB]�[39m Starting 'C:\Users\z029678\Desktop\Appium\build-tools\29.0.3\apksigner.bat' with args '["verify","--print-certs","C:\Users\z029678\AppData\Local\Temp\2020329-12244-1guzlvk.xddz\appium-uiautomator2-server-debug-androidTest.apk"]'[debug] �[35m[ADB]�[39m apksigner stdout: Signer #1 certificate DN: CN=Android Debug, O=Android, C=US
[debug] �[35m[ADB]�[39m Signer #1 certificate SHA-256 digest: 3e4f2ab66d641bbbd363421151755f8b12b66ea37a5db43c52116596b7392a8e
[debug] �[35m[ADB]�[39m Signer #1 certificate SHA-1 digest: e24fc8971c0aad07d1df6cc62af7fb0d48b45b60
[debug] �[35m[ADB]�[39m Signer #1 certificate MD5 digest: 5623d53469c7f7147b52ace9d09901eb
[debug] �[35m[ADB]�[39m
[debug] �[35m[ADB]�[39m apksigner stderr: ERROR: Registry editing has been disabled by your administrator.
[debug] �[35m[ADB]�[39m
[debug] �[35m[ADB]�[39m 'C:\Users\z029678\AppData\Local\Temp\2020329-12244-1guzlvk.xddz\appium-uiautomator2-server-debug-androidTest.apk' is signed with non-default certificate
[info] �[35m[ADB]�[39m Using 'zipalign.exe' from 'C:\Users\z029678\Desktop\Appium\build-tools\29.0.3\zipalign.exe'
[debug] �[35m[ADB]�[39m C:\Users\z029678\AppData\Local\Temp\2020329-12244-1guzlvk.xddz\appium-uiautomator2-server-debug-androidTest.apk' is already zip-aligned. Doing nothing
[debug] �[35m[ADB]�[39m Signing 'C:\Users\z029678\AppData\Local\Temp\2020329-12244-1guzlvk.xddz\appium-uiautomator2-server-debug-androidTest.apk' with default cert
[debug] �[35m[ADB]�[39m Starting 'C:\Users\z029678\Desktop\Appium\build-tools\29.0.3\apksigner.bat' with args '["sign","--key","C:\Program Files\Appium\resources\app\node_modules\appium\node_modules\appium-adb\keys\testkey.pk8","--cert","C:\Program Files\Appium\resources\app\node_modules\appium\node_modules\appium-adb\keys\testkey.x509.pem","C:\Users\z029678\AppData\Local\Temp\2020329-12244-1guzlvk.xddz\appium-uiautomator2-server-debug-androidTest.apk"]'[debug] �[35m[ADB]�[39m apksigner stderr: ERROR: Registry editing has been disabled by your administrator.
[debug] �[35m[ADB]�[39m
[info] �[35m[UiAutomator2]�[39m Server packages are going to be (re)installed
[info] �[35m[UiAutomator2]�[39m Full packages reinstall is going to be performed
[debug] �[35m[ADB]�[39m Uninstalling io.appium.uiautomator2.server
[debug] �[35m[ADB]�[39m Getting install status for io.appium.uiautomator2.server
[debug] �[35m[ADB]�[39m Running 'C:\Users\z029678\Desktop\Appium\platform-tools\adb.exe -P 5037 -s 6b426af90906 shell dumpsys package io.appium.uiautomator2.server'[debug] �[35m[ADB]�[39m 'io.appium.uiautomator2.server' is installed
[debug] �[35m[ADB]�[39m Running 'C:\Users\z029678\Desktop\Appium\platform-tools\adb.exe -P 5037 -s 6b426af90906 shell am force-stop io.appium.uiautomator2.server'[debug] �[35m[ADB]�[39m Running 'C:\Users\z029678\Desktop\Appium\platform-tools\adb.exe -P 5037 -s 6b426af90906 uninstall io.appium.uiautomator2.server'
[debug] �[35m[Instrumentation]�[39m INSTRUMENTATION_RESULT: shortMsg=Process crashed.
[debug] �[35m[Instrumentation]�[39m INSTRUMENTATION_CODE: 0[debug] �[35m[Instrumentation]�[39m The process has exited with code 0[debug] �[35m[ADB]�[39m 'adb uninstall io.appium.uiautomator2.server' command output: Success
[info] �[35m[ADB]�[39m io.appium.uiautomator2.server was successfully uninstalled
[debug] �[35m[ADB]�[39m Running 'C:\Users\z029678\Desktop\Appium\platform-tools\adb.exe -P 5037 -s 6b426af90906 shell 'ls -t -1 /data/local/tmp/appium_cache 2>&1 || echo ERROR''[debug] �[35m[ADB]�[39m The count of applications in the cache: 3
[info] �[35m[ADB]�[39m The application at 'C:\Users\z029678\AppData\Local\Temp\2020329-12244-1guzlvk.xddz\appium-uiautomator2-server-v4.3.0.apk' is already cached to '/data/local/tmp/appium_cache/0cc1725a60a05dbb5d0d09256f2fc6ece7e3b10f.apk'
[debug] �[35m[ADB]�[39m Running 'C:\Users\z029678\Desktop\Appium\platform-tools\adb.exe -P 5037 -s 6b426af90906 shell pm install -r /data/local/tmp/appium_cache/0cc1725a60a05dbb5d0d09256f2fc6ece7e3b10f.apk'[info] �[35m[ADB]�[39m The installation of 'appium-uiautomator2-server-v4.3.0.apk' took 8.657s
[debug] �[35m[ADB]�[39m Install command stdout: Success
[debug] �[35m[ADB]�[39m Uninstalling io.appium.uiautomator2.server.test
[debug] �[35m[ADB]�[39m Getting install status for io.appium.uiautomator2.server.test
[debug] �[35m[ADB]�[39m Running 'C:\Users\z029678\Desktop\Appium\platform-tools\adb.exe -P 5037 -s 6b426af90906 shell dumpsys package io.appium.uiautomator2.server.test'[debug] �[35m[ADB]�[39m 'io.appium.uiautomator2.server.test' is installed
[debug] �[35m[ADB]�[39m Running 'C:\Users\z029678\Desktop\Appium\platform-tools\adb.exe -P 5037 -s 6b426af90906 shell am force-stop io.appium.uiautomator2.server.test'[debug] �[35m[ADB]�[39m Running 'C:\Users\z029678\Desktop\Appium\platform-tools\adb.exe -P 5037 -s 6b426af90906 uninstall io.appium.uiautomator2.server.test'[debug] �[35m[ADB]�[39m 'adb uninstall io.appium.uiautomator2.server.test' command output: Success
[info] �[35m[ADB]�[39m io.appium.uiautomator2.server.test was successfully uninstalled
[debug] �[35m[ADB]�[39m Running 'C:\Users\z029678\Desktop\Appium\platform-tools\adb.exe -P 5037 -s 6b426af90906 shell 'ls -t -1 /data/local/tmp/appium_cache 2>&1 || echo ERROR''[info] �[35m[ADB]�[39m The installation of 'appium-uiautomator2-server-debug-androidTest.apk' took 4.237s
[debug] �[35m[ADB]�[39m Install command stdout: Success
[debug] �[35m[UiAutomator2]�[39m Waiting up to 30000ms for services to be available
[debug] �[35m[ADB]�[39m Running 'C:\Users\z029678\Desktop\Appium\platform-tools\adb.exe -P 5037 -s 6b426af90906 shell pm list instrumentation'[debug] �[35m[UiAutomator2]�[39m Instrumentation target 'io.appium.uiautomator2.server.test/androidx.test.runner.AndroidJUnitRunner' is available
[debug] �[35m[UiAutomator2]�[39m Forwarding UiAutomator2 Server port 6790 to 8200
[debug] �[35m[ADB]�[39m Forwarding system: 8200 to device: 6790
[debug] �[35m[ADB]�[39m Running 'C:\Users\z029678\Desktop\Appium\platform-tools\adb.exe -P 5037 -s 6b426af90906 forward tcp:8200 tcp:6790'
[debug] �[35m[UiAutomator2]�[39m No app capability. Assuming it is already on the device
[debug] �[35m[ADB]�[39m Getting install status for com.android.chrome
[debug] �[35m[ADB]�[39m Running 'C:\Users\z029678\Desktop\Appium\platform-tools\adb.exe -P 5037 -s 6b426af90906 shell dumpsys package com.android.chrome'[debug] �[35m[ADB]�[39m 'com.android.chrome' is installed
[debug] �[35m[ADB]�[39m Running 'C:\Users\z029678\Desktop\Appium\platform-tools\adb.exe -P 5037 -s 6b426af90906 shell am force-stop com.android.chrome'
[debug] �[35m[ADB]�[39m Running 'C:\Users\z029678\Desktop\Appium\platform-tools\adb.exe -P 5037 -s 6b426af90906 shell pm clear com.android.chrome'[debug] �[35m[AndroidDriver]�[39m Performed fast reset on the installed 'com.android.chrome' application (stop and clear)
[debug] �[35m[UiAutomator2]�[39m Performing shallow cleanup of automation leftovers[debug] �[35m[UiAutomator2]�[39m No obsolete sessions have been detected (Error: ESOCKETTIMEDOUT)
[debug] �[35m[ADB]�[39m Running 'C:\Users\z029678\Desktop\Appium\platform-tools\adb.exe -P 5037 -s 6b426af90906 shell am force-stop io.appium.uiautomator2.server.test'[info] �[35m[UiAutomator2]�[39m Starting UIAutomator2 server 4.3.0
[info] �[35m[UiAutomator2]�[39m Using UIAutomator2 server from 'C:\Program Files\Appium\resources\app\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-v4.3.0.apk' and test from 'C:\Program Files\Appium\resources\app\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-debug-androidTest.apk'
[info] �[35m[UiAutomator2]�[39m Waiting up to 30000ms for UiAutomator2 to be online...
[debug] �[35m[ADB]�[39m Creating ADB subprocess with args: ["-P",5037,"-s","6b426af90906","shell","am","instrument","-w","io.appium.uiautomator2.server.test/androidx.test.runner.AndroidJUnitRunner"][debug] �[35m[WD Proxy]�[39m Matched '/status' to command name 'getStatus'
[debug] �[35m[WD Proxy]�[39m Proxying [GET /status] to [GET http://localhost:8200/wd/hub/status] with no body[info] �[35m[WD Proxy]�[39m Got an unexpected response with status 401:
[info] �[35m[WD Proxy]�[39m <TITLE>Access Denied</TITLE>
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m


[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m Access Denied (authentication_failed)
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m Your credentials could not be authenticated: "Credentials are missing.". You will not be permitted access until your credentials can be verified.
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m This is typically caused by an incorrect username and/or password, but could also be caused by network problems.
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m For assistance, contact your network support team.
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m [debug] �[35m[WD Proxy]�[39m Matched '/status' to command name 'getStatus'
[debug] �[35m[WD Proxy]�[39m Proxying [GET /status] to [GET http://localhost:8200/wd/hub/status] with no body[info] �[35m[WD Proxy]�[39m Got an unexpected response with status 401:
[info] �[35m[WD Proxy]�[39m <TITLE>Access Denied</TITLE>
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m Access Denied (authentication_failed)
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m Your credentials could not be authenticated: "Credentials are missing.". You will not be permitted access until your credentials can be verified.
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m This is typically caused by an incorrect username and/or password, but could also be caused by network problems.
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m For assistance, contact your network support team.
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m [debug] �[35m[WD Proxy]�[39m Matched '/status' to command name 'getStatus'
[debug] �[35m[WD Proxy]�[39m Proxying [GET /status] to [GET http://localhost:8200/wd/hub/status] with no body[info] �[35m[WD Proxy]�[39m Got an unexpected response with status 401:
[info] �[35m[WD Proxy]�[39m <TITLE>Access Denied</TITLE>
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m Access Denied (authentication_failed)
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m Your credentials could not be authenticated: "Credentials are missing.". You will not be permitted access until your credentials can be verified.
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m This is typically caused by an incorrect username and/or password, but could also be caused by network problems.
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m For assistance, contact your network support team.
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[debug] �[35m[Instrumentation]�[39m io.appium.uiautomator2.server.test.AppiumUiAutomator2Server:[debug] �[35m[WD Proxy]�[39m Matched '/status' to command name 'getStatus'
[debug] �[35m[WD Proxy]�[39m Proxying [GET /status] to [GET http://localhost:8200/wd/hub/status] with no body[info] �[35m[WD Proxy]�[39m Got an unexpected response with status 401:
[info] �[35m[WD Proxy]�[39m <TITLE>Access Denied</TITLE>
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m Access Denied (authentication_failed)
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m Your credentials could not be authenticated: "Credentials are missing.". You will not be permitted access until your credentials can be verified.
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m This is typically caused by an incorrect username and/or password, but could also be caused by network problems.
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m For assistance, contact your network support team.
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m [debug] �[35m[WD Proxy]�[39m Matched '/status' to command name 'getStatus'
[debug] �[35m[WD Proxy]�[39m Proxying [GET /status] to [GET http://localhost:8200/wd/hub/status] with no body[info] �[35m[WD Proxy]�[39m Got an unexpected response with status 401:
[info] �[35m[WD Proxy]�[39m <TITLE>Access Denied</TITLE>
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m Access Denied (authentication_failed)
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m Your credentials could not be authenticated: "Credentials are missing.". You will not be permitted access until your credentials can be verified.
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m This is typically caused by an incorrect username and/or password, but could also be caused by network problems.
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m For assistance, contact your network support team.
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m [debug] �[35m[WD Proxy]�[39m Matched '/status' to command name 'getStatus'
[debug] �[35m[WD Proxy]�[39m Proxying [GET /status] to [GET http://localhost:8200/wd/hub/status] with no body[info] �[35m[WD Proxy]�[39m Got an unexpected response with status 401:
[info] �[35m[WD Proxy]�[39m <TITLE>Access Denied</TITLE>
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m Access Denied (authentication_failed)
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m Your credentials could not be authenticated: "Credentials are missing.". You will not be permitted access until your credentials can be verified.
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m This is typically caused by an incorrect username and/or password, but could also be caused by network problems.
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m For assistance, contact your network support team.
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m [debug] �[35m[WD Proxy]�[39m Matched '/status' to command name 'getStatus'
[debug] �[35m[WD Proxy]�[39m Proxying [GET /status] to [GET http://localhost:8200/wd/hub/status] with no body[info] �[35m[WD Proxy]�[39m Got an unexpected response with status 401:
[info] �[35m[WD Proxy]�[39m <TITLE>Access Denied</TITLE>
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m Access Denied (authentication_failed)
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m Your credentials could not be authenticated: "Credentials are missing.". You will not be permitted access until your credentials can be verified.
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m This is typically caused by an incorrect username and/or password, but could also be caused by network problems.
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m For assistance, contact your network support team.
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m [debug] �[35m[WD Proxy]�[39m Matched '/status' to command name 'getStatus'
[debug] �[35m[WD Proxy]�[39m Proxying [GET /status] to [GET http://localhost:8200/wd/hub/status] with no body[info] �[35m[WD Proxy]�[39m Got an unexpected response with status 401:
[info] �[35m[WD Proxy]�[39m <TITLE>Access Denied</TITLE>
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m Access Denied (authentication_failed)
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m Your credentials could not be authenticated: "Credentials are missing.". You will not be permitted access until your credentials can be verified.
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m This is typically caused by an incorrect username and/or password, but could also be caused by network problems.
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m For assistance, contact your network support team.
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m [debug] �[35m[WD Proxy]�[39m Matched '/status' to command name 'getStatus'
[debug] �[35m[WD Proxy]�[39m Proxying [GET /status] to [GET http://localhost:8200/wd/hub/status] with no body[info] �[35m[WD Proxy]�[39m Got an unexpected response with status 401:
[info] �[35m[WD Proxy]�[39m <TITLE>Access Denied</TITLE>
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m Access Denied (authentication_failed)
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m Your credentials could not be authenticated: "Credentials are missing.". You will not be permitted access until your credentials can be verified.
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m This is typically caused by an incorrect username and/or password, but could also be caused by network problems.
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m For assistance, contact your network support team.
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m [debug] �[35m[WD Proxy]�[39m Matched '/status' to command name 'getStatus'
[debug] �[35m[WD Proxy]�[39m Proxying [GET /status] to [GET http://localhost:8200/wd/hub/status] with no body[info] �[35m[WD Proxy]�[39m Got an unexpected response with status 401:
[info] �[35m[WD Proxy]�[39m <TITLE>Access Denied</TITLE>
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m Access Denied (authentication_failed)
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m Your credentials could not be authenticated: "Credentials are missing.". You will not be permitted access until your credentials can be verified.
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m This is typically caused by an incorrect username and/or password, but could also be caused by network problems.
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m For assistance, contact your network support team.
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m [debug] �[35m[WD Proxy]�[39m Matched '/status' to command name 'getStatus'
[debug] �[35m[WD Proxy]�[39m Proxying [GET /status] to [GET http://localhost:8200/wd/hub/status] with no body[info] �[35m[WD Proxy]�[39m Got an unexpected response with status 401:
[info] �[35m[WD Proxy]�[39m <TITLE>Access Denied</TITLE>
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m Access Denied (authentication_failed)
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m Your credentials could not be authenticated: "Credentials are missing.". You will not be permitted access until your credentials can be verified.
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m This is typically caused by an incorrect username and/or password, but could also be caused by network problems.
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m For assistance, contact your network support team.
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m [debug] �[35m[WD Proxy]�[39m Matched '/status' to command name 'getStatus'
[debug] �[35m[WD Proxy]�[39m Proxying [GET /status] to [GET http://localhost:8200/wd/hub/status] with no body[info] �[35m[WD Proxy]�[39m Got an unexpected response with status 401:
[info] �[35m[WD Proxy]�[39m <TITLE>Access Denied</TITLE>
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m Access Denied (authentication_failed)
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m Your credentials could not be authenticated: "Credentials are missing.". You will not be permitted access until your credentials can be verified.
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m This is typically caused by an incorrect username and/or password, but could also be caused by network problems.
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m For assistance, contact your network support team.
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m [debug] �[35m[WD Proxy]�[39m Matched '/status' to command name 'getStatus'
[debug] �[35m[WD Proxy]�[39m Proxying [GET /status] to [GET http://localhost:8200/wd/hub/status] with no body[info] �[35m[WD Proxy]�[39m Got an unexpected response with status 401:
[info] �[35m[WD Proxy]�[39m <TITLE>Access Denied</TITLE>
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m Access Denied (authentication_failed)
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m Your credentials could not be authenticated: "Credentials are missing.". You will not be permitted access until your credentials can be verified.
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m This is typically caused by an incorrect username and/or password, but could also be caused by network problems.
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m For assistance, contact your network support team.
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m [debug] �[35m[WD Proxy]�[39m Matched '/status' to command name 'getStatus'
[debug] �[35m[WD Proxy]�[39m Proxying [GET /status] to [GET http://localhost:8200/wd/hub/status] with no body[info] �[35m[WD Proxy]�[39m Got an unexpected response with status 401:
[info] �[35m[WD Proxy]�[39m <TITLE>Access Denied</TITLE>
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m Access Denied (authentication_failed)
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m Your credentials could not be authenticated: "Credentials are missing.". You will not be permitted access until your credentials can be verified.
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m This is typically caused by an incorrect username and/or password, but could also be caused by network problems.
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m For assistance, contact your network support team.
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m [debug] �[35m[WD Proxy]�[39m Matched '/status' to command name 'getStatus'
[debug] �[35m[WD Proxy]�[39m Proxying [GET /status] to [GET http://localhost:8200/wd/hub/status] with no body[info] �[35m[WD Proxy]�[39m Got an unexpected response with status 401:
[info] �[35m[WD Proxy]�[39m <TITLE>Access Denied</TITLE>
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m Access Denied (authentication_failed)
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m Your credentials could not be authenticated: "Credentials are missing.". You will not be permitted access until your credentials can be verified.
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m This is typically caused by an incorrect username and/or password, but could also be caused by network problems.
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m For assistance, contact your network support team.
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m [debug] �[35m[WD Proxy]�[39m Matched '/status' to command name 'getStatus'
[debug] �[35m[WD Proxy]�[39m Proxying [GET /status] to [GET http://localhost:8200/wd/hub/status] with no body[info] �[35m[WD Proxy]�[39m Got an unexpected response with status 401:
[info] �[35m[WD Proxy]�[39m <TITLE>Access Denied</TITLE>
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m Access Denied (authentication_failed)
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m Your credentials could not be authenticated: "Credentials are missing.". You will not be permitted access until your credentials can be verified.
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m This is typically caused by an incorrect username and/or password, but could also be caused by network problems.
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m For assistance, contact your network support team.
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m [debug] �[35m[WD Proxy]�[39m Matched '/status' to command name 'getStatus'
[debug] �[35m[WD Proxy]�[39m Proxying [GET /status] to [GET http://localhost:8200/wd/hub/status] with no body[info] �[35m[WD Proxy]�[39m Got an unexpected response with status 401:
[info] �[35m[WD Proxy]�[39m <TITLE>Access Denied</TITLE>
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m Access Denied (authentication_failed)
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m Your credentials could not be authenticated: "Credentials are missing.". You will not be permitted access until your credentials can be verified.
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m This is typically caused by an incorrect username and/or password, but could also be caused by network problems.
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m For assistance, contact your network support team.
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m [debug] �[35m[WD Proxy]�[39m Matched '/status' to command name 'getStatus'
[debug] �[35m[WD Proxy]�[39m Proxying [GET /status] to [GET http://localhost:8200/wd/hub/status] with no body[info] �[35m[WD Proxy]�[39m Got an unexpected response with status 401:
[info] �[35m[WD Proxy]�[39m <TITLE>Access Denied</TITLE>
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m Access Denied (authentication_failed)
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m Your credentials could not be authenticated: "Credentials are missing.". You will not be permitted access until your credentials can be verified.
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m This is typically caused by an incorrect username and/or password, but could also be caused by network problems.
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m For assistance, contact your network support team.
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m [debug] �[35m[WD Proxy]�[39m Matched '/status' to command name 'getStatus'
[debug] �[35m[WD Proxy]�[39m Proxying [GET /status] to [GET http://localhost:8200/wd/hub/status] with no body[info] �[35m[WD Proxy]�[39m Got an unexpected response with status 401:
[info] �[35m[WD Proxy]�[39m <TITLE>Access Denied</TITLE>
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m Access Denied (authentication_failed)
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m Your credentials could not be authenticated: "Credentials are missing.". You will not be permitted access until your credentials can be verified.
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m This is typically caused by an incorrect username and/or password, but could also be caused by network problems.
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m For assistance, contact your network support team.
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m [debug] �[35m[WD Proxy]�[39m Matched '/status' to command name 'getStatus'
[debug] �[35m[WD Proxy]�[39m Proxying [GET /status] to [GET http://localhost:8200/wd/hub/status] with no body[info] �[35m[WD Proxy]�[39m Got an unexpected response with status 401:
[info] �[35m[WD Proxy]�[39m <TITLE>Access Denied</TITLE>
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m Access Denied (authentication_failed)
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m Your credentials could not be authenticated: "Credentials are missing.". You will not be permitted access until your credentials can be verified.
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m This is typically caused by an incorrect username and/or password, but could also be caused by network problems.
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m For assistance, contact your network support team.
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m [debug] �[35m[WD Proxy]�[39m Matched '/status' to command name 'getStatus'
[debug] �[35m[WD Proxy]�[39m Proxying [GET /status] to [GET http://localhost:8200/wd/hub/status] with no body[info] �[35m[WD Proxy]�[39m Got an unexpected response with status 401:
[info] �[35m[WD Proxy]�[39m <TITLE>Access Denied</TITLE>
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m Access Denied (authentication_failed)
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m Your credentials could not be authenticated: "Credentials are missing.". You will not be permitted access until your credentials can be verified.
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m This is typically caused by an incorrect username and/or password, but could also be caused by network problems.
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m For assistance, contact your network support team.
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m

[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[info] �[35m[WD Proxy]�[39m
[error] �[35m[UiAutomator2]�[39m Error: The instrumentation process cannot be initialized within 30000ms timeout. Make sure the application under test does not crash and investigate the logcat output. You could also try to increase the value of 'uiautomator2ServerLaunchTimeout' capability.
[error] �[35m[UiAutomator2]�[39m at Object.wrappedLogger.errorAndThrow (C:\Program Files\Appium\resources\app\node_modules\appium\node_modules\appium-support\lib\logging.js:79:13)
[error] �[35m[UiAutomator2]�[39m at UiAutomator2Server.errorAndThrow [as startSession] (C:\Program Files\Appium\resources\app\node_modules\appium\node_modules\appium-uiautomator2-driver\lib\uiautomator2.js:216:15)
[debug] �[35m[UiAutomator2]�[39m Deleting UiAutomator2 session
[debug] �[35m[UiAutomator2]�[39m Deleting UiAutomator2 server session
[debug] �[35m[WD Proxy]�[39m Matched '/' to command name 'deleteSession'
[warn] �[35m[UiAutomator2]�[39m Did not get confirmation UiAutomator2 deleteSession worked; Error was: UnknownError: An unknown server-side error occurred while processing the command. Original error: Trying to proxy a session command without session id
[debug] �[35m[Logcat]�[39m Stopping logcat capture
[debug] �[35m[ADB]�[39m Removing forwarded port socket connection: 8200
[debug] �[35m[ADB]�[39m Running 'C:\Users\z029678\Desktop\Appium\platform-tools\adb.exe -P 5037 -s 6b426af90906 forward --remove tcp:8200'
[info] �[35m[UiAutomator2]�[39m Restoring hidden api policy to the device default configuration
[debug] �[35m[ADB]�[39m Running 'C:\Users\z029678\Desktop\Appium\platform-tools\adb.exe -P 5037 -s 6b426af90906 shell settings delete global hidden_api_policy_pre_p_apps'[debug] �[35m[ADB]�[39m Running 'C:\Users\z029678\Desktop\Appium\platform-tools\adb.exe -P 5037 -s 6b426af90906 shell settings delete global hidden_api_policy_p_apps'[debug] �[35m[ADB]�[39m Running 'C:\Users\z029678\Desktop\Appium\platform-tools\adb.exe -P 5037 -s 6b426af90906 shell settings delete global hidden_api_policy'[debug] �[35m[BaseDriver]�[39m Event 'newSessionStarted' logged at 1588172991587 (20:39:51 GMT+0530 (India Standard Time))
[debug] �[35m[MJSONWP]�[39m Encountered internal error running command: Error: The instrumentation process cannot be initialized within 30000ms timeout. Make sure the application under test does not crash and investigate the logcat output. You could also try to increase the value of 'uiautomator2ServerLaunchTimeout' capability.
[debug] �[35m[MJSONWP]�[39m at Object.wrappedLogger.errorAndThrow (C:\Program Files\Appium\resources\app\node_modules\appium\node_modules\appium-support\lib\logging.js:79:13)
[debug] �[35m[MJSONWP]�[39m at UiAutomator2Server.errorAndThrow [as startSession] (C:\Program Files\Appium\resources\app\node_modules\appium\node_modules\appium-uiautomator2-driver\lib\uiautomator2.js:216:15)
[info] �[35m[HTTP]�[39m �[37m<-- POST /wd/hub/session �[39m�[31m500�[39m �[90m57313 ms - 388�[39m
[info] �[35m[HTTP]�[39m �[90m�[39m

@VinothArasu
Copy link

This is what my Terminal in protractor looks like
image

@KazuCocoa
Copy link
Member

What happens when you call adb shell am instrument command as below?
Then, Appium expects 200 responses will back against http://localhost:8200/wd/hub/status, but strangely your response was 401. I wonder something rout was wrong on your environment.

[info] �[35m[UiAutomator2]�[39m Waiting up to 30000ms for UiAutomator2 to be online...
[debug] �[35m[ADB]�[39m Creating ADB subprocess with args: ["-P",5037,"-s","6b426af90906","shell","am","instrument","-w","io.appium.uiautomator2.server.test/androidx.test.runner.AndroidJUnitRunner"][debug] �[35m[WD Proxy]�[39m Matched '/status' to command name 'getStatus'
[debug] �[35m[WD Proxy]�[39m Proxying [GET /status] to [GET http://localhost:8200/wd/hub/status] with no body[info] �[35m[WD Proxy]�[39m Got an unexpected response with status 401:

@MeinVFTesting
Copy link

I got the same error when using physical device and switching between different appium servers (on different computer). The solution that I got is to uninstall the Appium Settings app from the device and restart the appium process again.

Thank you.

@akshay-9964
Copy link

akshay-9964 commented Sep 8, 2022 •
edited

Hi team could anybody help me in resolving the above instrumentation process cannot be intialized, which others are facing above.
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
UIAutomator2 specific to uiautomator2 driver
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests