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]