An unknown server-side error occurred while processing the command

[info] e[35m[Appium]e[39m Welcome to Appium v1.15.1

[info] e[35m[Appium]e[39m Non-default server args:
[info] e[35m[Appium]e[39m allowInsecure: {
[info] e[35m[Appium]e[39m }
[info] e[35m[Appium]e[39m denyInsecure: {
[info] e[35m[Appium]e[39m }
[info] e[35m[Appium]e[39m Appium REST http interface listener started on 0.0.0.0:4723[info] e[35m[HTTP]e[39m e[37m–>e[39m e[37mGETe[39m e[37m/wd/hub/sessionse[39m
[info] e[35m[HTTP]e[39m e[90m{}e[39m
[debug] e[35m[GENERIC]e[39m Calling AppiumDriver.getSessions() with args: []
[debug] e[35m[GENERIC]e[39m Responding to client with driver.getSessions() result: []
[info] e[35m[HTTP]e[39m e[37m<-- GET /wd/hub/sessions e[39me[32m200e[39m e[90m18 ms - 40e[39m
[info] e[35m[HTTP]e[39m e[90me[39m[info] e[35m[HTTP]e[39m e[37m–>e[39m e[37mPOSTe[39m e[37m/wd/hub/sessione[39m
[info] e[35m[HTTP]e[39m e[90m{“desiredCapabilities”:{“app”:“C:\Users\xxxx\Downloads\xxxx-prod-release.apk”,“deviceName”:“5200c479eaa935c3”,“platformName”:“Android”,“newCommandTimeout”:0,“connectHardwareKeyboard”:true}}e[39m
[debug] e[35m[MJSONWP]e[39m Calling AppiumDriver.createSession() with args: [{“app”:“C:\Users\xxxx\Downloads\xxxx-prod-release.apk”,“deviceName”:“5200c479eaa935c3”,“platformName”:“Android”,“newCommandTimeout”:0,“connectHardwareKeyboard”:true},null,null]
[debug] e[35m[BaseDriver]e[39m Event ‘newSessionRequested’ logged at 1585321343967 (18:02:23 GMT+0300 (Türkiye Standart Saati))
[warn] e[35m[Appium]e[39m
[warn] e[35m[Appium]e[39m ======================================================================
[warn] e[35m[Appium]e[39m DEPRECATION WARNING:
[warn] e[35m[Appium]e[39m
[warn] e[35m[Appium]e[39m The ‘automationName’ capability was not provided in the desired
[warn] e[35m[Appium]e[39m capabilities for this Android session
[warn] e[35m[Appium]e[39m
[warn] e[35m[Appium]e[39m Setting ‘automationName=UiAutomator2’ by default and using the
[warn] e[35m[Appium]e[39m UiAutomator2 Driver
[warn] e[35m[Appium]e[39m
[warn] e[35m[Appium]e[39m The next major version of Appium (2.x) will require the
[warn] e[35m[Appium]e[39m ‘automationName’ capability to be set for all sessions on all
[warn] e[35m[Appium]e[39m platforms
[warn] e[35m[Appium]e[39m
[warn] e[35m[Appium]e[39m In previous versions (Appium <= 1.13.x), the default was
[warn] e[35m[Appium]e[39m ‘automationName=UiAutomator1’
[warn] e[35m[Appium]e[39m
[warn] e[35m[Appium]e[39m If you wish to use that automation instead of UiAutomator2, please
[warn] e[35m[Appium]e[39m add ‘automationName=UiAutomator1’ to your desired capabilities
[warn] e[35m[Appium]e[39m
[warn] e[35m[Appium]e[39m For more information about drivers, please visit
[warn] e[35m[Appium]e[39m http://appium.io/docs/en/about-appium/intro/ and explore the
[warn] e[35m[Appium]e[39m ‘Drivers’ menu
[warn] e[35m[Appium]e[39m
[warn] e[35m[Appium]e[39m ======================================================================
[warn] e[35m[Appium]e[39m
[info] e[35m[Appium]e[39m Appium v1.15.1 creating new AndroidUiautomator2Driver (v1.37.2) session
[debug] e[35m[BaseDriver]e[39m Creating session with MJSONWP desired capabilities: {
[debug] e[35m[BaseDriver]e[39m “app”: “C:\Users\xxxx\Downloads\xxxx-prod-release.apk”,
[debug] e[35m[BaseDriver]e[39m “deviceName”: “5200c479eaa935c3”,
[debug] e[35m[BaseDriver]e[39m “platformName”: “Android”,
[debug] e[35m[BaseDriver]e[39m “newCommandTimeout”: 0,
[debug] e[35m[BaseDriver]e[39m “connectHardwareKeyboard”: true
[debug] e[35m[BaseDriver]e[39m }
[warn] e[35m[BaseDriver]e[39m The following capabilities were provided, but are not recognized by Appium:
[warn] e[35m[BaseDriver]e[39m connectHardwareKeyboard
[info] e[35m[BaseDriver]e[39m Session created with session id: ff6133e6-bcf2-446d-9836-a51f2a6535db[info] e[35m[ADB]e[39m Found 2 ‘build-tools’ folders under ‘C:\Users\xxxx\AppData\Local\Android\Sdk’ (newest first):
[info] e[35m[ADB]e[39m C:/Users/xxxx/AppData/Local/Android/Sdk/build-tools/30.0.0-rc2
[info] e[35m[ADB]e[39m C:/Users/xxxx/AppData/Local/Android/Sdk/build-tools/29.0.3
[info] e[35m[ADB]e[39m Using ‘adb.exe’ from ‘C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\adb.exe’
[info] e[35m[AndroidDriver]e[39m Retrieving device list
[debug] e[35m[ADB]e[39m Trying to find a connected android device
[debug] e[35m[ADB]e[39m Getting connected devices…
[debug] e[35m[ADB]e[39m Connected devices: [{“udid”:“5200c479eaa935c3”,“state”:“device”}]
[info] e[35m[AndroidDriver]e[39m Using device: 5200c479eaa935c3[debug] e[35m[ADB]e[39m Current device property ‘ro.build.version.sdk’: 26
[debug] e[35m[ADB]e[39m Device API level: 26
[debug] e[35m[AndroidDriver]e[39m Parsing package and activity from app manifest
[info] e[35m[ADB]e[39m Using the alternative activity name detection method because of: Could not find ‘apkanalyzer.bat’ in [“C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\apkanalyzer.bat”,“C:\Users\xxxx\AppData\Local\Android\Sdk\emulator\apkanalyzer.bat”,“C:\Users\xxxx\AppData\Local\Android\Sdk\tools\apkanalyzer.bat”,“C:\Users\xxxx\AppData\Local\Android\Sdk\tools\bin\apkanalyzer.bat”,“C:\Users\xxxx\AppData\Local\Android\Sdk\build-tools\30.0.0-rc2\apkanalyzer.bat”,“C:\Users\xxxx\AppData\Local\Android\Sdk\build-tools\29.0.3\apkanalyzer.bat”]. Do you have Android Build Tools installed at ‘C:\Users\xxxx\AppData\Local\Android\Sdk’?
[info] e[35m[ADB]e[39m Using ‘aapt.exe’ from ‘C:\Users\xxxx\AppData\Local\Android\Sdk\build-tools\30.0.0-rc2\aapt.exe’
[info] e[35m[ADB]e[39m Extracting package and launch activity from manifest[info] e[35m[ADB]e[39m Package name: ‘com.matriksdata.mobileiq’
[info] e[35m[ADB]e[39m Main activity name: ‘com.matriksdata.mobileiq.view.splash.SplashActivity’
[debug] e[35m[AndroidDriver]e[39m Parsed package and activity are: com.matriksdata.mobileiq/com.matriksdata.mobileiq.view.splash.SplashActivity
[debug] e[35m[ADB]e[39m Running ‘C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 5200c479eaa935c3 wait-for-device’
[debug] e[35m[ADB]e[39m Running ‘C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 5200c479eaa935c3 shell echo ping’
[debug] e[35m[AndroidDriver]e[39m Pushing settings apk to device…
[debug] e[35m[ADB]e[39m Getting install status for io.appium.settings
[debug] e[35m[ADB]e[39m Running ‘C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 5200c479eaa935c3 shell dumpsys package io.appium.settings’[debug] e[35m[ADB]e[39m ‘io.appium.settings’ is installed
[debug] e[35m[ADB]e[39m Getting package info for ‘io.appium.settings’
[debug] e[35m[ADB]e[39m Running ‘C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 5200c479eaa935c3 shell dumpsys package io.appium.settings’[info] e[35m[ADB]e[39m Cannot extract apk info using apkanalyzer. Falling back to aapt. Original error: Could not find ‘apkanalyzer.bat’ in [“C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\apkanalyzer.bat”,“C:\Users\xxxx\AppData\Local\Android\Sdk\emulator\apkanalyzer.bat”,“C:\Users\xxxx\AppData\Local\Android\Sdk\tools\apkanalyzer.bat”,“C:\Users\xxxx\AppData\Local\Android\Sdk\tools\bin\apkanalyzer.bat”,“C:\Users\xxxx\AppData\Local\Android\Sdk\build-tools\30.0.0-rc2\apkanalyzer.bat”,“C:\Users\xxxx\AppData\Local\Android\Sdk\build-tools\29.0.3\apkanalyzer.bat”]. Do you have Android Build Tools installed at ‘C:\Users\xxxx\AppData\Local\Android\Sdk’?
[debug] e[35m[ADB]e[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] e[35m[ADB]e[39m There is no need to install/upgrade ‘C:\Users\xxxx\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\io.appium.settings\apks\settings_apk-debug.apk’
[debug] e[35m[ADB]e[39m Getting IDs of all ‘io.appium.settings’ processes
[debug] e[35m[ADB]e[39m Running ‘C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 5200c479eaa935c3 shell ‘pgrep --help; echo $?’’
[debug] e[35m[ADB]e[39m Running ‘C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 5200c479eaa935c3 shell pgrep ^appium\.settings$’[debug] e[35m[ADB]e[39m Running ‘C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 5200c479eaa935c3 shell am start -n io.appium.settings/.Settings -a android.intent.action.MAIN -c android.intent.category.LAUNCHER’[debug] e[35m[ADB]e[39m Getting IDs of all ‘io.appium.settings’ processes
[debug] e[35m[ADB]e[39m Running ‘C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 5200c479eaa935c3 shell pgrep ^appium\.settings$’[debug] e[35m[ADB]e[39m Running ‘C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 5200c479eaa935c3 shell appops set io.appium.settings android:mock_location allow’[debug] e[35m[Logcat]e[39m Starting logcat capture
[debug] e[35m[ADB]e[39m Getting install status for io.appium.uiautomator2.server
[debug] e[35m[ADB]e[39m Running ‘C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 5200c479eaa935c3 shell dumpsys package io.appium.uiautomator2.server’[debug] e[35m[ADB]e[39m ‘io.appium.uiautomator2.server’ is installed
[debug] e[35m[ADB]e[39m Getting package info for ‘io.appium.uiautomator2.server’
[debug] e[35m[ADB]e[39m Running ‘C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 5200c479eaa935c3 shell dumpsys package io.appium.uiautomator2.server’
[info] e[35m[ADB]e[39m Cannot extract apk info using apkanalyzer. Falling back to aapt. Original error: Could not find ‘apkanalyzer.bat’ in [“C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\apkanalyzer.bat”,“C:\Users\xxxx\AppData\Local\Android\Sdk\emulator\apkanalyzer.bat”,“C:\Users\xxxx\AppData\Local\Android\Sdk\tools\apkanalyzer.bat”,“C:\Users\xxxx\AppData\Local\Android\Sdk\tools\bin\apkanalyzer.bat”,“C:\Users\xxxx\AppData\Local\Android\Sdk\build-tools\30.0.0-rc2\apkanalyzer.bat”,“C:\Users\xxxx\AppData\Local\Android\Sdk\build-tools\29.0.3\apkanalyzer.bat”]. Do you have Android Build Tools installed at ‘C:\Users\xxxx\AppData\Local\Android\Sdk’?
[debug] e[35m[ADB]e[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] e[35m[UiAutomator2]e[39m io.appium.uiautomator2.server installation state: sameVersionInstalled
[debug] e[35m[ADB]e[39m Checking app cert for C:\Users\xxxx\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-v4.3.0.apk
[info] e[35m[ADB]e[39m Using ‘apksigner.bat’ from ‘C:\Users\xxxx\AppData\Local\Android\Sdk\build-tools\30.0.0-rc2\apksigner.bat’
[debug] e[35m[ADB]e[39m Starting ‘C:\Users\xxxx\AppData\Local\Android\Sdk\build-tools\30.0.0-rc2\apksigner.bat’ with args ‘[“verify”,"–print-certs",“C:\Users\xxxx\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-v4.3.0.apk”]’[debug] e[35m[ADB]e[39m ‘C:\Users\xxxx\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-v4.3.0.apk’ is signed with non-default certificate
[info] e[35m[ADB]e[39m Using ‘zipalign.exe’ from ‘C:\Users\xxxx\AppData\Local\Android\Sdk\build-tools\30.0.0-rc2\zipalign.exe’
[debug] e[35m[ADB]e[39m C:\Users\xxxx\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-v4.3.0.apk’ is already zip-aligned. Doing nothing
[debug] e[35m[ADB]e[39m Signing ‘C:\Users\xxxx\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-v4.3.0.apk’ with default cert
[debug] e[35m[ADB]e[39m Starting ‘C:\Users\xxxx\AppData\Local\Android\Sdk\build-tools\30.0.0-rc2\apksigner.bat’ with args ‘[“sign”,"–key",“C:\Users\xxxx\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-adb\keys\testkey.pk8”,"–cert",“C:\Users\xxxx\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-adb\keys\testkey.x509.pem”,“C:\Users\xxxx\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-v4.3.0.apk”]’
[debug] e[35m[ADB]e[39m Getting install status for io.appium.uiautomator2.server.test
[debug] e[35m[ADB]e[39m Running ‘C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 5200c479eaa935c3 shell dumpsys package io.appium.uiautomator2.server.test’[debug] e[35m[ADB]e[39m ‘io.appium.uiautomator2.server.test’ is installed
[debug] e[35m[ADB]e[39m Checking app cert for C:\Users\xxxx\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-debug-androidTest.apk
[debug] e[35m[ADB]e[39m Starting ‘C:\Users\xxxx\AppData\Local\Android\Sdk\build-tools\30.0.0-rc2\apksigner.bat’ with args ‘[“verify”,"–print-certs",“C:\Users\xxxx\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-debug-androidTest.apk”]’
[debug] e[35m[ADB]e[39m ‘C:\Users\xxxx\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-debug-androidTest.apk’ is signed with non-default certificate
[debug] e[35m[ADB]e[39m C:\Users\xxxx\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-debug-androidTest.apk’ is already zip-aligned. Doing nothing
[debug] e[35m[ADB]e[39m Signing ‘C:\Users\xxxx\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-debug-androidTest.apk’ with default cert
[debug] e[35m[ADB]e[39m Starting ‘C:\Users\xxxx\AppData\Local\Android\Sdk\build-tools\30.0.0-rc2\apksigner.bat’ with args ‘[“sign”,"–key",“C:\Users\xxxx\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-adb\keys\testkey.pk8”,"–cert",“C:\Users\xxxx\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-adb\keys\testkey.x509.pem”,“C:\Users\xxxx\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-debug-androidTest.apk”]’
[info] e[35m[UiAutomator2]e[39m Server packages are going to be (re)installed
[info] e[35m[UiAutomator2]e[39m Full packages reinstall is going to be performed
[debug] e[35m[ADB]e[39m Uninstalling io.appium.uiautomator2.server
[debug] e[35m[ADB]e[39m Getting install status for io.appium.uiautomator2.server
[debug] e[35m[ADB]e[39m Running ‘C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 5200c479eaa935c3 shell dumpsys package io.appium.uiautomator2.server’[debug] e[35m[ADB]e[39m ‘io.appium.uiautomator2.server’ is installed
[debug] e[35m[ADB]e[39m Running ‘C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 5200c479eaa935c3 shell am force-stop io.appium.uiautomator2.server’[debug] e[35m[ADB]e[39m Running ‘C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 5200c479eaa935c3 uninstall io.appium.uiautomator2.server’[debug] e[35m[ADB]e[39m ‘adb uninstall io.appium.uiautomator2.server’ command output: Success
[info] e[35m[ADB]e[39m io.appium.uiautomator2.server was successfully uninstalled
[debug] e[35m[ADB]e[39m Running ‘C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 5200c479eaa935c3 shell ‘ls -t -1 /data/local/tmp/appium_cache 2>&1 || echo ERROR’’[debug] e[35m[ADB]e[39m The count of applications in the cache: 7
[info] e[35m[ADB]e[39m The application at ‘C:\Users\xxxx\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-v4.3.0.apk’ is already cached to ‘/data/local/tmp/appium_cache/0cc1725a60a05dbb5d0d09256f2fc6ece7e3b10f.apk’
[debug] e[35m[ADB]e[39m Running ‘C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 5200c479eaa935c3 shell pm install -r /data/local/tmp/appium_cache/0cc1725a60a05dbb5d0d09256f2fc6ece7e3b10f.apk’[info] e[35m[ADB]e[39m The installation of ‘appium-uiautomator2-server-v4.3.0.apk’ took 10.919s
[debug] e[35m[ADB]e[39m Install command stdout: Success
[debug] e[35m[ADB]e[39m Uninstalling io.appium.uiautomator2.server.test
[debug] e[35m[ADB]e[39m Getting install status for io.appium.uiautomator2.server.test
[debug] e[35m[ADB]e[39m Running ‘C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 5200c479eaa935c3 shell dumpsys package io.appium.uiautomator2.server.test’[debug] e[35m[ADB]e[39m ‘io.appium.uiautomator2.server.test’ is installed
[debug] e[35m[ADB]e[39m Running ‘C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 5200c479eaa935c3 shell am force-stop io.appium.uiautomator2.server.test’[debug] e[35m[ADB]e[39m Running ‘C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 5200c479eaa935c3 uninstall io.appium.uiautomator2.server.test’[debug] e[35m[ADB]e[39m ‘adb uninstall io.appium.uiautomator2.server.test’ command output: Success
[info] e[35m[ADB]e[39m io.appium.uiautomator2.server.test was successfully uninstalled
[debug] e[35m[ADB]e[39m Running ‘C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 5200c479eaa935c3 shell ‘ls -t -1 /data/local/tmp/appium_cache 2>&1 || echo ERROR’’[debug] e[35m[ADB]e[39m The count of applications in the cache: 7
[info] e[35m[ADB]e[39m The application at ‘C:\Users\xxxx\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-debug-androidTest.apk’ is already cached to ‘/data/local/tmp/appium_cache/0beede6c27af5c71c23a0d9d1c82a7a0b18390e0.apk’
[debug] e[35m[ADB]e[39m Running ‘C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 5200c479eaa935c3 shell pm install -r /data/local/tmp/appium_cache/0beede6c27af5c71c23a0d9d1c82a7a0b18390e0.apk’[info] e[35m[ADB]e[39m The installation of ‘appium-uiautomator2-server-debug-androidTest.apk’ took 3.699s
[debug] e[35m[ADB]e[39m Install command stdout: Success
[debug] e[35m[UiAutomator2]e[39m Waiting up to 30000ms for services to be available
[debug] e[35m[ADB]e[39m Running ‘C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 5200c479eaa935c3 shell pm list instrumentation’[debug] e[35m[UiAutomator2]e[39m Instrumentation target ‘io.appium.uiautomator2.server.test/androidx.test.runner.AndroidJUnitRunner’ is available
[debug] e[35m[UiAutomator2]e[39m Forwarding UiAutomator2 Server port 6790 to 8200
[debug] e[35m[ADB]e[39m Forwarding system: 8200 to device: 6790
[debug] e[35m[ADB]e[39m Running ‘C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 5200c479eaa935c3 forward tcp:8200 tcp:6790’[debug] e[35m[ADB]e[39m Checking app cert for C:\Users\xxxx\Downloads\xxxx-prod-release.apk
[debug] e[35m[ADB]e[39m Starting ‘C:\Users\xxxx\AppData\Local\Android\Sdk\build-tools\30.0.0-rc2\apksigner.bat’ with args ‘[“verify”,"–print-certs",“C:\Users\xxxx\Downloads\xxxx-prod-release.apk”]’
[debug] e[35m[ADB]e[39m ‘C:\Users\xxxx\Downloads\xxxx-prod-release.apk’ is signed with non-default certificate
[debug] e[35m[ADB]e[39m C:\Users\xxxx\Downloads\xxxx-prod-release.apk’ is already zip-aligned. Doing nothing
[debug] e[35m[ADB]e[39m Signing ‘C:\Users\xxxx\Downloads\xxxx-prod-release.apk’ with default cert
[debug] e[35m[ADB]e[39m Starting ‘C:\Users\xxxx\AppData\Local\Android\Sdk\build-tools\30.0.0-rc2\apksigner.bat’ with args ‘[“sign”,"–key",“C:\Users\xxxx\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-adb\keys\testkey.pk8”,"–cert",“C:\Users\xxxx\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-adb\keys\testkey.x509.pem”,“C:\Users\xxxx\Downloads\xxxx-prod-release.apk”]’[debug] e[35m[ADB]e[39m Getting install status for com.matriksdata.mobileiq
[debug] e[35m[ADB]e[39m Running ‘C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 5200c479eaa935c3 shell dumpsys package com.matriksdata.mobileiq’
[debug] e[35m[ADB]e[39m ‘com.matriksdata.mobileiq’ is installed
[debug] e[35m[ADB]e[39m Getting package info for ‘com.matriksdata.mobileiq’
[debug] e[35m[ADB]e[39m Running ‘C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 5200c479eaa935c3 shell dumpsys package com.matriksdata.mobileiq’[info] e[35m[ADB]e[39m Cannot extract apk info using apkanalyzer. Falling back to aapt. Original error: Could not find ‘apkanalyzer.bat’ in [“C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\apkanalyzer.bat”,“C:\Users\xxxx\AppData\Local\Android\Sdk\emulator\apkanalyzer.bat”,“C:\Users\xxxx\AppData\Local\Android\Sdk\tools\apkanalyzer.bat”,“C:\Users\xxxx\AppData\Local\Android\Sdk\tools\bin\apkanalyzer.bat”,“C:\Users\xxxx\AppData\Local\Android\Sdk\build-tools\30.0.0-rc2\apkanalyzer.bat”,“C:\Users\xxxx\AppData\Local\Android\Sdk\build-tools\29.0.3\apkanalyzer.bat”]. Do you have Android Build Tools installed at ‘C:\Users\xxxx\AppData\Local\Android\Sdk’?
[debug] e[35m[ADB]e[39m The version name of the installed ‘com.matriksdata.mobileiq’ is greater or equal to the application version name (‘0.4.0’ >= ‘0.4.0’)
[debug] e[35m[ADB]e[39m There is no need to install/upgrade ‘C:\Users\xxxx\Downloads\xxxx-prod-release.apk’
[info] e[35m[AndroidDriver]e[39m Performing fast reset on ‘com.matriksdata.mobileiq’
[debug] e[35m[ADB]e[39m Getting install status for com.matriksdata.mobileiq
[debug] e[35m[ADB]e[39m Running ‘C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 5200c479eaa935c3 shell dumpsys package com.matriksdata.mobileiq’
[debug] e[35m[ADB]e[39m ‘com.matriksdata.mobileiq’ is installed
[debug] e[35m[ADB]e[39m Running ‘C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 5200c479eaa935c3 shell am force-stop com.matriksdata.mobileiq’[debug] e[35m[ADB]e[39m Running ‘C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 5200c479eaa935c3 shell pm clear com.matriksdata.mobileiq’[debug] e[35m[AndroidDriver]e[39m Performed fast reset on the installed ‘com.matriksdata.mobileiq’ application (stop and clear)
[debug] e[35m[UiAutomator2]e[39m Performing shallow cleanup of automation leftovers
[debug] e[35m[UiAutomator2]e[39m No obsolete sessions have been detected (Error: socket hang up)
[debug] e[35m[ADB]e[39m Running ‘C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 5200c479eaa935c3 shell am force-stop io.appium.uiautomator2.server.test’
[info] e[35m[UiAutomator2]e[39m Starting UIAutomator2 server 4.3.0
[info] e[35m[UiAutomator2]e[39m Using UIAutomator2 server from ‘C:\Users\xxxx\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-v4.3.0.apk’ and test from ‘C:\Users\xxxx\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-debug-androidTest.apk’
[info] e[35m[UiAutomator2]e[39m Waiting up to 30000ms for UiAutomator2 to be online…
[debug] e[35m[ADB]e[39m Creating ADB subprocess with args: ["-P",5037,"-s",“5200c479eaa935c3”,“shell”,“am”,“instrument”,"-w",“io.appium.uiautomator2.server.test/androidx.test.runner.AndroidJUnitRunner”][debug] e[35m[Instrumentation]e[39m java.lang.SecurityException: Permission Denial: starting instrumentation ComponentInfo{io.appium.uiautomator2.server.test/androidx.test.runner.AndroidJUnitRunner} from pid=5228, uid=5228 not allowed because package io.appium.uiautomator2.server.test does not have a signature matching the target io.appium.uiautomator2.server
[debug] e[35m[Instrumentation]e[39m INSTRUMENTATION_STATUS: id=ActivityManagerService
[debug] e[35m[Instrumentation]e[39m INSTRUMENTATION_STATUS: Error=Permission Denial: starting instrumentation ComponentInfo{io.appium.uiautomator2.server.test/androidx.test.runner.AndroidJUnitRunner} from pid=5228, uid=5228 not allowed because package io.appium.uiautomator2.server.test does not have a signature matching the target io.appium.uiautomator2.server
[debug] e[35m[Instrumentation]e[39m INSTRUMENTATION_STATUS_CODE: -1
[debug] e[35m[Instrumentation]e[39m at android.os.Parcel.readException(Parcel.java:1967)
[debug] e[35m[Instrumentation]e[39m at android.os.Parcel.readException(Parcel.java:1913)
[debug] e[35m[Instrumentation]e[39m at android.app.IActivityManager$Stub$Proxy.startInstrumentation(IActivityManager.java:5586)
[debug] e[35m[Instrumentation]e[39m at com.android.commands.am.Instrument.run(Instrument.java:408)
[debug] e[35m[Instrumentation]e[39m at com.android.commands.am.Am.runInstrument(Am.java:232)
[debug] e[35m[Instrumentation]e[39m at com.android.commands.am.Am.onRun(Am.java:125)
[debug] e[35m[Instrumentation]e[39m at com.android.internal.os.BaseCommand.run(BaseCommand.java:54)
[debug] e[35m[Instrumentation]e[39m at com.android.commands.am.Am.main(Am.java:95)
[debug] e[35m[Instrumentation]e[39m at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)
[debug] e[35m[Instrumentation]e[39m at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:287)[warn] e[35m[UiAutomator2]e[39m The instrumentation process has been unexpectedly terminated. Retrying UiAutomator2 startup (#1 of 1)
[debug] e[35m[UiAutomator2]e[39m Performing strict cleanup of automation leftovers
[debug] e[35m[UiAutomator2]e[39m No obsolete sessions have been detected (Error: socket hang up)
[debug] e[35m[ADB]e[39m Running ‘C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 5200c479eaa935c3 shell am force-stop io.appium.uiautomator2.server.test’[debug] e[35m[ADB]e[39m Attempting to kill all uiautomator processes
[debug] e[35m[ADB]e[39m Getting IDs of all ‘uiautomator’ processes
[debug] e[35m[ADB]e[39m Running ‘C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 5200c479eaa935c3 shell pgrep ^uiautomator$’[info] e[35m[ADB]e[39m No ‘uiautomator’ process has been found[info] e[35m[UiAutomator2]e[39m Waiting up to 30000ms for UiAutomator2 to be online…
[debug] e[35m[ADB]e[39m Creating ADB subprocess with args: ["-P",5037,"-s",“5200c479eaa935c3”,“shell”,“am”,“instrument”,"-w",“io.appium.uiautomator2.server.test/androidx.test.runner.AndroidJUnitRunner”][debug] e[35m[Instrumentation]e[39m java.lang.SecurityException: Permission Denial: starting instrumentation ComponentInfo{io.appium.uiautomator2.server.test/androidx.test.runner.AndroidJUnitRunner} from pid=5305, uid=5305 not allowed because package io.appium.uiautomator2.server.test does not have a signature matching the target io.appium.uiautomator2.server
[debug] e[35m[Instrumentation]e[39m at android.os.Parcel.readException(Parcel.java:1967)
[debug] e[35m[Instrumentation]e[39m at android.os.Parcel.readException(Parcel.java:1913)
[debug] e[35m[Instrumentation]e[39m at android.app.IActivityManager$Stub$Proxy.startInstrumentation(IActivityManager.java:5586)
[debug] e[35m[Instrumentation]e[39m at com.android.commands.am.Instrument.run(Instrument.java:408)
[debug] e[35m[Instrumentation]e[39m at com.android.commands.am.Am.runInstrument(Am.java:232)
[debug] e[35m[Instrumentation]e[39m at com.android.commands.am.Am.onRun(Am.java:125)
[debug] e[35m[Instrumentation]e[39m at com.android.internal.os.BaseCommand.run(BaseCommand.java:54)
[debug] e[35m[Instrumentation]e[39m at com.android.commands.am.Am.main(Am.java:95)
[debug] e[35m[Instrumentation]e[39m at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)
[debug] e[35m[Instrumentation]e[39m at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:287)
[debug] e[35m[Instrumentation]e[39m INSTRUMENTATION_STATUS: id=ActivityManagerService
[debug] e[35m[Instrumentation]e[39m INSTRUMENTATION_STATUS: Error=Permission Denial: starting instrumentation ComponentInfo{io.appium.uiautomator2.server.test/androidx.test.runner.AndroidJUnitRunner} from pid=5305, uid=5305 not allowed because package io.appium.uiautomator2.server.test does not have a signature matching the target io.appium.uiautomator2.server
[debug] e[35m[Instrumentation]e[39m INSTRUMENTATION_STATUS_CODE: -1
[debug] e[35m[Instrumentation]e[39m The process has exited with code 1[error] e[35m[UiAutomator2]e[39m Error: The instrumentation process cannot be initialized. Make sure the application under test does not crash and investigate the logcat output.
[error] e[35m[UiAutomator2]e[39m at Object.wrappedLogger.errorAndThrow (C:\Users\xxxx\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-support\lib\logging.js:79:13)
[error] e[35m[UiAutomator2]e[39m at UiAutomator2Server.errorAndThrow [as startSession] (C:\Users\xxxx\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-uiautomator2-driver\lib\uiautomator2.js:227:13)
[debug] e[35m[UiAutomator2]e[39m Deleting UiAutomator2 session
[debug] e[35m[UiAutomator2]e[39m Deleting UiAutomator2 server session
[debug] e[35m[WD Proxy]e[39m Matched ‘/’ to command name ‘deleteSession’
[warn] e[35m[UiAutomator2]e[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] e[35m[ADB]e[39m Running ‘C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 5200c479eaa935c3 shell am force-stop com.matriksdata.mobileiq’
[debug] e[35m[Logcat]e[39m Stopping logcat capture
[debug] e[35m[ADB]e[39m Removing forwarded port socket connection: 8200
[debug] e[35m[ADB]e[39m Running ‘C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 5200c479eaa935c3 forward --remove tcp:8200’[debug] e[35m[BaseDriver]e[39m Event ‘newSessionStarted’ logged at 1585321375630 (18:02:55 GMT+0300 (Türkiye Standart Saati))
[debug] e[35m[MJSONWP]e[39m 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] e[35m[MJSONWP]e[39m at Object.wrappedLogger.errorAndThrow (C:\Users\xxxx\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-support\lib\logging.js:79:13)
[debug] e[35m[MJSONWP]e[39m at UiAutomator2Server.errorAndThrow [as startSession] (C:\Users\xxxx\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-uiautomator2-driver\lib\uiautomator2.js:227:13)
[info] e[35m[HTTP]e[39m e[37m<-- POST /wd/hub/session e[39me[31m500e[39m e[90m31665 ms - 274e[39m
[info] e[35m[HTTP]e[39m e[90me[39m
[info] e[35m[HTTP]e[39m e[37m–>e[39m e[37mDELETEe[39m e[37m/wd/hub/sessione[39m
[info] e[35m[HTTP]e[39m e[90m{}e[39m
[debug] e[35m[HTTP]e[39m No route found. Setting content type to ‘text/plain’
[info] e[35m[HTTP]e[39m e[37m<-- DELETE /wd/hub/session e[39me[33m404e[39m e[90m3 ms - 57e[39m
[info] e[35m[HTTP]e[39m e[90me[39m[info] e[35m[HTTP]e[39m e[37m–>e[39m e[37mPOSTe[39m e[37m/wd/hub/sessione[39m
[info] e[35m[HTTP]e[39m e[90m{“desiredCapabilities”:{“app”:“C:\Users\xxxx\Downloads\xxxx-prod-release.apk”,“deviceName”:“5200c479eaa935c3”,“platformName”:“Android”,“newCommandTimeout”:0,“connectHardwareKeyboard”:true}}e[39m
[debug] e[35m[MJSONWP]e[39m Calling AppiumDriver.createSession() with args: [{“app”:“C:\Users\xxxx\Downloads\xxxx-prod-release.apk”,“deviceName”:“5200c479eaa935c3”,“platformName”:“Android”,“newCommandTimeout”:0,“connectHardwareKeyboard”:true},null,null]
[debug] e[35m[BaseDriver]e[39m Event ‘newSessionRequested’ logged at 1585321385440 (18:03:05 GMT+0300 (Türkiye Standart Saati))
[warn] e[35m[Appium]e[39m
[warn] e[35m[Appium]e[39m ======================================================================
[warn] e[35m[Appium]e[39m DEPRECATION WARNING:
[warn] e[35m[Appium]e[39m
[warn] e[35m[Appium]e[39m The ‘automationName’ capability was not provided in the desired
[warn] e[35m[Appium]e[39m capabilities for this Android session
[warn] e[35m[Appium]e[39m
[warn] e[35m[Appium]e[39m Setting ‘automationName=UiAutomator2’ by default and using the
[warn] e[35m[Appium]e[39m UiAutomator2 Driver
[warn] e[35m[Appium]e[39m
[warn] e[35m[Appium]e[39m The next major version of Appium (2.x) will require the
[warn] e[35m[Appium]e[39m ‘automationName’ capability to be set for all sessions on all
[warn] e[35m[Appium]e[39m platforms
[warn] e[35m[Appium]e[39m
[warn] e[35m[Appium]e[39m In previous versions (Appium <= 1.13.x), the default was
[warn] e[35m[Appium]e[39m ‘automationName=UiAutomator1’
[warn] e[35m[Appium]e[39m
[warn] e[35m[Appium]e[39m If you wish to use that automation instead of UiAutomator2, please
[warn] e[35m[Appium]e[39m add ‘automationName=UiAutomator1’ to your desired capabilities
[warn] e[35m[Appium]e[39m
[warn] e[35m[Appium]e[39m For more information about drivers, please visit
[warn] e[35m[Appium]e[39m http://appium.io/docs/en/about-appium/intro/ and explore the
[warn] e[35m[Appium]e[39m ‘Drivers’ menu
[warn] e[35m[Appium]e[39m
[warn] e[35m[Appium]e[39m ======================================================================
[warn] e[35m[Appium]e[39m
[info] e[35m[Appium]e[39m Appium v1.15.1 creating new AndroidUiautomator2Driver (v1.37.2) session
[debug] e[35m[BaseDriver]e[39m Creating session with MJSONWP desired capabilities: {
[debug] e[35m[BaseDriver]e[39m “app”: “C:\Users\xxxx\Downloads\xxxx-prod-release.apk”,
[debug] e[35m[BaseDriver]e[39m “deviceName”: “5200c479eaa935c3”,
[debug] e[35m[BaseDriver]e[39m “platformName”: “Android”,
[debug] e[35m[BaseDriver]e[39m “newCommandTimeout”: 0,
[debug] e[35m[BaseDriver]e[39m “connectHardwareKeyboard”: true
[debug] e[35m[BaseDriver]e[39m }
[warn] e[35m[BaseDriver]e[39m The following capabilities were provided, but are not recognized by Appium:
[warn] e[35m[BaseDriver]e[39m connectHardwareKeyboard
[info] e[35m[BaseDriver]e[39m Session created with session id: 7863082f-e5e5-4cc7-871e-2c0f19473eae
[info] e[35m[BaseDriver]e[39m Using local app ‘C:\Users\xxxx\Downloads\xxxx-prod-release.apk’
[debug] e[35m[UiAutomator2]e[39m Checking whether app is actually present[info] e[35m[ADB]e[39m Using ‘adb.exe’ from ‘C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\adb.exe’
[info] e[35m[AndroidDriver]e[39m Retrieving device list
[debug] e[35m[ADB]e[39m Trying to find a connected android device
[debug] e[35m[ADB]e[39m Getting connected devices…[debug] e[35m[ADB]e[39m Connected devices: [{“udid”:“5200c479eaa935c3”,“state”:“device”}]
[info] e[35m[AndroidDriver]e[39m Using device: 5200c479eaa935c3
[info] e[35m[ADB]e[39m Using ‘adb.exe’ from ‘C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\adb.exe’
[debug] e[35m[ADB]e[39m Setting device id to 5200c479eaa935c3
[debug] e[35m[ADB]e[39m Running ‘C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 5200c479eaa935c3 shell getprop ro.build.version.sdk’
[debug] e[35m[ADB]e[39m Current device property ‘ro.build.version.sdk’: 26
[debug] e[35m[ADB]e[39m Device API level: 26
[debug] e[35m[AndroidDriver]e[39m Parsing package and activity from app manifest
[info] e[35m[ADB]e[39m Using the alternative activity name detection method because of: Could not find ‘apkanalyzer.bat’ in [“C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\apkanalyzer.bat”,“C:\Users\xxxx\AppData\Local\Android\Sdk\emulator\apkanalyzer.bat”,“C:\Users\xxxx\AppData\Local\Android\Sdk\tools\apkanalyzer.bat”,“C:\Users\xxxx\AppData\Local\Android\Sdk\tools\bin\apkanalyzer.bat”,“C:\Users\xxxx\AppData\Local\Android\Sdk\build-tools\30.0.0-rc2\apkanalyzer.bat”,“C:\Users\xxxx\AppData\Local\Android\Sdk\build-tools\29.0.3\apkanalyzer.bat”]. Do you have Android Build Tools installed at ‘C:\Users\xxxx\AppData\Local\Android\Sdk’?
[info] e[35m[ADB]e[39m Using ‘aapt.exe’ from ‘C:\Users\xxxx\AppData\Local\Android\Sdk\build-tools\30.0.0-rc2\aapt.exe’
[info] e[35m[ADB]e[39m Extracting package and launch activity from manifest
[info] e[35m[ADB]e[39m Package name: ‘com.matriksdata.mobileiq’
[info] e[35m[ADB]e[39m Main activity name: ‘com.matriksdata.mobileiq.view.splash.SplashActivity’
[debug] e[35m[AndroidDriver]e[39m Parsed package and activity are: com.matriksdata.mobileiq/com.matriksdata.mobileiq.view.splash.SplashActivity
[debug] e[35m[ADB]e[39m Running ‘C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 5200c479eaa935c3 wait-for-device’[debug] e[35m[ADB]e[39m Running ‘C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 5200c479eaa935c3 shell echo ping’
[debug] e[35m[AndroidDriver]e[39m Pushing settings apk to device…
[debug] e[35m[ADB]e[39m Getting install status for io.appium.settings
[debug] e[35m[ADB]e[39m Running ‘C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 5200c479eaa935c3 shell dumpsys package io.appium.settings’
[debug] e[35m[ADB]e[39m ‘io.appium.settings’ is not installed
[debug] e[35m[ADB]e[39m App ‘C:\Users\xxxx\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\io.appium.settings\apks\settings_apk-debug.apk’ is not installed
[debug] e[35m[ADB]e[39m Installing ‘C:\Users\xxxx\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\io.appium.settings\apks\settings_apk-debug.apk’[debug] e[35m[ADB]e[39m Running ‘C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 5200c479eaa935c3 shell ‘ls -t -1 /data/local/tmp/appium_cache 2>&1 || echo ERROR’’
[debug] e[35m[ADB]e[39m The count of applications in the cache: 7
[info] e[35m[ADB]e[39m The application at ‘C:\Users\xxxx\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\io.appium.settings\apks\settings_apk-debug.apk’ is already cached to ‘/data/local/tmp/appium_cache/3d97225b036c28750562ef8962defee6b1af19a4.apk’
[debug] e[35m[ADB]e[39m Running ‘C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 5200c479eaa935c3 shell pm install -g /data/local/tmp/appium_cache/3d97225b036c28750562ef8962defee6b1af19a4.apk’[info] e[35m[ADB]e[39m The installation of ‘settings_apk-debug.apk’ took 3.320s
[debug] e[35m[ADB]e[39m Install command stdout: Success
[debug] e[35m[ADB]e[39m Getting IDs of all ‘io.appium.settings’ processes
[debug] e[35m[ADB]e[39m Running ‘C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 5200c479eaa935c3 shell ‘pgrep --help; echo $?’’[debug] e[35m[ADB]e[39m Running ‘C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 5200c479eaa935c3 shell pgrep ^appium\.settings$’[debug] e[35m[ADB]e[39m Getting IDs of all ‘io.appium.settings’ processes
[debug] e[35m[ADB]e[39m Running ‘C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 5200c479eaa935c3 shell pgrep ^appium\.settings$’[debug] e[35m[ADB]e[39m Running ‘C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 5200c479eaa935c3 shell appops set io.appium.settings android:mock_location allow’
[debug] e[35m[Logcat]e[39m Starting logcat capture[debug] e[35m[ADB]e[39m Getting install status for io.appium.uiautomator2.server
[debug] e[35m[ADB]e[39m Running ‘C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 5200c479eaa935c3 shell dumpsys package io.appium.uiautomator2.server’[debug] e[35m[ADB]e[39m ‘io.appium.uiautomator2.server’ is installed
[debug] e[35m[ADB]e[39m Getting package info for ‘io.appium.uiautomator2.server’
[debug] e[35m[ADB]e[39m Running ‘C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 5200c479eaa935c3 shell dumpsys package io.appium.uiautomator2.server’
[info] e[35m[ADB]e[39m Cannot extract apk info using apkanalyzer. Falling back to aapt. Original error: Could not find ‘apkanalyzer.bat’ in [“C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\apkanalyzer.bat”,“C:\Users\xxxx\AppData\Local\Android\Sdk\emulator\apkanalyzer.bat”,“C:\Users\xxxx\AppData\Local\Android\Sdk\tools\apkanalyzer.bat”,“C:\Users\xxxx\AppData\Local\Android\Sdk\tools\bin\apkanalyzer.bat”,“C:\Users\xxxx\AppData\Local\Android\Sdk\build-tools\30.0.0-rc2\apkanalyzer.bat”,“C:\Users\xxxx\AppData\Local\Android\Sdk\build-tools\29.0.3\apkanalyzer.bat”]. Do you have Android Build Tools installed at ‘C:\Users\xxxx\AppData\Local\Android\Sdk’?[debug] e[35m[ADB]e[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] e[35m[UiAutomator2]e[39m io.appium.uiautomator2.server installation state: sameVersionInstalled
[debug] e[35m[ADB]e[39m Checking app cert for C:\Users\xxxx\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-v4.3.0.apk
[info] e[35m[ADB]e[39m Using ‘apksigner.bat’ from ‘C:\Users\xxxx\AppData\Local\Android\Sdk\build-tools\30.0.0-rc2\apksigner.bat’
[debug] e[35m[ADB]e[39m Starting ‘C:\Users\xxxx\AppData\Local\Android\Sdk\build-tools\30.0.0-rc2\apksigner.bat’ with args ‘[“verify”,"–print-certs",“C:\Users\xxxx\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-v4.3.0.apk”]’
[debug] e[35m[ADB]e[39m ‘C:\Users\xxxx\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-v4.3.0.apk’ is signed with non-default certificate
[info] e[35m[ADB]e[39m Using ‘zipalign.exe’ from ‘C:\Users\xxxx\AppData\Local\Android\Sdk\build-tools\30.0.0-rc2\zipalign.exe’
[debug] e[35m[ADB]e[39m C:\Users\xxxx\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-v4.3.0.apk’ is already zip-aligned. Doing nothing
[debug] e[35m[ADB]e[39m Signing ‘C:\Users\xxxx\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-v4.3.0.apk’ with default cert
[debug] e[35m[ADB]e[39m Starting ‘C:\Users\xxxx\AppData\Local\Android\Sdk\build-tools\30.0.0-rc2\apksigner.bat’ with args ‘[“sign”,"–key",“C:\Users\xxxx\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-adb\keys\testkey.pk8”,"–cert",“C:\Users\xxxx\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-adb\keys\testkey.x509.pem”,“C:\Users\xxxx\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-v4.3.0.apk”]’[debug] e[35m[ADB]e[39m Getting install status for io.appium.uiautomator2.server.test
[debug] e[35m[ADB]e[39m Running ‘C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 5200c479eaa935c3 shell dumpsys package io.appium.uiautomator2.server.test’
[debug] e[35m[ADB]e[39m ‘io.appium.uiautomator2.server.test’ is installed
[debug] e[35m[ADB]e[39m Checking app cert for C:\Users\xxxx\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-debug-androidTest.apk
[debug] e[35m[ADB]e[39m Starting ‘C:\Users\xxxx\AppData\Local\Android\Sdk\build-tools\30.0.0-rc2\apksigner.bat’ with args ‘[“verify”,"–print-certs",“C:\Users\xxxx\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-debug-androidTest.apk”]’
[debug] e[35m[ADB]e[39m ‘C:\Users\xxxx\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-debug-androidTest.apk’ is signed with non-default certificate[info] e[35m[UiAutomator2]e[39m Server packages are going to be (re)installed
[info] e[35m[UiAutomator2]e[39m Full packages reinstall is going to be performed
[debug] e[35m[ADB]e[39m Uninstalling io.appium.uiautomator2.server
[debug] e[35m[ADB]e[39m Getting install status for io.appium.uiautomator2.server
[debug] e[35m[ADB]e[39m Running ‘C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 5200c479eaa935c3 shell dumpsys package io.appium.uiautomator2.server’
[debug] e[35m[ADB]e[39m ‘io.appium.uiautomator2.server’ is installed
[debug] e[35m[ADB]e[39m Running ‘C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 5200c479eaa935c3 shell am force-stop io.appium.uiautomator2.server’[debug] e[35m[ADB]e[39m Running ‘C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 5200c479eaa935c3 uninstall io.appium.uiautomator2.server’[debug] e[35m[ADB]e[39m ‘adb uninstall io.appium.uiautomator2.server’ command output: Success
[info] e[35m[ADB]e[39m io.appium.uiautomator2.server was successfully uninstalled[debug] e[35m[ADB]e[39m Running ‘C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 5200c479eaa935c3 shell ‘ls -t -1 /data/local/tmp/appium_cache 2>&1 || echo ERROR’’
[debug] e[35m[ADB]e[39m The count of applications in the cache: 7
[info] e[35m[ADB]e[39m The application at ‘C:\Users\xxxx\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-v4.3.0.apk’ is already cached to ‘/data/local/tmp/appium_cache/0cc1725a60a05dbb5d0d09256f2fc6ece7e3b10f.apk’
[debug] e[35m[ADB]e[39m Running ‘C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 5200c479eaa935c3 shell pm install -r /data/local/tmp/appium_cache/0cc1725a60a05dbb5d0d09256f2fc6ece7e3b10f.apk’[info] e[35m[ADB]e[39m The installation of ‘appium-uiautomator2-server-v4.3.0.apk’ took 5.361s
[debug] e[35m[ADB]e[39m Install command stdout: Success
[debug] e[35m[ADB]e[39m Uninstalling io.appium.uiautomator2.server.test
[debug] e[35m[ADB]e[39m Getting install status for io.appium.uiautomator2.server.test
[debug] e[35m[ADB]e[39m Running ‘C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 5200c479eaa935c3 shell dumpsys package io.appium.uiautomator2.server.test’
[debug] e[35m[ADB]e[39m ‘io.appium.uiautomator2.server.test’ is installed
[debug] e[35m[ADB]e[39m Running ‘C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 5200c479eaa935c3 shell am force-stop io.appium.uiautomator2.server.test’[debug] e[35m[ADB]e[39m Running ‘C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 5200c479eaa935c3 uninstall io.appium.uiautomator2.server.test’[debug] e[35m[ADB]e[39m ‘adb uninstall io.appium.uiautomator2.server.test’ command output: Success
[info] e[35m[ADB]e[39m io.appium.uiautomator2.server.test was successfully uninstalled
[debug] e[35m[ADB]e[39m Running ‘C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 5200c479eaa935c3 shell ‘ls -t -1 /data/local/tmp/appium_cache 2>&1 || echo ERROR’’
[debug] e[35m[ADB]e[39m The count of applications in the cache: 7
[info] e[35m[ADB]e[39m The application at ‘C:\Users\xxxx\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-debug-androidTest.apk’ is already cached to ‘/data/local/tmp/appium_cache/0beede6c27af5c71c23a0d9d1c82a7a0b18390e0.apk’
[debug] e[35m[ADB]e[39m Running ‘C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 5200c479eaa935c3 shell pm install -r /data/local/tmp/appium_cache/0beede6c27af5c71c23a0d9d1c82a7a0b18390e0.apk’[info] e[35m[ADB]e[39m The installation of ‘appium-uiautomator2-server-debug-androidTest.apk’ took 2.710s
[debug] e[35m[ADB]e[39m Install command stdout: Success
[debug] e[35m[UiAutomator2]e[39m Waiting up to 30000ms for services to be available
[debug] e[35m[ADB]e[39m Running ‘C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 5200c479eaa935c3 shell pm list instrumentation’[debug] e[35m[UiAutomator2]e[39m Instrumentation target ‘io.appium.uiautomator2.server.test/androidx.test.runner.AndroidJUnitRunner’ is available
[debug] e[35m[UiAutomator2]e[39m Forwarding UiAutomator2 Server port 6790 to 8200
[debug] e[35m[ADB]e[39m Forwarding system: 8200 to device: 6790
[debug] e[35m[ADB]e[39m Running ‘C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 5200c479eaa935c3 forward tcp:8200 tcp:6790’[debug] e[35m[ADB]e[39m Checking app cert for C:\Users\xxxx\Downloads\xxxx-prod-release.apk
[debug] e[35m[ADB]e[39m Starting ‘C:\Users\xxxx\AppData\Local\Android\Sdk\build-tools\30.0.0-rc2\apksigner.bat’ with args ‘[“verify”,"–print-certs",“C:\Users\xxxx\Downloads\xxxx-prod-release.apk”]’
[debug] e[35m[ADB]e[39m ‘C:\Users\xxxx\Downloads\xxxx-prod-release.apk’ is signed with non-default certificate
[debug] e[35m[ADB]e[39m C:\Users\xxxx\Downloads\xxxx-prod-release.apk’ is already zip-aligned. Doing nothing
[debug] e[35m[ADB]e[39m Signing ‘C:\Users\xxxx\Downloads\xxxx-prod-release.apk’ with default cert
[debug] e[35m[ADB]e[39m Starting ‘C:\Users\xxxx\AppData\Local\Android\Sdk\build-tools\30.0.0-rc2\apksigner.bat’ with args ‘[“sign”,"–key",“C:\Users\xxxx\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-adb\keys\testkey.pk8”,"–cert",“C:\Users\xxxx\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-adb\keys\testkey.x509.pem”,“C:\Users\xxxx\Downloads\xxxx-prod-release.apk”]’[debug] e[35m[ADB]e[39m Getting install status for com.matriksdata.mobileiq
[debug] e[35m[ADB]e[39m Running ‘C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 5200c479eaa935c3 shell dumpsys package com.matriksdata.mobileiq’
[debug] e[35m[ADB]e[39m ‘com.matriksdata.mobileiq’ is installed
[debug] e[35m[ADB]e[39m Getting package info for ‘com.matriksdata.mobileiq’
[debug] e[35m[ADB]e[39m Running ‘C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 5200c479eaa935c3 shell dumpsys package com.matriksdata.mobileiq’[info] e[35m[ADB]e[39m Cannot extract apk info using apkanalyzer. Falling back to aapt. Original error: Could not find ‘apkanalyzer.bat’ in [“C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\apkanalyzer.bat”,“C:\Users\xxxx\AppData\Local\Android\Sdk\emulator\apkanalyzer.bat”,“C:\Users\xxxx\AppData\Local\Android\Sdk\tools\apkanalyzer.bat”,“C:\Users\xxxx\AppData\Local\Android\Sdk\tools\bin\apkanalyzer.bat”,“C:\Users\xxxx\AppData\Local\Android\Sdk\build-tools\30.0.0-rc2\apkanalyzer.bat”,“C:\Users\xxxx\AppData\Local\Android\Sdk\build-tools\29.0.3\apkanalyzer.bat”]. Do you have Android Build Tools installed at ‘C:\Users\xxxx\AppData\Local\Android\Sdk’?
[debug] e[35m[ADB]e[39m The version name of the installed ‘com.matriksdata.mobileiq’ is greater or equal to the application version name (‘0.4.0’ >= ‘0.4.0’)
[debug] e[35m[ADB]e[39m There is no need to install/upgrade ‘C:\Users\xxxx\Downloads\xxxx-prod-release.apk’
[info] e[35m[AndroidDriver]e[39m Performing fast reset on ‘com.matriksdata.mobileiq’
[debug] e[35m[ADB]e[39m Getting install status for com.matriksdata.mobileiq
[debug] e[35m[ADB]e[39m Running ‘C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 5200c479eaa935c3 shell dumpsys package com.matriksdata.mobileiq’[debug] e[35m[ADB]e[39m ‘com.matriksdata.mobileiq’ is installed
[debug] e[35m[ADB]e[39m Running ‘C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 5200c479eaa935c3 shell am force-stop com.matriksdata.mobileiq’
[debug] e[35m[ADB]e[39m Running ‘C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 5200c479eaa935c3 shell pm clear com.matriksdata.mobileiq’[debug] e[35m[AndroidDriver]e[39m Performed fast reset on the installed ‘com.matriksdata.mobileiq’ application (stop and clear)
[debug] e[35m[UiAutomator2]e[39m Performing shallow cleanup of automation leftovers
[debug] e[35m[UiAutomator2]e[39m No obsolete sessions have been detected (Error: socket hang up)
[debug] e[35m[ADB]e[39m Running ‘C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 5200c479eaa935c3 shell am force-stop io.appium.uiautomator2.server.test’[info] e[35m[UiAutomator2]e[39m Starting UIAutomator2 server 4.3.0
[info] e[35m[UiAutomator2]e[39m Using UIAutomator2 server from ‘C:\Users\xxxx\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-v4.3.0.apk’ and test from ‘C:\Users\xxxx\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-debug-androidTest.apk’
[info] e[35m[UiAutomator2]e[39m Waiting up to 30000ms for UiAutomator2 to be online…
[debug] e[35m[ADB]e[39m Creating ADB subprocess with args: ["-P",5037,"-s",“5200c479eaa935c3”,“shell”,“am”,“instrument”,"-w",“io.appium.uiautomator2.server.test/androidx.test.runner.AndroidJUnitRunner”][debug] e[35m[Instrumentation]e[39m java.lang.SecurityException: Permission Denial: starting instrumentation ComponentInfo{io.appium.uiautomator2.server.test/androidx.test.runner.AndroidJUnitRunner} from pid=6042, uid=6042 not allowed because package io.appium.uiautomator2.server.test does not have a signature matching the target io.appium.uiautomator2.server
[debug] e[35m[Instrumentation]e[39m at android.os.Parcel.readException(Parcel.java:1967)
[debug] e[35m[Instrumentation]e[39m at android.os.Parcel.readException(Parcel.java:1913)
[debug] e[35m[Instrumentation]e[39m at android.app.IActivityManager$Stub$Proxy.startInstrumentation(IActivityManager.java:5586)
[debug] e[35m[Instrumentation]e[39m at com.android.commands.am.Instrument.run(Instrument.java:408)
[debug] e[35m[Instrumentation]e[39m at com.android.commands.am.Am.runInstrument(Am.java:232)
[debug] e[35m[Instrumentation]e[39m at com.android.commands.am.Am.onRun(Am.java:125)
[debug] e[35m[Instrumentation]e[39m at com.android.internal.os.BaseCommand.run(BaseCommand.java:54)
[debug] e[35m[Instrumentation]e[39m at com.android.commands.am.Am.main(Am.java:95)
[debug] e[35m[Instrumentation]e[39m at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)
[debug] e[35m[Instrumentation]e[39m at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:287)
[debug] e[35m[Instrumentation]e[39m INSTRUMENTATION_STATUS: id=ActivityManagerService
[debug] e[35m[Instrumentation]e[39m INSTRUMENTATION_STATUS: Error=Permission Denial: starting instrumentation ComponentInfo{io.appium.uiautomator2.server.test/androidx.test.runner.AndroidJUnitRunner} from pid=6042, uid=6042 not allowed because package io.appium.uiautomator2.server.test does not have a signature matching the target io.appium.uiautomator2.server
[debug] e[35m[Instrumentation]e[39m INSTRUMENTATION_STATUS_CODE: -1[debug] e[35m[Instrumentation]e[39m The process has exited with code 1[warn] e[35m[UiAutomator2]e[39m The instrumentation process has been unexpectedly terminated. Retrying UiAutomator2 startup (#1 of 1)
[debug] e[35m[UiAutomator2]e[39m Performing strict cleanup of automation leftovers
[debug] e[35m[UiAutomator2]e[39m No obsolete sessions have been detected (Error: socket hang up)
[debug] e[35m[ADB]e[39m Running ‘C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 5200c479eaa935c3 shell am force-stop io.appium.uiautomator2.server.test’
[debug] e[35m[ADB]e[39m Attempting to kill all uiautomator processes
[debug] e[35m[ADB]e[39m Getting IDs of all ‘uiautomator’ processes
[debug] e[35m[ADB]e[39m Running ‘C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 5200c479eaa935c3 shell pgrep ^uiautomator$’[info] e[35m[ADB]e[39m No ‘uiautomator’ process has been found[info] e[35m[UiAutomator2]e[39m Waiting up to 30000ms for UiAutomator2 to be online…
[debug] e[35m[ADB]e[39m Creating ADB subprocess with args: ["-P",5037,"-s",“5200c479eaa935c3”,“shell”,“am”,“instrument”,"-w",“io.appium.uiautomator2.server.test/androidx.test.runner.AndroidJUnitRunner”][debug] e[35m[Instrumentation]e[39m java.lang.SecurityException: Permission Denial: starting instrumentation ComponentInfo{io.appium.uiautomator2.server.test/androidx.test.runner.AndroidJUnitRunner} from pid=6064, uid=6064 not allowed because package io.appium.uiautomator2.server.test does not have a signature matching the target io.appium.uiautomator2.server
[debug] e[35m[Instrumentation]e[39m at android.os.Parcel.readException(Parcel.java:1967)
[debug] e[35m[Instrumentation]e[39m at android.os.Parcel.readException(Parcel.java:1913)
[debug] e[35m[Instrumentation]e[39m at android.app.IActivityManager$Stub$Proxy.startInstrumentation(IActivityManager.java:5586)
[debug] e[35m[Instrumentation]e[39m at com.android.commands.am.Instrument.run(Instrument.java:408)
[debug] e[35m[Instrumentation]e[39m at com.android.commands.am.Am.runInstrument(Am.java:232)
[debug] e[35m[Instrumentation]e[39m at com.android.commands.am.Am.onRun(Am.java:125)
[debug] e[35m[Instrumentation]e[39m at com.android.internal.os.BaseCommand.run(BaseCommand.java:54)
[debug] e[35m[Instrumentation]e[39m at com.android.commands.am.Am.main(Am.java:95)
[debug] e[35m[Instrumentation]e[39m at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)
[debug] e[35m[Instrumentation]e[39m at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:287)
[debug] e[35m[Instrumentation]e[39m INSTRUMENTATION_STATUS: id=ActivityManagerService
[debug] e[35m[Instrumentation]e[39m INSTRUMENTATION_STATUS: Error=Permission Denial: starting instrumentation ComponentInfo{io.appium.uiautomator2.server.test/androidx.test.runner.AndroidJUnitRunner} from pid=6064, uid=6064 not allowed because package io.appium.uiautomator2.server.test does not have a signature matching the target io.appium.uiautomator2.server
[debug] e[35m[Instrumentation]e[39m INSTRUMENTATION_STATUS_CODE: -1
[debug] e[35m[Instrumentation]e[39m The process has exited with code 1[error] e[35m[UiAutomator2]e[39m Error: The instrumentation process cannot be initialized. Make sure the application under test does not crash and investigate the logcat output.
[error] e[35m[UiAutomator2]e[39m at Object.wrappedLogger.errorAndThrow (C:\Users\xxxx\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-support\lib\logging.js:79:13)
[error] e[35m[UiAutomator2]e[39m at UiAutomator2Server.errorAndThrow [as startSession] (C:\Users\xxxx\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-uiautomator2-driver\lib\uiautomator2.js:227:13)
[debug] e[35m[UiAutomator2]e[39m Deleting UiAutomator2 session
[debug] e[35m[UiAutomator2]e[39m Deleting UiAutomator2 server session
[debug] e[35m[WD Proxy]e[39m Matched ‘/’ to command name ‘deleteSession’
[warn] e[35m[UiAutomator2]e[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] e[35m[ADB]e[39m Running ‘C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 5200c479eaa935c3 shell am force-stop com.matriksdata.mobileiq’[debug] e[35m[Logcat]e[39m Stopping logcat capture
[debug] e[35m[ADB]e[39m Removing forwarded port socket connection: 8200
[debug] e[35m[ADB]e[39m Running ‘C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 5200c479eaa935c3 forward --remove tcp:8200’
[debug] e[35m[BaseDriver]e[39m Event ‘newSessionStarted’ logged at 1585321410576 (18:03:30 GMT+0300 (Türkiye Standart Saati))
[debug] e[35m[MJSONWP]e[39m 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] e[35m[MJSONWP]e[39m at Object.wrappedLogger.errorAndThrow (C:\Users\xxxx\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-support\lib\logging.js:79:13)
[debug] e[35m[MJSONWP]e[39m at UiAutomator2Server.errorAndThrow [as startSession] (C:\Users\xxxx\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-uiautomator2-driver\lib\uiautomator2.js:227:13)
[info] e[35m[HTTP]e[39m e[37m<-- POST /wd/hub/session e[39me[31m500e[39m e[90m25138 ms - 274e[39m
[info] e[35m[HTTP]e[39m e[90me[39m
[info] e[35m[HTTP]e[39m e[37m–>e[39m e[37mDELETEe[39m e[37m/wd/hub/sessione[39m
[info] e[35m[HTTP]e[39m e[90m{}e[39m
[debug] e[35m[HTTP]e[39m No route found. Setting content type to ‘text/plain’
[info] e[35m[HTTP]e[39m e[37m<-- DELETE /wd/hub/session e[39me[33m404e[39m e[90m1 ms - 57e[39m
[info] e[35m[HTTP]e[39m e[90me[39m[info] e[35m[HTTP]e[39m e[37m–>e[39m e[37mPOSTe[39m e[37m/wd/hub/sessione[39m
[info] e[35m[HTTP]e[39m e[90m{“desiredCapabilities”:{“app”:“C:\Users\xxxx\Downloads\xxxx-prod-release.apk”,“deviceName”:“5200c479eaa935c3”,“platformName”:“Android”,“newCommandTimeout”:0,“connectHardwareKeyboard”:true}}e[39m
[debug] e[35m[MJSONWP]e[39m Calling AppiumDriver.createSession() with args: [{“app”:“C:\Users\xxxx\Downloads\xxxx-prod-release.apk”,“deviceName”:“5200c479eaa935c3”,“platformName”:“Android”,“newCommandTimeout”:0,“connectHardwareKeyboard”:true},null,null]
[debug] e[35m[BaseDriver]e[39m Event ‘newSessionRequested’ logged at 1585323417695 (18:36:57 GMT+0300 (Türkiye Standart Saati))
[warn] e[35m[Appium]e[39m
[warn] e[35m[Appium]e[39m ======================================================================
[warn] e[35m[Appium]e[39m DEPRECATION WARNING:
[warn] e[35m[Appium]e[39m
[warn] e[35m[Appium]e[39m The ‘automationName’ capability was not provided in the desired
[warn] e[35m[Appium]e[39m capabilities for this Android session
[warn] e[35m[Appium]e[39m
[warn] e[35m[Appium]e[39m Setting ‘automationName=UiAutomator2’ by default and using the
[warn] e[35m[Appium]e[39m UiAutomator2 Driver
[warn] e[35m[Appium]e[39m
[warn] e[35m[Appium]e[39m The next major version of Appium (2.x) will require the
[warn] e[35m[Appium]e[39m ‘automationName’ capability to be set for all sessions on all
[warn] e[35m[Appium]e[39m platforms
[warn] e[35m[Appium]e[39m
[warn] e[35m[Appium]e[39m In previous versions (Appium <= 1.13.x), the default was
[warn] e[35m[Appium]e[39m ‘automationName=UiAutomator1’
[warn] e[35m[Appium]e[39m
[warn] e[35m[Appium]e[39m If you wish to use that automation instead of UiAutomator2, please
[warn] e[35m[Appium]e[39m add ‘automationName=UiAutomator1’ to your desired capabilities
[warn] e[35m[Appium]e[39m
[warn] e[35m[Appium]e[39m For more information about drivers, please visit
[warn] e[35m[Appium]e[39m http://appium.io/docs/en/about-appium/intro/ and explore the
[warn] e[35m[Appium]e[39m ‘Drivers’ menu
[warn] e[35m[Appium]e[39m
[warn] e[35m[Appium]e[39m ======================================================================
[warn] e[35m[Appium]e[39m
[info] e[35m[Appium]e[39m Appium v1.15.1 creating new AndroidUiautomator2Driver (v1.37.2) session
[debug] e[35m[BaseDriver]e[39m Creating session with MJSONWP desired capabilities: {
[debug] e[35m[BaseDriver]e[39m “app”: “C:\Users\xxxx\Downloads\xxxx-prod-release.apk”,
[debug] e[35m[BaseDriver]e[39m “deviceName”: “5200c479eaa935c3”,
[debug] e[35m[BaseDriver]e[39m “platformName”: “Android”,
[debug] e[35m[BaseDriver]e[39m “newCommandTimeout”: 0,
[debug] e[35m[BaseDriver]e[39m “connectHardwareKeyboard”: true
[debug] e[35m[BaseDriver]e[39m }
[warn] e[35m[BaseDriver]e[39m The following capabilities were provided, but are not recognized by Appium:
[warn] e[35m[BaseDriver]e[39m connectHardwareKeyboard
[info] e[35m[BaseDriver]e[39m Session created with session id: e83a6e74-f1c6-44cc-9a67-5b82db9f1238
[info] e[35m[BaseDriver]e[39m Using local app ‘C:\Users\xxxx\Downloads\xxxx-prod-release.apk’
[debug] e[35m[UiAutomator2]e[39m Checking whether app is actually present[info] e[35m[ADB]e[39m Using ‘adb.exe’ from ‘C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\adb.exe’
[info] e[35m[AndroidDriver]e[39m Retrieving device list
[debug] e[35m[ADB]e[39m Trying to find a connected android device
[debug] e[35m[ADB]e[39m Getting connected devices…
[debug] e[35m[ADB]e[39m Connected devices: [{“udid”:“5200c479eaa935c3”,“state”:“device”}]
[info] e[35m[AndroidDriver]e[39m Using device: 5200c479eaa935c3
[info] e[35m[ADB]e[39m Using ‘adb.exe’ from ‘C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\adb.exe’
[debug] e[35m[ADB]e[39m Setting device id to 5200c479eaa935c3
[debug] e[35m[ADB]e[39m Running ‘C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 5200c479eaa935c3 shell getprop ro.build.version.sdk’[debug] e[35m[ADB]e[39m Current device property ‘ro.build.version.sdk’: 26
[debug] e[35m[ADB]e[39m Device API level: 26
[debug] e[35m[AndroidDriver]e[39m Parsing package and activity from app manifest
[info] e[35m[ADB]e[39m Using the alternative activity name detection method because of: Could not find ‘apkanalyzer.bat’ in [“C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\apkanalyzer.bat”,“C:\Users\xxxx\AppData\Local\Android\Sdk\emulator\apkanalyzer.bat”,“C:\Users\xxxx\AppData\Local\Android\Sdk\tools\apkanalyzer.bat”,“C:\Users\xxxx\AppData\Local\Android\Sdk\tools\bin\apkanalyzer.bat”,“C:\Users\xxxx\AppData\Local\Android\Sdk\build-tools\30.0.0-rc2\apkanalyzer.bat”,“C:\Users\xxxx\AppData\Local\Android\Sdk\build-tools\29.0.3\apkanalyzer.bat”]. Do you have Android Build Tools installed at ‘C:\Users\xxxx\AppData\Local\Android\Sdk’?
[info] e[35m[ADB]e[39m Using ‘aapt.exe’ from ‘C:\Users\xxxx\AppData\Local\Android\Sdk\build-tools\30.0.0-rc2\aapt.exe’
[info] e[35m[ADB]e[39m Extracting package and launch activity from manifest
[info] e[35m[ADB]e[39m Package name: ‘com.matriksdata.mobileiq’
[info] e[35m[ADB]e[39m Main activity name: ‘com.matriksdata.mobileiq.view.splash.SplashActivity’
[debug] e[35m[AndroidDriver]e[39m Parsed package and activity are: com.matriksdata.mobileiq/com.matriksdata.mobileiq.view.splash.SplashActivity
[debug] e[35m[ADB]e[39m Running ‘C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 5200c479eaa935c3 wait-for-device’
[debug] e[35m[ADB]e[39m Running ‘C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 5200c479eaa935c3 shell echo ping’[debug] e[35m[AndroidDriver]e[39m Pushing settings apk to device…
[debug] e[35m[ADB]e[39m Getting install status for io.appium.settings
[debug] e[35m[ADB]e[39m Running ‘C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 5200c479eaa935c3 shell dumpsys package io.appium.settings’
[debug] e[35m[ADB]e[39m ‘io.appium.settings’ is installed
[debug] e[35m[ADB]e[39m Getting package info for ‘io.appium.settings’
[debug] e[35m[ADB]e[39m Running ‘C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 5200c479eaa935c3 shell dumpsys package io.appium.settings’[info] e[35m[ADB]e[39m Cannot extract apk info using apkanalyzer. Falling back to aapt. Original error: Could not find ‘apkanalyzer.bat’ in [“C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\apkanalyzer.bat”,“C:\Users\xxxx\AppData\Local\Android\Sdk\emulator\apkanalyzer.bat”,“C:\Users\xxxx\AppData\Local\Android\Sdk\tools\apkanalyzer.bat”,“C:\Users\xxxx\AppData\Local\Android\Sdk\tools\bin\apkanalyzer.bat”,“C:\Users\xxxx\AppData\Local\Android\Sdk\build-tools\30.0.0-rc2\apkanalyzer.bat”,“C:\Users\xxxx\AppData\Local\Android\Sdk\build-tools\29.0.3\apkanalyzer.bat”]. Do you have Android Build Tools installed at ‘C:\Users\xxxx\AppData\Local\Android\Sdk’?
[debug] e[35m[ADB]e[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] e[35m[ADB]e[39m There is no need to install/upgrade ‘C:\Users\xxxx\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\io.appium.settings\apks\settings_apk-debug.apk’
[debug] e[35m[ADB]e[39m Getting IDs of all ‘io.appium.settings’ processes
[debug] e[35m[ADB]e[39m Running ‘C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 5200c479eaa935c3 shell ‘pgrep --help; echo $?’’[debug] e[35m[ADB]e[39m Running ‘C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 5200c479eaa935c3 shell pgrep ^appium\.settings$’
[debug] e[35m[AndroidDriver]e[39m io.appium.settings is already running. There is no need to reset its permissions.
[debug] e[35m[ADB]e[39m Running ‘C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 5200c479eaa935c3 shell appops set io.appium.settings android:mock_location allow’[debug] e[35m[Logcat]e[39m Starting logcat capture
[debug] e[35m[ADB]e[39m Getting install status for io.appium.uiautomator2.server
[debug] e[35m[ADB]e[39m Running ‘C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 5200c479eaa935c3 shell dumpsys package io.appium.uiautomator2.server’[debug] e[35m[ADB]e[39m ‘io.appium.uiautomator2.server’ is installed
[debug] e[35m[ADB]e[39m Getting package info for ‘io.appium.uiautomator2.server’
[debug] e[35m[ADB]e[39m Running ‘C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 5200c479eaa935c3 shell dumpsys package io.appium.uiautomator2.server’
[info] e[35m[ADB]e[39m Cannot extract apk info using apkanalyzer. Falling back to aapt. Original error: Could not find ‘apkanalyzer.bat’ in [“C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\apkanalyzer.bat”,“C:\Users\xxxx\AppData\Local\Android\Sdk\emulator\apkanalyzer.bat”,“C:\Users\xxxx\AppData\Local\Android\Sdk\tools\apkanalyzer.bat”,“C:\Users\xxxx\AppData\Local\Android\Sdk\tools\bin\apkanalyzer.bat”,“C:\Users\xxxx\AppData\Local\Android\Sdk\build-tools\30.0.0-rc2\apkanalyzer.bat”,“C:\Users\xxxx\AppData\Local\Android\Sdk\build-tools\29.0.3\apkanalyzer.bat”]. Do you have Android Build Tools installed at ‘C:\Users\xxxx\AppData\Local\Android\Sdk’?[debug] e[35m[ADB]e[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] e[35m[UiAutomator2]e[39m io.appium.uiautomator2.server installation state: sameVersionInstalled
[debug] e[35m[ADB]e[39m Checking app cert for C:\Users\xxxx\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-v4.3.0.apk
[info] e[35m[ADB]e[39m Using ‘apksigner.bat’ from ‘C:\Users\xxxx\AppData\Local\Android\Sdk\build-tools\30.0.0-rc2\apksigner.bat’
[debug] e[35m[ADB]e[39m Starting ‘C:\Users\xxxx\AppData\Local\Android\Sdk\build-tools\30.0.0-rc2\apksigner.bat’ with args ‘[“verify”,"–print-certs",“C:\Users\xxxx\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-v4.3.0.apk”]’
[debug] e[35m[ADB]e[39m ‘C:\Users\xxxx\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-v4.3.0.apk’ is signed with non-default certificate
[info] e[35m[ADB]e[39m Using ‘zipalign.exe’ from ‘C:\Users\xxxx\AppData\Local\Android\Sdk\build-tools\30.0.0-rc2\zipalign.exe’
[debug] e[35m[ADB]e[39m C:\Users\xxxx\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-v4.3.0.apk’ is already zip-aligned. Doing nothing
[debug] e[35m[ADB]e[39m Signing ‘C:\Users\xxxx\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-v4.3.0.apk’ with default cert
[debug] e[35m[ADB]e[39m Starting ‘C:\Users\xxxx\AppData\Local\Android\Sdk\build-tools\30.0.0-rc2\apksigner.bat’ with args ‘[“sign”,"–key",“C:\Users\xxxx\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-adb\keys\testkey.pk8”,"–cert",“C:\Users\xxxx\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-adb\keys\testkey.x509.pem”,“C:\Users\xxxx\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-v4.3.0.apk”]’
[debug] e[35m[ADB]e[39m Getting install status for io.appium.uiautomator2.server.test
[debug] e[35m[ADB]e[39m Running ‘C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 5200c479eaa935c3 shell dumpsys package io.appium.uiautomator2.server.test’[debug] e[35m[ADB]e[39m ‘io.appium.uiautomator2.server.test’ is installed
[debug] e[35m[ADB]e[39m Checking app cert for C:\Users\xxxx\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-debug-androidTest.apk
[debug] e[35m[ADB]e[39m Starting ‘C:\Users\xxxx\AppData\Local\Android\Sdk\build-tools\30.0.0-rc2\apksigner.bat’ with args ‘[“verify”,"–print-certs",“C:\Users\xxxx\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-debug-androidTest.apk”]’
[debug] e[35m[ADB]e[39m ‘C:\Users\xxxx\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-debug-androidTest.apk’ is signed with non-default certificate
[debug] e[35m[ADB]e[39m C:\Users\xxxx\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-debug-androidTest.apk’ is already zip-aligned. Doing nothing
[debug] e[35m[ADB]e[39m Signing ‘C:\Users\xxxx\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-debug-androidTest.apk’ with default cert
[debug] e[35m[ADB]e[39m Starting ‘C:\Users\xxxx\AppData\Local\Android\Sdk\build-tools\30.0.0-rc2\apksigner.bat’ with args ‘[“sign”,"–key",“C:\Users\xxxx\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-adb\keys\testkey.pk8”,"–cert",“C:\Users\xxxx\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-adb\keys\testkey.x509.pem”,“C:\Users\xxxx\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-debug-androidTest.apk”]’[info] e[35m[UiAutomator2]e[39m Server packages are going to be (re)installed
[info] e[35m[UiAutomator2]e[39m Full packages reinstall is going to be performed
[debug] e[35m[ADB]e[39m Uninstalling io.appium.uiautomator2.server
[debug] e[35m[ADB]e[39m Getting install status for io.appium.uiautomator2.server
[debug] e[35m[ADB]e[39m Running ‘C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 5200c479eaa935c3 shell dumpsys package io.appium.uiautomator2.server’
[debug] e[35m[ADB]e[39m ‘io.appium.uiautomator2.server’ is installed
[debug] e[35m[ADB]e[39m Running ‘C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 5200c479eaa935c3 shell am force-stop io.appium.uiautomator2.server’[debug] e[35m[ADB]e[39m Running ‘C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 5200c479eaa935c3 uninstall io.appium.uiautomator2.server’[debug] e[35m[ADB]e[39m ‘adb uninstall io.appium.uiautomator2.server’ command output: Success
[info] e[35m[ADB]e[39m io.appium.uiautomator2.server was successfully uninstalled
[debug] e[35m[ADB]e[39m Running ‘C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 5200c479eaa935c3 shell ‘ls -t -1 /data/local/tmp/appium_cache 2>&1 || echo ERROR’’[debug] e[35m[ADB]e[39m The count of applications in the cache: 7
[info] e[35m[ADB]e[39m The application at ‘C:\Users\xxxx\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-v4.3.0.apk’ is already cached to ‘/data/local/tmp/appium_cache/0cc1725a60a05dbb5d0d09256f2fc6ece7e3b10f.apk’
[debug] e[35m[ADB]e[39m Running ‘C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 5200c479eaa935c3 shell pm install -r /data/local/tmp/appium_cache/0cc1725a60a05dbb5d0d09256f2fc6ece7e3b10f.apk’[info] e[35m[ADB]e[39m The installation of ‘appium-uiautomator2-server-v4.3.0.apk’ took 6.987s
[debug] e[35m[ADB]e[39m Install command stdout: Success
[debug] e[35m[ADB]e[39m Uninstalling io.appium.uiautomator2.server.test
[debug] e[35m[ADB]e[39m Getting install status for io.appium.uiautomator2.server.test
[debug] e[35m[ADB]e[39m Running ‘C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 5200c479eaa935c3 shell dumpsys package io.appium.uiautomator2.server.test’[debug] e[35m[ADB]e[39m ‘io.appium.uiautomator2.server.test’ is installed
[debug] e[35m[ADB]e[39m Running ‘C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 5200c479eaa935c3 shell am force-stop io.appium.uiautomator2.server.test’
[debug] e[35m[ADB]e[39m Running ‘C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 5200c479eaa935c3 uninstall io.appium.uiautomator2.server.test’[debug] e[35m[ADB]e[39m ‘adb uninstall io.appium.uiautomator2.server.test’ command output: Success
[info] e[35m[ADB]e[39m io.appium.uiautomator2.server.test was successfully uninstalled
[debug] e[35m[ADB]e[39m Running ‘C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 5200c479eaa935c3 shell ‘ls -t -1 /data/local/tmp/appium_cache 2>&1 || echo ERROR’’[debug] e[35m[ADB]e[39m The count of applications in the cache: 7
[info] e[35m[ADB]e[39m The application at ‘C:\Users\xxxx\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-debug-androidTest.apk’ is already cached to ‘/data/local/tmp/appium_cache/0beede6c27af5c71c23a0d9d1c82a7a0b18390e0.apk’
[debug] e[35m[ADB]e[39m Running ‘C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 5200c479eaa935c3 shell pm install -r /data/local/tmp/appium_cache/0beede6c27af5c71c23a0d9d1c82a7a0b18390e0.apk’[info] e[35m[ADB]e[39m The installation of ‘appium-uiautomator2-server-debug-androidTest.apk’ took 2.913s
[debug] e[35m[ADB]e[39m Install command stdout: Success
[debug] e[35m[UiAutomator2]e[39m Waiting up to 30000ms for services to be available
[debug] e[35m[ADB]e[39m Running ‘C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 5200c479eaa935c3 shell pm list instrumentation’[debug] e[35m[UiAutomator2]e[39m Instrumentation target ‘io.appium.uiautomator2.server.test/androidx.test.runner.AndroidJUnitRunner’ is available
[debug] e[35m[UiAutomator2]e[39m Forwarding UiAutomator2 Server port 6790 to 8200
[debug] e[35m[ADB]e[39m Forwarding system: 8200 to device: 6790
[debug] e[35m[ADB]e[39m Running ‘C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 5200c479eaa935c3 forward tcp:8200 tcp:6790’
[debug] e[35m[ADB]e[39m Checking app cert for C:\Users\xxxx\Downloads\xxxx-prod-release.apk
[debug] e[35m[ADB]e[39m Starting ‘C:\Users\xxxx\AppData\Local\Android\Sdk\build-tools\30.0.0-rc2\apksigner.bat’ with args ‘[“verify”,"–print-certs",“C:\Users\xxxx\Downloads\xxxx-prod-release.apk”]’
[debug] e[35m[ADB]e[39m ‘C:\Users\xxxx\Downloads\xxxx-prod-release.apk’ is signed with non-default certificate[debug] e[35m[ADB]e[39m C:\Users\xxxx\Downloads\xxxx-prod-release.apk’ is already zip-aligned. Doing nothing
[debug] e[35m[ADB]e[39m Signing ‘C:\Users\xxxx\Downloads\xxxx-prod-release.apk’ with default cert
[debug] e[35m[ADB]e[39m Starting ‘C:\Users\xxxx\AppData\Local\Android\Sdk\build-tools\30.0.0-rc2\apksigner.bat’ with args ‘[“sign”,"–key",“C:\Users\xxxx\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-adb\keys\testkey.pk8”,"–cert",“C:\Users\xxxx\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-adb\keys\testkey.x509.pem”,“C:\Users\xxxx\Downloads\xxxx-prod-release.apk”]’
[debug] e[35m[ADB]e[39m Getting install status for com.matriksdata.mobileiq
[debug] e[35m[ADB]e[39m Running ‘C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 5200c479eaa935c3 shell dumpsys package com.matriksdata.mobileiq’
[debug] e[35m[ADB]e[39m ‘com.matriksdata.mobileiq’ is installed
[debug] e[35m[ADB]e[39m Getting package info for ‘com.matriksdata.mobileiq’
[debug] e[35m[ADB]e[39m Running ‘C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 5200c479eaa935c3 shell dumpsys package com.matriksdata.mobileiq’[info] e[35m[ADB]e[39m Cannot extract apk info using apkanalyzer. Falling back to aapt. Original error: Could not find ‘apkanalyzer.bat’ in [“C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\apkanalyzer.bat”,“C:\Users\xxxx\AppData\Local\Android\Sdk\emulator\apkanalyzer.bat”,“C:\Users\xxxx\AppData\Local\Android\Sdk\tools\apkanalyzer.bat”,“C:\Users\xxxx\AppData\Local\Android\Sdk\tools\bin\apkanalyzer.bat”,“C:\Users\xxxx\AppData\Local\Android\Sdk\build-tools\30.0.0-rc2\apkanalyzer.bat”,“C:\Users\xxxx\AppData\Local\Android\Sdk\build-tools\29.0.3\apkanalyzer.bat”]. Do you have Android Build Tools installed at ‘C:\Users\xxxx\AppData\Local\Android\Sdk’?
[debug] e[35m[ADB]e[39m The version name of the installed ‘com.matriksdata.mobileiq’ is greater or equal to the application version name (‘0.4.0’ >= ‘0.4.0’)
[debug] e[35m[ADB]e[39m There is no need to install/upgrade ‘C:\Users\xxxx\Downloads\xxxx-prod-release.apk’
[info] e[35m[AndroidDriver]e[39m Performing fast reset on ‘com.matriksdata.mobileiq’
[debug] e[35m[ADB]e[39m Getting install status for com.matriksdata.mobileiq
[debug] e[35m[ADB]e[39m Running ‘C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 5200c479eaa935c3 shell dumpsys package com.matriksdata.mobileiq’[debug] e[35m[ADB]e[39m ‘com.matriksdata.mobileiq’ is installed
[debug] e[35m[ADB]e[39m Running ‘C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 5200c479eaa935c3 shell am force-stop com.matriksdata.mobileiq’
[debug] e[35m[ADB]e[39m Running ‘C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 5200c479eaa935c3 shell pm clear com.matriksdata.mobileiq’[debug] e[35m[AndroidDriver]e[39m Performed fast reset on the installed ‘com.matriksdata.mobileiq’ application (stop and clear)
[debug] e[35m[UiAutomator2]e[39m Performing shallow cleanup of automation leftovers[info] e[35m[UiAutomator2]e[39m Starting UIAutomator2 server 4.3.0
[info] e[35m[UiAutomator2]e[39m Using UIAutomator2 server from ‘C:\Users\xxxx\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-v4.3.0.apk’ and test from ‘C:\Users\xxxx\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-debug-androidTest.apk’
[info] e[35m[UiAutomator2]e[39m Waiting up to 30000ms for UiAutomator2 to be online…
[debug] e[35m[ADB]e[39m Creating ADB subprocess with args: ["-P",5037,"-s",“5200c479eaa935c3”,“shell”,“am”,“instrument”,"-w",“io.appium.uiautomator2.server.test/androidx.test.runner.AndroidJUnitRunner”][debug] e[35m[Instrumentation]e[39m java.lang.SecurityException: Permission Denial: starting instrumentation ComponentInfo{io.appium.uiautomator2.server.test/androidx.test.runner.AndroidJUnitRunner} from pid=8496, uid=8496 not allowed because package io.appium.uiautomator2.server.test does not have a signature matching the target io.appium.uiautomator2.server
[debug] e[35m[Instrumentation]e[39m at android.os.Parcel.readException(Parcel.java:1967)
[debug] e[35m[Instrumentation]e[39m at android.os.Parcel.readException(Parcel.java:1913)
[debug] e[35m[Instrumentation]e[39m at android.app.IActivityManager$Stub$Proxy.startInstrumentation(IActivityManager.java:5586)
[debug] e[35m[Instrumentation]e[39m at com.android.commands.am.Instrument.run(Instrument.java:408)
[debug] e[35m[Instrumentation]e[39m at com.android.commands.am.Am.runInstrument(Am.java:232)
[debug] e[35m[Instrumentation]e[39m at com.android.commands.am.Am.onRun(Am.java:125)
[debug] e[35m[Instrumentation]e[39m at com.android.internal.os.BaseCommand.run(BaseCommand.java:54)
[debug] e[35m[Instrumentation]e[39m at com.android.commands.am.Am.main(Am.java:95)
[debug] e[35m[Instrumentation]e[39m at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)
[debug] e[35m[Instrumentation]e[39m at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:287)
[debug] e[35m[Instrumentation]e[39m INSTRUMENTATION_STATUS: id=ActivityManagerService
[debug] e[35m[Instrumentation]e[39m INSTRUMENTATION_STATUS: Error=Permission Denial: starting instrumentation ComponentInfo{io.appium.uiautomator2.server.test/androidx.test.runner.AndroidJUnitRunner} from pid=8496, uid=8496 not allowed because package io.appium.uiautomator2.server.test does not have a signature matching the target io.appium.uiautomator2.server
[debug] e[35m[Instrumentation]e[39m INSTRUMENTATION_STATUS_CODE: -1
[debug] e[35m[Instrumentation]e[39m The process has exited with code 1[warn] e[35m[UiAutomator2]e[39m The instrumentation process has been unexpectedly terminated. Retrying UiAutomator2 startup (#1 of 1)
[debug] e[35m[UiAutomator2]e[39m Performing strict cleanup of automation leftovers
[debug] e[35m[UiAutomator2]e[39m No obsolete sessions have been detected (Error: socket hang up)
[debug] e[35m[ADB]e[39m Running ‘C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 5200c479eaa935c3 shell am force-stop io.appium.uiautomator2.server.test’[debug] e[35m[ADB]e[39m Attempting to kill all uiautomator processes
[debug] e[35m[ADB]e[39m Getting IDs of all ‘uiautomator’ processes
[debug] e[35m[ADB]e[39m Running ‘C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 5200c479eaa935c3 shell pgrep ^uiautomator$’
[info] e[35m[ADB]e[39m No ‘uiautomator’ process has been found[info] e[35m[UiAutomator2]e[39m Waiting up to 30000ms for UiAutomator2 to be online…
[debug] e[35m[ADB]e[39m Creating ADB subprocess with args: ["-P",5037,"-s",“5200c479eaa935c3”,“shell”,“am”,“instrument”,"-w",“io.appium.uiautomator2.server.test/androidx.test.runner.AndroidJUnitRunner”][debug] e[35m[Instrumentation]e[39m java.lang.SecurityException: Permission Denial: starting instrumentation ComponentInfo{io.appium.uiautomator2.server.test/androidx.test.runner.AndroidJUnitRunner} from pid=8524, uid=8524 not allowed because package io.appium.uiautomator2.server.test does not have a signature matching the target io.appium.uiautomator2.server
[debug] e[35m[Instrumentation]e[39m at android.os.Parcel.readException(Parcel.java:1967)
[debug] e[35m[Instrumentation]e[39m INSTRUMENTATION_STATUS: id=ActivityManagerService
[debug] e[35m[Instrumentation]e[39m INSTRUMENTATION_STATUS: Error=Permission Denial: starting instrumentation ComponentInfo{io.appium.uiautomator2.server.test/androidx.test.runner.AndroidJUnitRunner} from pid=8524, uid=8524 not allowed because package io.appium.uiautomator2.server.test does not have a signature matching the target io.appium.uiautomator2.server
[debug] e[35m[Instrumentation]e[39m INSTRUMENTATION_STATUS_CODE: -1
[debug] e[35m[Instrumentation]e[39m at android.os.Parcel.readException(Parcel.java:1913)
[debug] e[35m[Instrumentation]e[39m at android.app.IActivityManager$Stub$Proxy.startInstrumentation(IActivityManager.java:5586)
[debug] e[35m[Instrumentation]e[39m at com.android.commands.am.Instrument.run(Instrument.java:408)
[debug] e[35m[Instrumentation]e[39m at com.android.commands.am.Am.runInstrument(Am.java:232)
[debug] e[35m[Instrumentation]e[39m at com.android.commands.am.Am.onRun(Am.java:125)
[debug] e[35m[Instrumentation]e[39m at com.android.internal.os.BaseCommand.run(BaseCommand.java:54)
[debug] e[35m[Instrumentation]e[39m at com.android.commands.am.Am.main(Am.java:95)
[debug] e[35m[Instrumentation]e[39m at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)
[debug] e[35m[Instrumentation]e[39m at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:287)[debug] e[35m[Instrumentation]e[39m The process has exited with code 1
[error] e[35m[UiAutomator2]e[39m Error: The instrumentation process cannot be initialized. Make sure the application under test does not crash and investigate the logcat output.
[error] e[35m[UiAutomator2]e[39m at Object.wrappedLogger.errorAndThrow (C:\Users\xxxx\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-support\lib\logging.js:79:13)
[error] e[35m[UiAutomator2]e[39m at UiAutomator2Server.errorAndThrow [as startSession] (C:\Users\xxxx\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-uiautomator2-driver\lib\uiautomator2.js:227:13)
[debug] e[35m[UiAutomator2]e[39m Deleting UiAutomator2 session
[debug] e[35m[UiAutomator2]e[39m Deleting UiAutomator2 server session
[debug] e[35m[WD Proxy]e[39m Matched ‘/’ to command name ‘deleteSession’
[warn] e[35m[UiAutomator2]e[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] e[35m[ADB]e[39m Running ‘C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 5200c479eaa935c3 shell am force-stop com.matriksdata.mobileiq’[debug] e[35m[Logcat]e[39m Stopping logcat capture
[debug] e[35m[ADB]e[39m Removing forwarded port socket connection: 8200
[debug] e[35m[ADB]e[39m Running ‘C:\Users\xxxx\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 5200c479eaa935c3 forward --remove tcp:8200’
[debug] e[35m[BaseDriver]e[39m Event ‘newSessionStarted’ logged at 1585323440676 (18:37:20 GMT+0300 (Türkiye Standart Saati))
[debug] e[35m[MJSONWP]e[39m 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] e[35m[MJSONWP]e[39m at Object.wrappedLogger.errorAndThrow (C:\Users\xxxx\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-support\lib\logging.js:79:13)
[debug] e[35m[MJSONWP]e[39m at UiAutomator2Server.errorAndThrow [as startSession] (C:\Users\xxxx\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-uiautomator2-driver\lib\uiautomator2.js:227:13)
[info] e[35m[HTTP]e[39m e[37m<-- POST /wd/hub/session e[39me[31m500e[39m e[90m22983 ms - 274e[39m
[info] e[35m[HTTP]e[39m e[90me[39m
[info] e[35m[HTTP]e[39m e[37m–>e[39m e[37mDELETEe[39m e[37m/wd/hub/sessione[39m
[info] e[35m[HTTP]e[39m e[90m{}e[39m
[debug] e[35m[HTTP]e[39m No route found. Setting content type to ‘text/plain’
[info] e[35m[HTTP]e[39m e[37m<-- DELETE /wd/hub/session e[39me[33m404e[39m e[90m1 ms - 57e[39m
[info] e[35m[HTTP]e[39m e[90me[39m

This is the problem,

to resolve, run these commands:

adb uninstall io.appium.uiautomator2.server
adb uninstall io.appium.uiautomator2.server.test

Solution posted by Oldstone here:

Alternate option, update to latest Appium version v1.17.0 and give it a try.