Error while installing android apk Using Appum 1.10.0


#1

PLease help me

public static final String apk ="C:\APK\xxx.apk";

String className = this .getClass().getSimpleName();

static AppiumDriver<WebElement> driver = null ;

@Test

public void configure() throws MalformedURLException, InterruptedException

{

System. err .println("Finished test - class name " + className);

try {

System. out .println("App installation started :");

File app = new File( apk );

DesiredCapabilities capabilities = new DesiredCapabilities();

capabilities.setCapability(CapabilityType. BROWSER_NAME , "");

Thread. sleep (3000);

capabilities.setCapability("deviceName","0915f9d3592c1904");

capabilities.setCapability("platformVersion", "7.0");

capabilities.setCapability("platformName", "Android");

capabilities.setCapability("app", app.getAbsolutePath());

Thread. sleep (5000);

capabilities.setCapability("app-package", "com.company.mobile.projX");

capabilities.setCapability("app-activity", "md5cab66dbf08211acdc39d74bdadc3428b.MainActivity"); //md5cab66dbf08211acdc39d74bdadc3428b.MainActivity

driver = new AppiumDriver<WebElement>( new URL("http://127.0.0.1:4723/wd/hub"), capabilities) ;

capabilities.setCapability("autoGrantPermissions", true );

capabilities.setCapability("appWaitActivity","md5cab66dbf08211acdc39d74bdadc3428b.MainActivity");

System. out .println("Installing the native app in device…");

}

catch (Exception e)

{

throw new RuntimeException();

}

}

}

Error: java.lang.RuntimeException

Appium:-

The server is running

[Appium] Welcome to Appium v1.10.0

[Appium] Appium REST http interface listener started on 0.0.0.0:4723

[HTTP] --> POST /wd/hub/session

[HTTP] {"desiredCapabilities":{"app":"C:\apk\xxx.apk","platformVersion":"7.0","app-activity":"md5cab66dbf08211acdc39d74bdadc3428b.MainActivity","app-package":"com.company.mobile.projX","browserName":"","platformName":"Android","deviceName":"0915f9d3592c1904"},"capabilities":{"firstMatch":[{"appium:app":" C:\apk\xxx.apk ", "app-activity":"md5cab66dbf08211acdc39d74bdadc3428b.MainActivity","app-package":" com.company.mobile.projX”,"browserName":"","appium:deviceName":"0915f9d3592c1904","platformName":"android","appium:platformVersion":"7.0"}]}}

[W3C] Calling AppiumDriver.createSession() with args: [{"app":"C:\ APK\xxx.apk","platformVersion":"7.0","app-activity":"md5cab66dbf08211acdc39d74bdadc3428b.MainActivity","app-package":"com.company.mobile.projX","browserName":"","platformName":"Android","deviceName":"0915f9d3592c1904"},null,{"firstMatch":[{"appium:app":"C:\APK\xxx.apk","app-activity":"md5cab66dbf08211acdc39d74bdadc3428b.MainActivity","app-package":"com.company.mobile.projX","browserName":"","appium:deviceName":"0915f9d3592c1904","platformName":"android","appium:platformVersion":"7.0"}]}]

[BaseDriver] Event ‘newSessionRequested’ logged at 1553080385647 (16:43:05 GMT+0530 (India Standard Time))

[BaseDriver] The capabilities ["app-activity","app-package"] are not standard capabilities and should have an extension prefix

[Appium] Consider setting ‘automationName’ capability to ‘UiAutomator2’ on Android >= 6, since UIAutomator framework is not maintained anymore by the OS vendor.

[Appium] Creating new AndroidDriver (v4.8.0) session

[Appium] Capabilities:

[Appium] app-activity: md5cab66dbf08211acdc39d74bdadc3428b.MainActivity

[Appium] app-package: com.company.mobile.projX

[Appium] browserName:

[Appium] platformName: android

[Appium] app: C:\MobileAutomation\APK\com.company.mobile.projX-signed-zipaligned.apk

[Appium] deviceName: 0915f9d3592c1904

[Appium] platformVersion: 7.0

[BaseDriver] W3C capabilities {"alwaysMatch":{"appium:app… and MJSONWP desired capabilities {"app":"C:\MobileAutomatio… were provided

[BaseDriver] Creating session with W3C capabilities: {"alwaysMatch":{"appium:app…

[BaseDriver] The following capabilities were provided, but are not recognized by appium: app-activity, app-package.

[BaseDriver] Session created with session id: 65dc67f5-fdc7-408a-bc94-6b41a8a699fd

[AndroidDriver] Java version is: 1.8.0_191

[AndroidDriver] Retrieving device list

[ADB] Trying to find a connected android device

[ADB] Getting connected devices…

[ADB] 1 device(s) connected

[AndroidDriver] Looking for a device with Android ‘7.0’

[ADB] Setting device id to 0915f9d3592c1904

[ADB] Getting device platform version

[ADB] Running ‘C:\Users\KotturJ\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 0915f9d3592c1904 shell getprop ro.build.version.release’

[ADB] Current device property ‘ro.build.version.release’: 7.0

[AndroidDriver] Using device: 0915f9d3592c1904

[ADB] Setting device id to 0915f9d3592c1904

[ADB] Running ‘C:\Users\KotturJ\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 0915f9d3592c1904 shell getprop ro.build.version.sdk’

[ADB] Current device property ‘ro.build.version.sdk’: 24

[ADB] Device API level: 24

[AndroidDriver] Consider setting ‘automationName’ capability to ‘uiautomator2’ on Android >= 6, since UIAutomator framework is not maintained anymore by the OS vendor.

[BaseDriver] Using local app ‘C:\APK\xxx.apk’

[AndroidDriver] Checking whether app is actually present

[AndroidDriver] Starting Android session

[ADB] Running ‘C:\Users\KotturJ\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 0915f9d3592c1904 wait-for-device’

[ADB] Running ‘C:\Users\KotturJ\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 0915f9d3592c1904 shell echo ping’

[AndroidDriver] Pushing settings apk to device…

[ADB] Getting install status for io.appium.settings

[ADB] Running ‘C:\Users\KotturJ\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 0915f9d3592c1904 shell dumpsys package io.appium.settings’

[ADB] ‘io.appium.settings’ is installed

[ADB] Getting package info for ‘io.appium.settings’

[ADB] Running ‘C:\Users\KotturJ\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 0915f9d3592c1904 shell dumpsys package io.appium.settings’

[ADB] The version name of the installed ‘io.appium.settings’ is greater or equal to the application version name (‘2.11.0’ >= ‘2.11.0’)

[ADB] There is no need to install/upgrade ‘C:\Users\KotturJ\AppData\Local\Programs\Appium\resources\app\node_modules\io.appium.settings\apks\settings_apk-debug.apk’

[ADB] Running ‘C:\Users\KotturJ\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 0915f9d3592c1904 shell ps’

[ADB] Device API level: 24

[ADB] Device API level: 24

[ADB] Running ‘C:\Users\KotturJ\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 0915f9d3592c1904 shell am start -W -n io.appium.settings/.Settings -a android.intent.action.MAIN -c android.intent.category.LAUNCHER -f 0x10200000’

[ADB] Device API level: 24

[ADB] Running ‘C:\Users\KotturJ\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 0915f9d3592c1904 shell appops set io.appium.settings android:mock_location allow’

[Logcat] Starting logcat capture

[ADB] Getting device platform version

[ADB] Running ‘C:\Users\KotturJ\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 0915f9d3592c1904 shell getprop ro.build.version.release’

[ADB] Current device property ‘ro.build.version.release’: 7.0

[ADB] Running ‘C:\Users\KotturJ\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 0915f9d3592c1904 shell wm size’

[ADB] Running ‘C:\Users\KotturJ\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 0915f9d3592c1904 shell getprop ro.product.model’

[ADB] Current device property ‘ro.product.model’: SM-G920F

[ADB] Running ‘C:\Users\KotturJ\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 0915f9d3592c1904 shell getprop ro.product.manufacturer’

[ADB] Current device property ‘ro.product.manufacturer’: samsung

[AndroidDriver] Parsing package and activity from app manifest

[ADB] Using the alternative activity name detection method because of: Could not find apkanalyzer.bat in C:\Users\KotturJ\AppData\Local\Android\Sdk\platform-tools\apkanalyzer.bat,C:\Users\KotturJ\AppData\Local\Android\Sdk\emulator\apkanalyzer.bat,C:\Users\KotturJ\AppData\Local\Android\Sdk\tools\apkanalyzer.bat,C:\Users\KotturJ\AppData\Local\Android\Sdk\tools\bin\apkanalyzer.bat,C:\Users\KotturJ\AppData\Local\Android\Sdk\build-tools\28.0.3\apkanalyzer.bat. Do you have the Android SDK installed at ‘C:\Users\KotturJ\AppData\Local\Android\Sdk’?

[ADB] Extracting package and launch activity from manifest

[ADB] Package name: ‘com.company.mobile.projX’

[ADB] Main activity name: ‘md5cab66dbf08211acdc39d74bdadc3428b.SplashScreen’

[AndroidDriver] Parsed package and activity are: com.company.mobile.projX/md5cab66dbf08211acdc39d74bdadc3428b.SplashScreen

[ADB] Getting install status for com.company.mobile.projX

[ADB] Running ‘C:\Users\KotturJ\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 0915f9d3592c1904 shell dumpsys package com.company.mobile.projX’

[ADB] ‘com.company.mobile.projX’ is not installed

[ADB] Getting install status for com.company.mobile.projX

[ADB] Running ‘C:\Users\KotturJ\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 0915f9d3592c1904 shell dumpsys package com.company.mobile.projX’

[ADB] ‘com.company.mobile.projX’ is not installed

[ADB] App ‘C:\MobileAutomation\APK\com.company.mobile.projX-signed-zipaligned.apk’ is not installed

[ADB] Installing ‘C:\MobileAutomation\APK\com.company.mobile.projX-signed-zipaligned.apk’

[ADB] Device API level: 24

[ADB] Running ‘C:\Users\KotturJ\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 0915f9d3592c1904 install C:\MobileAutomation\APK\com.company.mobile.projX-signed-zipaligned.apk’

[ADB] Install command stdout: Success

[ADB] Running ‘C:\Users\KotturJ\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 0915f9d3592c1904 shell rm -rf /data/local/tmp/strings.json’

[AndroidDriver] Extracting strings from apk

[AndroidDriver] C:\MobileAutomation\APK\com.company.mobile.projX-signed-zipaligned.apk

[AndroidDriver] undefined

[AndroidDriver] C:\Users\KotturJ\AppData\Local\Temp\com.company.mobile.projX

[ADB] Extracting strings from for language: default

[ADB] Successfully extracted 202 strings from ‘C:\MobileAutomation\APK\com.company.mobile.projX-signed-zipaligned.apk’ resources for ‘(default)’ configuration

[ADB] Running ‘C:\Users\KotturJ\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 0915f9d3592c1904 push C:\Users\KotturJ\AppData\Local\Temp\com.company.mobile.projX\strings.json /data/local/tmp’

[AndroidBootstrap] Watching for bootstrap disconnect

[ADB] Forwarding system: 4724 to device: 4724

[ADB] Running ‘C:\Users\KotturJ\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 0915f9d3592c1904 forward tcp:4724 tcp:4724’

[UiAutomator] Starting UiAutomator

[UiAutomator] Moving to state ‘starting’

[UiAutomator] Parsing uiautomator jar

[UiAutomator] Found jar name: ‘AppiumBootstrap.jar’

[ADB] Running ‘C:\Users\KotturJ\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 0915f9d3592c1904 push C:\Users\KotturJ\AppData\Local\Programs\Appium\resources\app\node_modules\appium-android-driver\bootstrap\bin\AppiumBootstrap.jar /data/local/tmp/’

[ADB] Attempting to kill all uiautomator processes

[ADB] Getting all processes with uiautomator

[ADB] Running ‘C:\Users\KotturJ\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 0915f9d3592c1904 shell ps’

[ADB] No ‘uiautomator’ process has been found

[UiAutomator] Starting UIAutomator

[ADB] Creating ADB subprocess with args: ["-P",5037,"-s","0915f9d3592c1904","shell","uiautomator","runtest","AppiumBootstrap.jar","-c","io.appium.android.bootstrap.Bootstrap","-e","pkg","com.company.mobile.projX","-e","disableAndroidWatchers",false,"-e","acceptSslCerts",false]

[UiAutomator] Moving to state ‘online’

[AndroidBootstrap] [BOOTSTRAP LOG] [debug] json loading complete.

[AndroidBootstrap] [BOOTSTRAP LOG] [debug] Registered crash watchers.

[AndroidBootstrap] Android bootstrap socket is now connected

[ADB] Running ‘C:\Users\KotturJ\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 0915f9d3592c1904 shell dumpsys window’

[AndroidBootstrap] [BOOTSTRAP LOG] [debug] Client connected

[AndroidDriver] Screen already unlocked, doing nothing

[ADB] Device API level: 24

[ADB] Running ‘C:\Users\KotturJ\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 0915f9d3592c1904 shell am start -W -n com.company.mobile.projX/md5cab66dbf08211acdc39d74bdadc3428b.SplashScreen -S’

[ADB] Waiting up to 20000ms for activity matching pkg: ‘com.company.mobile.projX’ and activity: ‘md5cab66dbf08211acdc39d74bdadc3428b.SplashScreen’ to be focused

[ADB] Possible activities, to be checked: ‘md5cab66dbf08211acdc39d74bdadc3428b.SplashScreen’, ‘com.company.mobile.projX.md5cab66dbf08211acdc39d74bdadc3428b.SplashScreen’

[ADB] Getting focused package and activity

[ADB] Running ‘C:\Users\KotturJ\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 0915f9d3592c1904 shell dumpsys window windows’

[ADB] Found package: ‘com.company.mobile.projX’ and fully qualified activity name : ‘md5cab66dbf08211acdc39d74bdadc3428b.MainActivity’

[ADB] Incorrect package and activity. Retrying.

[ADB] Getting focused package and activity

[ADB] Running ‘C:\Users\KotturJ\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 0915f9d3592c1904 shell dumpsys window windows’

[ADB] Found package: ‘com.company.mobile.projX’ and fully qualified activity name : ‘md5cab66dbf08211acdc39d74bdadc3428b.MainActivity’

[ADB] Incorrect package and activity. Retrying.

[ADB] Getting focused package and activity

[ADB] Running ‘C:\Users\KotturJ\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 0915f9d3592c1904 shell dumpsys window windows’

[ADB] Found package: ‘com.company.mobile.projX’ and fully qualified activity name : ‘md5cab66dbf08211acdc39d74bdadc3428b.MainActivity’

[ADB] Incorrect package and activity. Retrying.

[ADB] Getting focused package and activity

[ADB] Running ‘C:\Users\KotturJ\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 0915f9d3592c1904 shell dumpsys window windows’

[ADB] Found package: ‘com.company.mobile.projX’ and fully qualified activity name : ‘md5cab66dbf08211acdc39d74bdadc3428b.MainActivity’

[ADB] Incorrect package and activity. Retrying.

[ADB] Getting focused package and activity

[ADB] Running ‘C:\Users\KotturJ\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 0915f9d3592c1904 shell dumpsys window windows’

[ADB] Found package: ‘com.company.mobile.projX’ and fully qualified activity name : ‘md5cab66dbf08211acdc39d74bdadc3428b.MainActivity’

[ADB] Incorrect package and activity. Retrying.

[ADB] Getting focused package and activity

[ADB] Running ‘C:\Users\KotturJ\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 0915f9d3592c1904 shell dumpsys window windows’

[ADB] Found package: ‘com.company.mobile.projX’ and fully qualified activity name : ‘md5cab66dbf08211acdc39d74bdadc3428b.MainActivity’

[ADB] Incorrect package and activity. Retrying.

[ADB] Getting focused package and activity

[ADB] Running ‘C:\Users\KotturJ\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 0915f9d3592c1904 shell dumpsys window windows’

[ADB] Found package: ‘com.company.mobile.projX’ and fully qualified activity name : ‘md5cab66dbf08211acdc39d74bdadc3428b.MainActivity’

[ADB] Incorrect package and activity. Retrying.

[ADB] Getting focused package and activity

[ADB] Running ‘C:\Users\KotturJ\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 0915f9d3592c1904 shell dumpsys window windows’

[ADB] Found package: ‘com.company.mobile.projX’ and fully qualified activity name : ‘md5cab66dbf08211acdc39d74bdadc3428b.MainActivity’

[ADB] Incorrect package and activity. Retrying.

[ADB] Getting focused package and activity

[ADB] Running ‘C:\Users\KotturJ\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 0915f9d3592c1904 shell dumpsys window windows’

[ADB] Found package: ‘com.company.mobile.projX’ and fully qualified activity name : ‘md5cab66dbf08211acdc39d74bdadc3428b.MainActivity’

[ADB] Incorrect package and activity. Retrying.

[ADB] Getting focused package and activity

[ADB] Running ‘C:\Users\KotturJ\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 0915f9d3592c1904 shell dumpsys window windows’

[ADB] Found package: ‘com.company.mobile.projX’ and fully qualified activity name : ‘md5cab66dbf08211acdc39d74bdadc3428b.MainActivity’

[ADB] Incorrect package and activity. Retrying.

[ADB] Getting focused package and activity

[ADB] Running ‘C:\Users\KotturJ\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 0915f9d3592c1904 shell dumpsys window windows’

[ADB] Found package: ‘com.company.mobile.projX’ and fully qualified activity name : ‘md5cab66dbf08211acdc39d74bdadc3428b.MainActivity’

[ADB] Incorrect package and activity. Retrying.

[ADB] Getting focused package and activity

[ADB] Running ‘C:\Users\KotturJ\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 0915f9d3592c1904 shell dumpsys window windows’

[ADB] Found package: ‘com.company.mobile.projX’ and fully qualified activity name : ‘md5cab66dbf08211acdc39d74bdadc3428b.MainActivity’

[ADB] Incorrect package and activity. Retrying.

[ADB] Getting focused package and activity

[ADB] Running ‘C:\Users\KotturJ\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 0915f9d3592c1904 shell dumpsys window windows’

[ADB] Found package: ‘com.company.mobile.projX’ and fully qualified activity name : ‘md5cab66dbf08211acdc39d74bdadc3428b.MainActivity’

[ADB] Incorrect package and activity. Retrying.

[ADB] Getting focused package and activity

[ADB] Running ‘C:\Users\KotturJ\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 0915f9d3592c1904 shell dumpsys window windows’

[ADB] Found package: ‘com.company.mobile.projX’ and fully qualified activity name : ‘md5cab66dbf08211acdc39d74bdadc3428b.MainActivity’

[ADB] Incorrect package and activity. Retrying.

[ADB] Getting focused package and activity

[ADB] Running ‘C:\Users\KotturJ\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 0915f9d3592c1904 shell dumpsys window windows’

[ADB] Found package: ‘com.company.mobile.projX’ and fully qualified activity name : ‘md5cab66dbf08211acdc39d74bdadc3428b.MainActivity’

[ADB] Incorrect package and activity. Retrying.

[ADB] Getting focused package and activity

[ADB] Running ‘C:\Users\KotturJ\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 0915f9d3592c1904 shell dumpsys window windows’

[ADB] Found package: ‘com.company.mobile.projX’ and fully qualified activity name : ‘md5cab66dbf08211acdc39d74bdadc3428b.MainActivity’

[ADB] Incorrect package and activity. Retrying.

[ADB] Getting focused package and activity

[ADB] Running ‘C:\Users\KotturJ\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 0915f9d3592c1904 shell dumpsys window windows’

[ADB] Found package: ‘com.company.mobile.projX’ and fully qualified activity name : ‘md5cab66dbf08211acdc39d74bdadc3428b.MainActivity’

[ADB] Incorrect package and activity. Retrying.

[ADB] Getting focused package and activity

[ADB] Running ‘C:\Users\KotturJ\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 0915f9d3592c1904 shell dumpsys window windows’

[ADB] Found package: ‘com.company.mobile.projX’ and fully qualified activity name : ‘md5cab66dbf08211acdc39d74bdadc3428b.MainActivity’

[ADB] Incorrect package and activity. Retrying.

[ADB] Getting focused package and activity

[ADB] Running ‘C:\Users\KotturJ\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 0915f9d3592c1904 shell dumpsys window windows’

[ADB] Found package: ‘com.company.mobile.projX’ and fully qualified activity name : ‘md5cab66dbf08211acdc39d74bdadc3428b.MainActivity’

[ADB] Incorrect package and activity. Retrying.

[ADB] Getting focused package and activity

[ADB] Running ‘C:\Users\KotturJ\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 0915f9d3592c1904 shell dumpsys window windows’

[ADB] Found package: ‘com.company.mobile.projX’ and fully qualified activity name : ‘md5cab66dbf08211acdc39d74bdadc3428b.MainActivity’

[ADB] Incorrect package and activity. Retrying.

[ADB] Getting focused package and activity

[ADB] Running ‘C:\Users\KotturJ\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 0915f9d3592c1904 shell dumpsys window windows’

[ADB] Found package: ‘com.company.mobile.projX’ and fully qualified activity name : ‘md5cab66dbf08211acdc39d74bdadc3428b.MainActivity’

[ADB] Incorrect package and activity. Retrying.

[ADB] Getting focused package and activity

[ADB] Running ‘C:\Users\KotturJ\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 0915f9d3592c1904 shell dumpsys window windows’

[ADB] Found package: ‘com.company.mobile.projX’ and fully qualified activity name : ‘md5cab66dbf08211acdc39d74bdadc3428b.MainActivity’

[ADB] Incorrect package and activity. Retrying.

[ADB] Getting focused package and activity

[ADB] Running ‘C:\Users\KotturJ\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 0915f9d3592c1904 shell dumpsys window windows’

[ADB] Found package: ‘com.company.mobile.projX’ and fully qualified activity name : ‘md5cab66dbf08211acdc39d74bdadc3428b.MainActivity’

[ADB] Incorrect package and activity. Retrying.

[ADB] Getting focused package and activity

[ADB] Running ‘C:\Users\KotturJ\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 0915f9d3592c1904 shell dumpsys window windows’

[ADB] Found package: ‘com.company.mobile.projX’ and fully qualified activity name : ‘md5cab66dbf08211acdc39d74bdadc3428b.MainActivity’

[ADB] Incorrect package and activity. Retrying.

[ADB] Getting focused package and activity

[ADB] Running ‘C:\Users\KotturJ\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 0915f9d3592c1904 shell dumpsys window windows’

[ADB] Found package: ‘com.company.mobile.projX’ and fully qualified activity name : ‘md5cab66dbf08211acdc39d74bdadc3428b.MainActivity’

[ADB] Incorrect package and activity. Retrying.

[ADB] Getting focused package and activity

[ADB] Running ‘C:\Users\KotturJ\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 0915f9d3592c1904 shell dumpsys window windows’

[ADB] Found package: ‘com.company.mobile.projX’ and fully qualified activity name : ‘md5cab66dbf08211acdc39d74bdadc3428b.MainActivity’

[ADB] Incorrect package and activity. Retrying.

[AndroidDriver] Shutting down Android driver

[ADB] Running ‘C:\Users\KotturJ\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 0915f9d3592c1904 shell am force-stop com.company.mobile.projX’

[ADB] Pressing the HOME button

[ADB] Running ‘C:\Users\KotturJ\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 0915f9d3592c1904 shell input keyevent 3’

[AndroidBootstrap] Sending command to android: {"cmd":"shutdown"}

[AndroidBootstrap] [BOOTSTRAP LOG] [debug] Got data from client: {"cmd":"shutdown"}

[AndroidBootstrap] [BOOTSTRAP LOG] [debug] Got command of type SHUTDOWN

[AndroidBootstrap] [BOOTSTRAP LOG] [debug] Returning result: {"status":0,"value":"OK, shutting down"}

[AndroidBootstrap] Received command result from bootstrap

[UiAutomator] Shutting down UiAutomator

[UiAutomator] Moving to state ‘stopping’

[UiAutomator] UiAutomator shut down normally

[UiAutomator] Moving to state ‘stopped’

[ADB] Attempting to kill all uiautomator processes

[ADB] Getting all processes with uiautomator

[ADB] Running ‘C:\Users\KotturJ\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 0915f9d3592c1904 shell ps’

[ADB] No ‘uiautomator’ process has been found

[UiAutomator] Moving to state ‘stopped’

[Logcat] Stopping logcat capture

[ADB] Running ‘C:\Users\KotturJ\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 0915f9d3592c1904 shell am force-stop io.appium.unlock’

[AndroidDriver] Not cleaning generated files. Add clearSystemFiles capability if wanted.

[BaseDriver] Event ‘newSessionStarted’ logged at 1553080443786 (16:44:03 GMT+0530 (India Standard Time))

[W3C] Encountered internal error running command: Error: Cannot start the ‘com.company.mobile.projX’ application. Visit https://github.com/appium/appium/blob/master/docs/en/writing-running-appium/android/activity-startup.md for troubleshooting. Original error: ‘md5cab66dbf08211acdc39d74bdadc3428b.SplashScreen’ or ‘com.company.mobile.projX.md5cab66dbf08211acdc39d74bdadc3428b.SplashScreen’ never started. Visit https://github.com/appium/appium/blob/master/docs/en/writing-running-appium/android/activity-startup.md for troubleshooting

[W3C] at ADB.apkUtilsMethods.startApp (C:\Users\KotturJ\AppData\Local\Programs\Appium\resources\app\node_modules\appium-adb\lib\tools\apk-utils.js:144:11)

[W3C] at process._tickCallback (internal/process/next_tick.js:68:7)

[HTTP] <-- POST /wd/hub/session 500 58148 ms - 1594

[HTTP]


#2

PLease help me. Above


#3

Try setting your capabilities to mobile capabilities.
caps.setCapability(AndroidMobileCapabilityType.APP_ACTIVITY, "md5cab66dbf08211acdc39d74bdadc3428b.MainActivity");

Are you also sure that is the name of the activity you want to launch? Looks kind of odd to me


#4

ThankQ Tom .

But not working. Please help me

Command promt using ‘‘mCurrentFocus’’ i got
Activity name: md5cab66dbf08211acdc39d74bdadc3428b
Installed old Appium 1.4.16 in that Activity name: “com.worklight.wlclient.ui.UIActivity”.

Both used but not working.

C:\Users\KotturJ>java -version
java version “1.8.0_191”
Java™ SE Runtime Environment (build 1.8.0_191-b12)
Java HotSpot™ Client VM (build 25.191-b12, mixed mode, sharing)
C:\Users\KotturJ>npm -v
6.9.0
C:\Users\KotturJ>appium -v
1.6.5-beta


#5

Have you tried appium-doctor. Very useful for diagnosing problems


#6

Hi, please help me .

Unable to install apk file.

Appium server log:

[info] e[35m[Appium]e[39m Welcome to Appium v1.12.1
[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[37mPOSTe[39m e[37m/wd/hub/sessione[39m
[info] e[35m[HTTP]e[39m e[90m{“desiredCapabilities”:{“app”:“C:\MobileAutomation\APK\CP4.apk”,“platformVersion”:“8.0.0”,“app-package”:“com.parexel.mobile.rtsm”,“browserName”:"",“platformName”:“Android”,“deviceName”:“4200c4c9cce0542b”},“capabilities”:{“firstMatch”:[{“appium:app”:“C:\MobileAutomation\APK\CP4.apk”,“app-package”:“com.parexel.mobile.rtsm”,“browserName”:"",“appium:deviceName”:“4200c4c9cce0542b”,“platformName”:“android”,“appium:platformVersion”:“8.0.0”}]}}e[39m
[debug] e[35m[W3C]e[39m Calling AppiumDriver.createSession() with args: [{“app”:“C:\MobileAutomation\APK\CP4.apk”,“platformVersion”:“8.0.0”,“app-package”:“com.parexel.mobile.rtsm”,“browserName”:"",“platformName”:“Android”,“deviceName”:“4200c4c9cce0542b”},null,{“firstMatch”:[{“appium:app”:“C:\MobileAutomation\APK\CP4.apk”,“app-package”:“com.parexel.mobile.rtsm”,“browserName”:"",“appium:deviceName”:“4200c4c9cce0542b”,“platformName”:“android”,“appium:platformVersion”:“8.0.0”}]}]
[debug] e[35m[BaseDriver]e[39m Event ‘newSessionRequested’ logged at 1555068980910 (17:06:20 GMT+0530 (India Standard Time))
[warn] e[35m[BaseDriver]e[39m The capabilities [“app-package”] are not standard capabilities and should have an extension prefix
[warn] e[35m[Appium]e[39m DeprecationWarning: ‘automationName’ capability was not provided. Future versions of Appium will require ‘automationName’ capability to be set for Android sessions.
[info] e[35m[Appium]e[39m Setting automation to ‘UiAutomator1’.
[warn] e[35m[Appium]e[39m Consider setting ‘automationName’ capability to ‘UiAutomator2’ on Android >= 6, since UIAutomator1 framework is not maintained anymore by the OS vendor.
[info] e[35m[Appium]e[39m Appium v1.12.1 creating new AndroidDriver (v4.11.0) session
[info] e[35m[Appium]e[39m Capabilities:
[info] e[35m[Appium]e[39m app-package: com.parexel.mobile.rtsm
[info] e[35m[Appium]e[39m browserName:
[info] e[35m[Appium]e[39m platformName: android
[info] e[35m[Appium]e[39m app: C:\MobileAutomation\APK\CP4.apk
[info] e[35m[Appium]e[39m deviceName: 4200c4c9cce0542b
[info] e[35m[Appium]e[39m platformVersion: 8.0.0
[debug] e[35m[BaseDriver]e[39m W3C capabilities {“alwaysMatch”:{“appium:app… and MJSONWP desired capabilities {“app”:“C:\MobileAutomatio… were provided
[debug] e[35m[BaseDriver]e[39m Creating session with W3C capabilities: {“alwaysMatch”:{“appium:app…
[warn] e[35m[BaseDriver]e[39m The following capabilities were provided, but are not recognized by appium: app-package.
[info] e[35m[BaseDriver]e[39m Session created with session id: 1842d004-3def-49c7-8efa-b86daf971bff
[info] e[35m[ADB]e[39m Checking whether adb is present[debug] e[35m[ADB]e[39m 1 device(s) connected
[info] e[35m[AndroidDriver]e[39m Looking for a device with Android ‘8.0.0’
[debug] e[35m[ADB]e[39m Setting device id to 4200c4c9cce0542b
[info] e[35m[ADB]e[39m Getting device platform version
[debug] e[35m[ADB]e[39m Running ‘C:\Users\KotturJ\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 4200c4c9cce0542b shell getprop ro.build.version.release’
[debug] e[35m[ADB]e[39m Current device property ‘ro.build.version.release’: 8.0.0
[info] e[35m[AndroidDriver]e[39m Using device: 4200c4c9cce0542b
[debug] e[35m[ADB]e[39m Setting device id to 4200c4c9cce0542b
[debug] e[35m[ADB]e[39m Running ‘C:\Users\KotturJ\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 4200c4c9cce0542b 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
[warn] e[35m[AndroidDriver]e[39m Consider setting ‘automationName’ capability to ‘uiautomator2’ on Android >= 6, since UIAutomator framework is not maintained anymore by the OS vendor.
[info] e[35m[BaseDriver]e[39m Using local app ‘C:\MobileAutomation\APK\CP4.apk’
[debug] e[35m[AndroidDriver]e[39m Checking whether app is actually present
[info] e[35m[AndroidDriver]e[39m Starting Android session
[debug] e[35m[ADB]e[39m Running ‘C:\Users\KotturJ\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 4200c4c9cce0542b wait-for-device’[debug] e[35m[ADB]e[39m Running ‘C:\Users\KotturJ\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 4200c4c9cce0542b 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\KotturJ\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 4200c4c9cce0542b shell dumpsys package io.appium.settings’[info] e[35m[ADB]e[39m Checking whether aapt is present
[info] e[35m[ADB]e[39m Using aapt.exe from C:\Users\KotturJ\AppData\Local\Android\Sdk\build-tools\28.0.3\aapt.exe
[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.0’ >= ‘2.14.0’)
[debug] e[35m[ADB]e[39m There is no need to install/upgrade ‘C:\Users\KotturJ\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\KotturJ\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 4200c4c9cce0542b shell ‘pgrep --help; echo $?’’[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\KotturJ\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 4200c4c9cce0542b shell appops set io.appium.settings android:mock_location allow’[debug] e[35m[Logcat]e[39m Starting logcat capture
[info] e[35m[ADB]e[39m Getting device platform version
[debug] e[35m[ADB]e[39m Running ‘C:\Users\KotturJ\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 4200c4c9cce0542b shell getprop ro.build.version.release’[debug] e[35m[ADB]e[39m Current device property ‘ro.build.version.release’: 8.0.0
[debug] e[35m[ADB]e[39m Running ‘C:\Users\KotturJ\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 4200c4c9cce0542b shell wm size’[debug] e[35m[ADB]e[39m Running ‘C:\Users\KotturJ\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 4200c4c9cce0542b shell getprop ro.product.model’
[debug] e[35m[ADB]e[39m Current device property ‘ro.product.model’: SM-J330F
[debug] e[35m[ADB]e[39m Running ‘C:\Users\KotturJ\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 4200c4c9cce0542b shell getprop ro.product.manufacturer’[debug] e[35m[ADB]e[39m Current device property ‘ro.product.manufacturer’: samsung
[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\KotturJ\AppData\Local\Android\Sdk\platform-tools\apkanalyzer.bat,C:\Users\KotturJ\AppData\Local\Android\Sdk\emulator\apkanalyzer.bat,C:\Users\KotturJ\AppData\Local\Android\Sdk\tools\apkanalyzer.bat,C:\Users\KotturJ\AppData\Local\Android\Sdk\tools\bin\apkanalyzer.bat,C:\Users\KotturJ\AppData\Local\Android\Sdk\build-tools\28.0.3\apkanalyzer.bat,C:\Users\KotturJ\AppData\Local\Android\Sdk\build-tools\25.0.0\apkanalyzer.bat,C:\Users\KotturJ\AppData\Local\Android\Sdk\build-tools\24.0.0\apkanalyzer.bat. Do you have the Android SDK installed at ‘C:\Users\KotturJ\AppData\Local\Android\Sdk’?
[info] e[35m[ADB]e[39m Extracting package and launch activity from manifest
[info] e[35m[ADB]e[39m Package name: ‘com.parexel.mobile.rtsm’
[info] e[35m[ADB]e[39m Main activity name: ‘md5cab66dbf08211acdc39d74bdadc3428b.SplashScreen’
[debug] e[35m[AndroidDriver]e[39m Parsed package and activity are: com.parexel.mobile.rtsm/md5cab66dbf08211acdc39d74bdadc3428b.SplashScreen
[debug] e[35m[ADB]e[39m Getting install status for com.parexel.mobile.rtsm
[debug] e[35m[ADB]e[39m Running ‘C:\Users\KotturJ\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 4200c4c9cce0542b shell dumpsys package com.parexel.mobile.rtsm’
[debug] e[35m[ADB]e[39m ‘com.parexel.mobile.rtsm’ is installed
[debug] e[35m[ADB]e[39m Getting install status for com.parexel.mobile.rtsm
[debug] e[35m[ADB]e[39m Running ‘C:\Users\KotturJ\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 4200c4c9cce0542b shell dumpsys package com.parexel.mobile.rtsm’[debug] e[35m[ADB]e[39m ‘com.parexel.mobile.rtsm’ is installed
[debug] e[35m[ADB]e[39m Getting package info for ‘com.parexel.mobile.rtsm’
[debug] e[35m[ADB]e[39m Running ‘C:\Users\KotturJ\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 4200c4c9cce0542b shell dumpsys package com.parexel.mobile.rtsm’
[debug] e[35m[ADB]e[39m The version name of the installed ‘com.parexel.mobile.rtsm’ is greater or equal to the application version name (‘2.2.1’ >= ‘2.2.1’)
[debug] e[35m[ADB]e[39m There is no need to install/upgrade ‘C:\MobileAutomation\APK\CP4.apk’
[info] e[35m[AndroidDriver]e[39m Performing fast reset on ‘com.parexel.mobile.rtsm’
[debug] e[35m[ADB]e[39m Getting install status for com.parexel.mobile.rtsm
[debug] e[35m[ADB]e[39m Running ‘C:\Users\KotturJ\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 4200c4c9cce0542b shell dumpsys package com.parexel.mobile.rtsm’[debug] e[35m[ADB]e[39m ‘com.parexel.mobile.rtsm’ is installed
[debug] e[35m[ADB]e[39m Running ‘C:\Users\KotturJ\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 4200c4c9cce0542b shell am force-stop com.parexel.mobile.rtsm’[debug] e[35m[ADB]e[39m Running ‘C:\Users\KotturJ\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 4200c4c9cce0542b shell pm clear com.parexel.mobile.rtsm’[debug] e[35m[AndroidDriver]e[39m Performed fast reset on the installed ‘com.parexel.mobile.rtsm’ application (stop and clear)
[debug] e[35m[ADB]e[39m Running ‘C:\Users\KotturJ\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 4200c4c9cce0542b shell rm -rf /data/local/tmp/strings.json’[debug] e[35m[AndroidDriver]e[39m Extracting strings from apk
[debug] e[35m[AndroidDriver]e[39m C:\MobileAutomation\APK\CP4.apk
[debug] e[35m[AndroidDriver]e[39m undefined
[debug] e[35m[AndroidDriver]e[39m C:\Users\KotturJ\AppData\Local\Temp\com.parexel.mobile.rtsm
[debug] e[35m[ADB]e[39m Extracting strings from for language: default
[info] e[35m[ADB]e[39m Successfully extracted 202 strings from ‘C:\MobileAutomation\APK\CP4.apk’ resources for ‘(default)’ configuration
[debug] e[35m[ADB]e[39m Running ‘C:\Users\KotturJ\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 4200c4c9cce0542b push C:\Users\KotturJ\AppData\Local\Temp\com.parexel.mobile.rtsm\strings.json /data/local/tmp’[debug] e[35m[AndroidBootstrap]e[39m Watching for bootstrap disconnect
[debug] e[35m[ADB]e[39m Forwarding system: 4724 to device: 4724
[debug] e[35m[ADB]e[39m Running ‘C:\Users\KotturJ\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 4200c4c9cce0542b forward tcp:4724 tcp:4724’
[debug] e[35m[UiAutomator]e[39m Starting UiAutomator
[debug] e[35m[UiAutomator]e[39m Moving to state ‘starting’
[debug] e[35m[UiAutomator]e[39m Parsing uiautomator jar
[debug] e[35m[UiAutomator]e[39m Found jar name: ‘AppiumBootstrap.jar’
[debug] e[35m[ADB]e[39m Running ‘C:\Users\KotturJ\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 4200c4c9cce0542b push C:\Users\KotturJ\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-android-driver\bootstrap\bin\AppiumBootstrap.jar /data/local/tmp/’
[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\KotturJ\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 4200c4c9cce0542b shell pgrep ^uiautomator$’[info] e[35m[ADB]e[39m No ‘uiautomator’ process has been found
[debug] e[35m[UiAutomator]e[39m Starting UIAutomator
[debug] e[35m[ADB]e[39m Creating ADB subprocess with args: [”-P”,5037,”-s",“4200c4c9cce0542b”,“shell”,“uiautomator”,“runtest”,“AppiumBootstrap.jar”,"-c",“io.appium.android.bootstrap.Bootstrap”,"-e",“pkg”,“com.parexel.mobile.rtsm”,"-e",“disableAndroidWatchers”,false,"-e",“acceptSslCerts”,false][debug] e[35m[UiAutomator]e[39m Moving to state ‘online’
[debug] e[35m[AndroidBootstrap]e[39m [BOOTSTRAP LOG] [debug] Loading json…
[debug] e[35m[AndroidBootstrap]e[39m [BOOTSTRAP LOG] [debug] json loading complete.
[info] e[35m[AndroidBootstrap]e[39m Android bootstrap socket is now connected
[debug] e[35m[AndroidBootstrap]e[39m [BOOTSTRAP LOG] [debug] Registered crash watchers.
[debug] e[35m[ADB]e[39m Running ‘C:\Users\KotturJ\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 4200c4c9cce0542b shell dumpsys window’
[debug] e[35m[AndroidBootstrap]e[39m [BOOTSTRAP LOG] [debug] Client connected
[debug] e[35m[AndroidDriver]e[39m Screen is locked, trying to unlock
[warn] e[35m[AndroidDriver]e[39m Using app unlock, this is going to be deprecated!
[info] e[35m[AndroidDriver]e[39m Unlocking screen
[info] e[35m[AndroidDriver]e[39m Launching .Unlock
[debug] e[35m[ADB]e[39m Running ‘C:\Users\KotturJ\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 4200c4c9cce0542b shell am start -n io.appium.settings/.Unlock -c android.intent.category.LAUNCHER -a android.intent.action.MAIN -f 0x10200000’[debug] e[35m[AndroidBootstrap]e[39m Emitting alert message…
[debug] e[35m[AndroidBootstrap]e[39m [BOOTSTRAP LOG] [debug] Emitting system alert message[debug] e[35m[ADB]e[39m Running ‘C:\Users\KotturJ\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 4200c4c9cce0542b shell am start -W -n com.parexel.mobile.rtsm/md5cab66dbf08211acdc39d74bdadc3428b.SplashScreen -S’[debug] e[35m[ADB]e[39m Waiting up to 20000ms for activity matching pkg: ‘com.parexel.mobile.rtsm’ and activity: ‘md5cab66dbf08211acdc39d74bdadc3428b.SplashScreen’ to be focused
[debug] e[35m[ADB]e[39m Possible activities, to be checked: ‘md5cab66dbf08211acdc39d74bdadc3428b.SplashScreen’, ‘com.parexel.mobile.rtsm.md5cab66dbf08211acdc39d74bdadc3428b.SplashScreen’
[debug] e[35m[ADB]e[39m Getting focused package and activity
[debug] e[35m[ADB]e[39m Running ‘C:\Users\KotturJ\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 4200c4c9cce0542b shell dumpsys window windows’[debug] e[35m[ADB]e[39m Found package: ‘com.parexel.mobile.rtsm’ and fully qualified activity name : ‘md5cab66dbf08211acdc39d74bdadc3428b.MainActivity’
[debug] e[35m[ADB]e[39m Incorrect package and activity. Retrying.[debug] e[35m[ADB]e[39m Getting focused package and activity
[debug] e[35m[ADB]e[39m Running ‘C:\Users\KotturJ\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 4200c4c9cce0542b shell dumpsys window windows’[debug] e[35m[ADB]e[39m Found package: ‘com.parexel.mobile.rtsm’ and fully qualified activity name : ‘md5cab66dbf08211acdc39d74bdadc3428b.MainActivity’
[debug] e[35m[ADB]e[39m Incorrect package and activity. Retrying.[debug] e[35m[ADB]e[39m Getting focused package and activity
[debug] e[35m[ADB]e[39m Running ‘C:\Users\KotturJ\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 4200c4c9cce0542b shell dumpsys window windows’[debug] e[35m[ADB]e[39m Found package: ‘com.parexel.mobile.rtsm’ and fully qualified activity name : ‘md5cab66dbf08211acdc39d74bdadc3428b.MainActivity’
[debug] e[35m[ADB]e[39m Incorrect package and activity. Retrying.[debug] e[35m[ADB]e[39m Getting focused package and activity
[debug] e[35m[ADB]e[39m Running ‘C:\Users\KotturJ\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 4200c4c9cce0542b shell dumpsys window windows’[debug] e[35m[ADB]e[39m Found package: ‘com.parexel.mobile.rtsm’ and fully qualified activity name : ‘md5cab66dbf08211acdc39d74bdadc3428b.MainActivity’
[debug] e[35m[ADB]e[39m Incorrect package and activity. Retrying.[debug] e[35m[ADB]e[39m Getting focused package and activity
[debug] e[35m[ADB]e[39m Running ‘C:\Users\KotturJ\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 4200c4c9cce0542b shell dumpsys window windows’[debug] e[35m[ADB]e[39m Getting focused package and activity
[debug] e[35m[ADB]e[39m Running ‘C:\Users\KotturJ\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 4200c4c9cce0542b shell dumpsys window windows’[debug] e[35m[ADB]e[39m Found package: ‘com.parexel.mobile.rtsm’ and fully qualified activity name : ‘md5cab66dbf08211acdc39d74bdadc3428b.MainActivity’
[debug] e[35m[ADB]e[39m Incorrect package and activity. Retrying.[debug] e[35m[ADB]e[39m Getting focused package and activity
[debug] e[35m[ADB]e[39m Running ‘C:\Users\KotturJ\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 4200c4c9cce0542b shell dumpsys window windows’
[debug] e[35m[ADB]e[39m Found package: ‘com.parexel.mobile.rtsm’ and fully qualified activity name : ‘md5cab66dbf08211acdc39d74bdadc3428b.MainActivity’
[debug] e[35m[ADB]e[39m Incorrect package and activity. Retrying.[debug] e[35m[ADB]e[39m Getting focused package and activity
[debug] e[35m[ADB]e[39m Running ‘C:\Users\KotturJ\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 4200c4c9cce0542b shell dumpsys window windows’[debug] e[35m[ADB]e[39m Found package: ‘com.parexel.mobile.rtsm’ and fully qualified activity name : ‘md5cab66dbf08211acdc39d74bdadc3428b.MainActivity’
[debug] e[35m[ADB]e[39m Incorrect package and activity. Retrying.[debug] e[35m[ADB]e[39m Getting focused package and activity
[debug] e[35m[ADB]e[39m Running ‘C:\Users\KotturJ\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 4200c4c9cce0542b shell dumpsys window windows’[debug] e[35m[ADB]e[39m Found package: ‘com.parexel.mobile.rtsm’ and fully qualified activity name : ‘md5cab66dbf08211acdc39d74bdadc3428b.MainActivity’
[debug] e[35m[ADB]e[39m Incorrect package and activity. Retrying.[debug] e[35m[ADB]e[39m Getting focused package and activity
[debug] e[35m[ADB]e[39m Running ‘C:\Users\KotturJ\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 4200c4c9cce0542b shell dumpsys window windows’[debug] e[35m[ADB]e[39m Found package: ‘com.parexel.mobile.rtsm’ and fully qualified activity name : ‘md5cab66dbf08211acdc39d74bdadc3428b.MainActivity’
[debug] e[35m[ADB]e[39m Incorrect package and activity. Retrying.[debug] e[35m[ADB]e[39m Getting focused package and activity
[debug] e[35m[ADB]e[39m Running ‘C:\Users\KotturJ\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 4200c4c9cce0542b shell dumpsys window windows’
[debug] e[35m[ADB]e[39m Found package: ‘com.parexel.mobile.rtsm’ and fully qualified activity name : ‘md5cab66dbf08211acdc39d74bdadc3428b.MainActivity’
[debug] e[35m[ADB]e[39m Incorrect package and activity. Retrying.[debug] e[35m[ADB]e[39m Getting focused package and activity
[debug] e[35m[ADB]e[39m Running ‘C:\Users\KotturJ\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 4200c4c9cce0542b shell dumpsys window windows’[debug] e[35m[ADB]e[39m Found package: ‘com.parexel.mobile.rtsm’ and fully qualified activity name : ‘md5cab66dbf08211acdc39d74bdadc3428b.MainActivity’
[debug] e[35m[ADB]e[39m Incorrect package and activity. Retrying.[debug] e[35m[ADB]e[39m Getting focused package and activity
[debug] e[35m[ADB]e[39m Running ‘C:\Users\KotturJ\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 4200c4c9cce0542b shell dumpsys window windows’[debug] e[35m[ADB]e[39m Getting focused package and activity
[debug] e[35m[ADB]e[39m Running ‘C:\Users\KotturJ\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 4200c4c9cce0542b shell dumpsys window windows’
[debug] e[35m[ADB]e[39m Found package: ‘com.parexel.mobile.rtsm’ and fully qualified activity name : ‘md5cab66dbf08211acdc39d74bdadc3428b.MainActivity’
[debug] e[35m[ADB]e[39m Incorrect package and activity. Retrying.[debug] e[35m[ADB]e[39m Getting focused package and activity
[debug] e[35m[ADB]e[39m Running ‘C:\Users\KotturJ\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 4200c4c9cce0542b shell dumpsys window windows’[debug] e[35m[ADB]e[39m Found package: ‘com.parexel.mobile.rtsm’ and fully qualified activity name : ‘md5cab66dbf08211acdc39d74bdadc3428b.MainActivity’
[debug] e[35m[ADB]e[39m Incorrect package and activity. Retrying.[debug] e[35m[ADB]e[39m Getting focused package and activity
[debug] e[35m[ADB]e[39m Running ‘C:\Users\KotturJ\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 4200c4c9cce0542b shell dumpsys window windows’
[debug] e[35m[ADB]e[39m Found package: ‘com.parexel.mobile.rtsm’ and fully qualified activity name : ‘md5cab66dbf08211acdc39d74bdadc3428b.MainActivity’
[debug] e[35m[ADB]e[39m Incorrect package and activity. Retrying.[debug] e[35m[ADB]e[39m Getting focused package and activity
[debug] e[35m[ADB]e[39m Running ‘C:\Users\KotturJ\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 4200c4c9cce0542b shell dumpsys window windows’[debug] e[35m[ADB]e[39m Found package: ‘com.parexel.mobile.rtsm’ and fully qualified activity name : ‘md5cab66dbf08211acdc39d74bdadc3428b.MainActivity’
[debug] e[35m[ADB]e[39m Incorrect package and activity. Retrying.[debug] e[35m[ADB]e[39m Getting focused package and activity
[debug] e[35m[ADB]e[39m Running ‘C:\Users\KotturJ\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 4200c4c9cce0542b shell dumpsys window windows’[debug] e[35m[ADB]e[39m Found package: ‘com.parexel.mobile.rtsm’ and fully qualified activity name : ‘md5cab66dbf08211acdc39d74bdadc3428b.MainActivity’
[debug] e[35m[ADB]e[39m Incorrect package and activity. Retrying.[debug] e[35m[ADB]e[39m Getting focused package and activity
[debug] e[35m[ADB]e[39m Running ‘C:\Users\KotturJ\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 4200c4c9cce0542b shell dumpsys window windows’
[debug] e[35m[ADB]e[39m Found package: ‘com.parexel.mobile.rtsm’ and fully qualified activity name : ‘md5cab66dbf08211acdc39d74bdadc3428b.MainActivity’
[debug] e[35m[ADB]e[39m Incorrect package and activity. Retrying.[debug] e[35m[ADB]e[39m Getting focused package and activity
[debug] e[35m[ADB]e[39m Running ‘C:\Users\KotturJ\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 4200c4c9cce0542b shell dumpsys window windows’[debug] e[35m[ADB]e[39m Found package: ‘com.parexel.mobile.rtsm’ and fully qualified activity name : ‘md5cab66dbf08211acdc39d74bdadc3428b.MainActivity’
[debug] e[35m[ADB]e[39m Incorrect package and activity. Retrying.[debug] e[35m[ADB]e[39m Getting focused package and activity
[debug] e[35m[ADB]e[39m Running ‘C:\Users\KotturJ\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 4200c4c9cce0542b shell dumpsys window windows’[debug] e[35m[ADB]e[39m Getting focused package and activity
[debug] e[35m[ADB]e[39m Running ‘C:\Users\KotturJ\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 4200c4c9cce0542b shell dumpsys window windows’[debug] e[35m[ADB]e[39m Getting focused package and activity
[debug] e[35m[ADB]e[39m Running ‘C:\Users\KotturJ\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 4200c4c9cce0542b shell dumpsys window windows’
[debug] e[35m[ADB]e[39m Found package: ‘com.parexel.mobile.rtsm’ and fully qualified activity name : ‘md5cab66dbf08211acdc39d74bdadc3428b.MainActivity’
[debug] e[35m[ADB]e[39m Incorrect package and activity. Retrying.[debug] e[35m[ADB]e[39m Getting focused package and activity
[debug] e[35m[ADB]e[39m Running ‘C:\Users\KotturJ\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 4200c4c9cce0542b shell dumpsys window windows’[debug] e[35m[ADB]e[39m Found package: ‘com.parexel.mobile.rtsm’ and fully qualified activity name : ‘md5cab66dbf08211acdc39d74bdadc3428b.MainActivity’
[debug] e[35m[ADB]e[39m Incorrect package and activity. Retrying.[debug] e[35m[ADB]e[39m Getting focused package and activity
[debug] e[35m[ADB]e[39m Running ‘C:\Users\KotturJ\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 4200c4c9cce0542b shell dumpsys window windows’[debug] e[35m[ADB]e[39m Found package: ‘com.parexel.mobile.rtsm’ and fully qualified activity name : ‘md5cab66dbf08211acdc39d74bdadc3428b.MainActivity’
[debug] e[35m[ADB]e[39m Incorrect package and activity. Retrying.[debug] e[35m[ADB]e[39m Getting focused package and activity
[debug] e[35m[ADB]e[39m Running ‘C:\Users\KotturJ\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 4200c4c9cce0542b shell dumpsys window windows’[debug] e[35m[ADB]e[39m Pressing the HOME button
[debug] e[35m[ADB]e[39m Running ‘C:\Users\KotturJ\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 4200c4c9cce0542b shell input keyevent 3’[debug] e[35m[AndroidBootstrap]e[39m Sending command to android: {“cmd”:“shutdown”}
[debug] e[35m[AndroidBootstrap]e[39m [BOOTSTRAP LOG] [debug] Got data from client: {“cmd”:“shutdown”}
[debug] e[35m[AndroidBootstrap]e[39m [BOOTSTRAP LOG] [debug] Got command of type SHUTDOWN
[debug] e[35m[AndroidBootstrap]e[39m [BOOTSTRAP LOG] [debug] Returning result: {“status”:0,“value”:“OK, shutting down”}
[debug] e[35m[AndroidBootstrap]e[39m Received command result from bootstrap
[debug] e[35m[UiAutomator]e[39m Shutting down UiAutomator
[debug] e[35m[UiAutomator]e[39m Moving to state ‘stopping’
[debug] e[35m[UiAutomator]e[39m UiAutomator shut down normally
[debug] e[35m[UiAutomator]e[39m Moving to state ‘stopped’
[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\KotturJ\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 4200c4c9cce0542b shell pgrep ^uiautomator$’[info] e[35m[ADB]e[39m No ‘uiautomator’ process has been found
[debug] e[35m[UiAutomator]e[39m Moving to state ‘stopped’
[debug] e[35m[Logcat]e[39m Stopping logcat capture
[debug] e[35m[ADB]e[39m Running ‘C:\Users\KotturJ\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 4200c4c9cce0542b shell am force-stop io.appium.unlock’[debug] e[35m[AndroidDriver]e[39m Not cleaning generated files. Add clearSystemFiles capability if wanted.
[debug] e[35m[BaseDriver]e[39m Event ‘newSessionStarted’ logged at 1555069032242 (17:07:12 GMT+0530 (India Standard Time))
[debug] e[35m[W3C]e[39m Encountered internal error running command: Error: Cannot start the ‘com.parexel.mobile.rtsm’ application. Visit https://github.com/appium/appium/blob/master/docs/en/writing-running-appium/android/activity-startup.md for troubleshooting. Original error: ‘md5cab66dbf08211acdc39d74bdadc3428b.SplashScreen’ or ‘com.parexel.mobile.rtsm.md5cab66dbf08211acdc39d74bdadc3428b.SplashScreen’ never started. Visit https://github.com/appium/appium/blob/master/docs/en/writing-running-appium/android/activity-startup.md for troubleshooting
[debug] e[35m[W3C]e[39m at ADB.startApp (C:\Users\KotturJ\AppData\Local\Programs\Appium\resources\app\node_modules\appium\node_modules\appium-adb\lib\tools\apk-utils.js:149:11)
[debug] e[35m[W3C]e[39m at process._tickCallback (internal/process/next_tick.js:68:7)
[info] e[35m[HTTP]e[39m e[37m<-- POST /wd/hub/session e[39me[31m500e[39m e[90m51405 ms - 1638e[39m
[info] e[35m[HTTP]e[39m e[90me[39m