Getting A new session could not be created. error

wajahat5139 · November 15, 2014, 7:39pm

When i run a specific .apk file it throws an error, But some times it runs fine.
If i change app apk file and run the same code with a different app .apk file it runs fine. Do you guys know what could be the issue?

Exception in thread “main” org.openqa.selenium.SessionNotCreatedException: A new session could not be created. (Original error: com.dominospizza/.activities.InitialLaunchActivity never started. Current: com.dominospizza/com.dominos.activities.LandingActivity_) (WARNING: The server did not provide any stacktrace information)
Command duration or timeout: 34.60 seconds
Build info: version: ‘2.44.0’, revision: ‘76d78cf’, time: ‘2014-10-23 20:03:00’
System info: host: ‘AWANW-8460W’, ip: ‘10.1.158.54’, os.name: ‘Windows 7’, os.arch: ‘amd64’, os.version: ‘6.1’, java.version: ‘1.8.0_25’
Driver info: io.appium.java_client.AppiumDriver
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
at java.lang.reflect.Constructor.newInstance(Unknown Source)
at org.openqa.selenium.remote.ErrorHandler.createThrowable(ErrorHandler.java:204)
at org.openqa.selenium.remote.ErrorHandler.throwIfResponseFailed(ErrorHandler.java:156)
at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:599)
at io.appium.java_client.AppiumDriver.execute(AppiumDriver.java:95)
at org.openqa.selenium.remote.RemoteWebDriver.startSession(RemoteWebDriver.java:240)
at org.openqa.selenium.remote.RemoteWebDriver.(RemoteWebDriver.java:126)
at org.openqa.selenium.remote.RemoteWebDriver.(RemoteWebDriver.java:153)
at io.appium.java_client.AppiumDriver.(AppiumDriver.java:49)
at DominosApp.main(DominosApp.java:33)

ddress":“127.0.0.1”,“noReset”:true,“logNoColors”:true,“platformName”:“Android”,“platformVersion”:“18”,“automationName”:“Appium”}

info: Appium REST http interface listener started on 127.0.0.1:4723
info: LogLevel: debug
info: → POST /wd/hub/session {“desiredCapabilities”:{“app”:“C:\Users\awanw\Downloads\com.whatsapp-2.apk”,“platformVersion”:“4.4.2”,“browserName”:“”,“platformName”:“Android”,“deviceName”:“SM-N900V”}}
debug: Appium request initiated at /wd/hub/session
debug: Request received with params: {“desiredCapabilities”:{“app”:“C:\Users\awanw\Downloads\com.whatsapp-2.apk”,“platformVersion”:“4.4.2”,“browserName”:“”,“platformName”:“Android”,“deviceName”:“SM-N900V”}}
info: Starting android appium
debug: No appActivity desired capability or server param. Parsing from apk.
debug: No appPackage desired capability or server param. Parsing from apk.
debug: Using local app from desired caps: C:\Users\awanw\Downloads\com.whatsapp-2.apk
info: Retrieving device
debug: Creating new appium session 252ca727-d549-4248-a1bf-298a32377674
debug: Using fast reset? false
debug: Preparing device for session
debug: Checking whether app is actually present
debug: Checking whether adb is present
debug: Using adb from C:\Users\awanw\Downloads\adt-bundle-windows-x86_64-20140702\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb.exe
debug: Trying to find a connected android device
debug: Getting connected devices…
debug: executing: “C:\Users\awanw\Downloads\adt-bundle-windows-x86_64-20140702\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb.exe” devices
debug: 1 device(s) connected
info: Found device 0e40b630
debug: Setting device id to 0e40b630
debug: Waiting for device to be ready and to respond to shell commands (timeout = 5)
debug: executing: “C:\Users\awanw\Downloads\adt-bundle-windows-x86_64-20140702\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb.exe” -s 0e40b630 wait-for-device
debug: executing: “C:\Users\awanw\Downloads\adt-bundle-windows-x86_64-20140702\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb.exe” -s 0e40b630 shell “echo ‘ready’”
debug: Starting logcat capture
debug: Parsing package and activity from app manifest
debug: Checking whether aapt is present
debug: Using aapt from C:\Users\awanw\Downloads\adt-bundle-windows-x86_64-20140702\adt-bundle-windows-x86_64-20140702\sdk\build-tools\19.1.0\aapt.exe
debug: packageAndLaunchActivityFromManifest: “C:\Users\awanw\Downloads\adt-bundle-windows-x86_64-20140702\adt-bundle-windows-x86_64-20140702\sdk\build-tools\19.1.0\aapt.exe” dump badging C:\Users\awanw\Downloads\com.whatsapp-2.apk
debug: badging package: com.whatsapp
debug: badging act: com.whatsapp.Main
debug: Parsed package and activity are: com.whatsapp/com.whatsapp.Main
debug: Getting device API level
debug: executing: “C:\Users\awanw\Downloads\adt-bundle-windows-x86_64-20140702\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb.exe” -s 0e40b630 shell “getprop ro.build.version.sdk”
debug: Device is at API Level 19
info: Device API level is: 19
debug: executing: “C:\Users\awanw\Downloads\adt-bundle-windows-x86_64-20140702\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb.exe” -s 0e40b630 shell “getprop persist.sys.language”
debug: Current device language: en
debug: java -jar “C:\Users\awanw\Desktop\Mobile Automation\Appium\node_modules\appium\node_modules\appium-adb\jars\strings_from_apk.jar” “C:\Users\awanw\Downloads\com.whatsapp-2.apk” “C:\Windows\Temp\com.whatsapp” en
debug: No strings.xml for language ‘en’, getting default strings.xml
debug: java -jar “C:\Users\awanw\Desktop\Mobile Automation\Appium\node_modules\appium\node_modules\appium-adb\jars\strings_from_apk.jar” “C:\Users\awanw\Downloads\com.whatsapp-2.apk” “C:\Windows\Temp\com.whatsapp”
debug: executing: “C:\Users\awanw\Downloads\adt-bundle-windows-x86_64-20140702\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb.exe” -s 0e40b630 push “C:\Windows\Temp\com.whatsapp\strings.json” /data/local/tmp
debug: Checking whether aapt is present
debug: Using aapt from C:\Users\awanw\Downloads\adt-bundle-windows-x86_64-20140702\adt-bundle-windows-x86_64-20140702\sdk\build-tools\19.1.0\aapt.exe
debug: processFromManifest: “C:\Users\awanw\Downloads\adt-bundle-windows-x86_64-20140702\adt-bundle-windows-x86_64-20140702\sdk\build-tools\19.1.0\aapt.exe” dump xmltree “C:\Users\awanw\Downloads\com.whatsapp-2.apk” AndroidManifest.xml
debug: Set app process to: com.whatsapp
debug: Not uninstalling app since server not started with --full-reset
debug: Checking app cert for C:\Users\awanw\Downloads\com.whatsapp-2.apk: java -jar “C:\Users\awanw\Desktop\Mobile Automation\Appium\node_modules\appium\node_modules\appium-adb\jars\verify.jar” “C:\Users\awanw\Downloads\com.whatsapp-2.apk”
debug: App already signed.
debug: Zip-aligning C:\Users\awanw\Downloads\com.whatsapp-2.apk
debug: Checking whether zipalign is present
debug: Using zipalign from C:\Users\awanw\Downloads\adt-bundle-windows-x86_64-20140702\adt-bundle-windows-x86_64-20140702\sdk\build-tools\19.1.0\zipalign.exe
debug: zipAlignApk: “C:\Users\awanw\Downloads\adt-bundle-windows-x86_64-20140702\adt-bundle-windows-x86_64-20140702\sdk\build-tools\19.1.0\zipalign.exe” -f 4 “C:\Users\awanw\Downloads\com.whatsapp-2.apk” “C:\Users\awanw\AppData\Local\Temp\appium1141015-6920-1vofzki.tmp”
debug: MD5 for app is ef5cbd229db7dcc8d5f84dfdfeb5505c
debug: executing: “C:\Users\awanw\Downloads\adt-bundle-windows-x86_64-20140702\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb.exe” -s 0e40b630 shell “ls /data/local/tmp/ef5cbd229db7dcc8d5f84dfdfeb5505c.apk”
debug: Getting install status for com.whatsapp
debug: executing: “C:\Users\awanw\Downloads\adt-bundle-windows-x86_64-20140702\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb.exe” -s 0e40b630 shell “pm list packages -3 com.whatsapp”
debug: App is installed
debug: Forwarding system:4724 to device:4724
debug: executing: “C:\Users\awanw\Downloads\adt-bundle-windows-x86_64-20140702\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb.exe” -s 0e40b630 forward tcp:4724 tcp:4724
debug: Pushing appium bootstrap to device…
debug: executing: “C:\Users\awanw\Downloads\adt-bundle-windows-x86_64-20140702\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb.exe” -s 0e40b630 push “C:\Users\awanw\Desktop\Mobile Automation\Appium\node_modules\appium\build\android_bootstrap\AppiumBootstrap.jar” /data/local/tmp/
debug: Pushing settings apk to device…
debug: executing: “C:\Users\awanw\Downloads\adt-bundle-windows-x86_64-20140702\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb.exe” -s 0e40b630 install “C:\Users\awanw\Desktop\Mobile Automation\Appium\node_modules\appium\build\settings_apk\settings_apk-debug.apk”
debug: Pushing unlock helper app to device…
debug: executing: “C:\Users\awanw\Downloads\adt-bundle-windows-x86_64-20140702\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb.exe” -s 0e40b630 install “C:\Users\awanw\Desktop\Mobile Automation\Appium\node_modules\appium\build\unlock_apk\unlock_apk-debug.apk”
info: Starting App
debug: Attempting to kill all ‘uiautomator’ processes
debug: Getting all processes with ‘uiautomator’
debug: executing: “C:\Users\awanw\Downloads\adt-bundle-windows-x86_64-20140702\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb.exe” -s 0e40b630 shell “ps ‘uiautomator’”
debug: No matching processes found
debug: Running bootstrap
debug: spawning: C:\Users\awanw\Downloads\adt-bundle-windows-x86_64-20140702\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb.exe -s 0e40b630 shell uiautomator runtest AppiumBootstrap.jar -c io.appium.android.bootstrap.Bootstrap
debug: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: numtests=1
debug: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: stream=
debug: [UIAUTOMATOR STDOUT] io.appium.android.bootstrap.Bootstrap:
debug: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: id=UiAutomatorTestRunner
debug: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: test=testRunServer
debug: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: class=io.appium.android.bootstrap.Bootstrap
debug: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: current=1
debug: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS_CODE: 1
debug: [BOOTSTRAP] [debug] Socket opened on port 4724
debug: [BOOTSTRAP] [debug] Appium Socket Server Ready
debug: [BOOTSTRAP] [debug] Loading json…
debug: Waking up device if it’s not alive
debug: Pushing command to appium work queue: [“wake”,{}]
debug: [BOOTSTRAP] [debug] json loading complete.
debug: [BOOTSTRAP] [debug] Registered crash watchers.
debug: [BOOTSTRAP] [debug] Client connected
debug: [BOOTSTRAP] [debug] Got data from client: {“cmd”:“action”,“action”:“wake”,“params”:{}}
debug: [BOOTSTRAP] [debug] Got command of type ACTION
debug: [BOOTSTRAP] [debug] Got command action: wake
debug: [BOOTSTRAP] [debug] Returning result: {“value”:true,“status”:0}
debug: executing: “C:\Users\awanw\Downloads\adt-bundle-windows-x86_64-20140702\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb.exe” -s 0e40b630 shell “dumpsys window”
debug: Writing dumpsys output to C:\Users\awanw\Desktop\Mobile Automation\Appium\node_modules\appium.dumpsys.log
debug: Screen already unlocked, continuing.
debug: Pushing command to appium work queue: [“getDataDir”,{}]
debug: [BOOTSTRAP] [debug] Got data from client: {“cmd”:“action”,“action”:“getDataDir”,“params”:{}}
debug: [BOOTSTRAP] [debug] Got command of type ACTION
debug: [BOOTSTRAP] [debug] Got command action: getDataDir
debug: [BOOTSTRAP] [debug] Returning result: {“value”:“/data/local/tmp”,“status”:0}
debug: dataDir set to: /data/local/tmp
debug: executing: “C:\Users\awanw\Downloads\adt-bundle-windows-x86_64-20140702\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb.exe” -s 0e40b630 shell “am start -S -a android.intent.action.MAIN -c android.intent.category.LAUNCHER -f 0x10200000 -n com.whatsapp/com.whatsapp.Main”
debug: Waiting for pkg “com.whatsapp” and activity “com.whatsapp.Main” to be focused
debug: Getting focused package and activity
debug: executing: “C:\Users\awanw\Downloads\adt-bundle-windows-x86_64-20140702\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb.exe” -s 0e40b630 shell “dumpsys window windows”
debug: Device launched! Ready for commands
info: ← POST /wd/hub/session 303 58800.695 ms - 9
debug: Setting command timeout to the default of 60 secs
debug: Appium session started with sessionId 252ca727-d549-4248-a1bf-298a32377674
info: → GET /wd/hub/session/252ca727-d549-4248-a1bf-298a32377674 {}
debug: Appium request initiated at /wd/hub/session/252ca727-d549-4248-a1bf-298a32377674
info: ← GET /wd/hub/session/252ca727-d549-4248-a1bf-298a32377674 200 3.230 ms - 512 {“status”:0,“value”:{“platform”:“LINUX”,“browserName”:“”,“platformVersion”:“4.4.2”,“webStorageEnabled”:false,“takesScreenshot”:true,“javascriptEnabled”:true,“databaseEnabled”:false,“warnings”:{},“desired”:{“app”:“C:\Users\awanw\Downloads\com.whatsapp-2.apk”,“platformVersion”:“4.4.2”,“browserName”:“”,“platformName”:“Android”,“deviceName”:“SM-N900V”},“app”:“C:\Users\awanw\Downloads\com.whatsapp-2.apk”,“platformName”:“Android”,“deviceName”:“SM-N900V”},“sessionId”:“252ca727-d549-4248-a1bf-298a32377674”}
debug: Request received with params: {}
debug: Responding to client with success: {“status”:0,“value”:{“platform”:“LINUX”,“browserName”:“”,“platformVersion”:“4.4.2”,“webStorageEnabled”:false,“takesScreenshot”:true,“javascriptEnabled”:true,“databaseEnabled”:false,“warnings”:{},“desired”:{“app”:“C:\Users\awanw\Downloads\com.whatsapp-2.apk”,“platformVersion”:“4.4.2”,“browserName”:“”,“platformName”:“Android”,“deviceName”:“SM-N900V”},“app”:“C:\Users\awanw\Downloads\com.whatsapp-2.apk”,“platformName”:“Android”,“deviceName”:“SM-N900V”},“sessionId”:“252ca727-d549-4248-a1bf-298a32377674”}
info: → POST /wd/hub/session/252ca727-d549-4248-a1bf-298a32377674/timeouts/implicit_wait {“ms”:10000}
debug: Appium request initiated at /wd/hub/session/252ca727-d549-4248-a1bf-298a32377674/timeouts/implicit_wait
debug: Request received with params: {“ms”:10000}
info: ← POST /wd/hub/session/252ca727-d549-4248-a1bf-298a32377674/timeouts/implicit_wait 200 1.897 ms - 76 {“status”:0,“value”:null,“sessionId”:“252ca727-d549-4248-a1bf-298a32377674”}
debug: Set Android implicit wait to 10000ms
debug: Responding to client with success: {“status”:0,“value”:null,“sessionId”:“252ca727-d549-4248-a1bf-298a32377674”}
Killed Node Server.
Node Server Process Ended
Starting Node Server
info: Welcome to Appium v1.2.0 (REV e53f49c706a25242e66d36685c268b599cc18da5)
debug: Non-default server args: {“address”:“127.0.0.1”,“noReset”:true,“logNoColors”:true,“platformName”:“Android”,“platformVersion”:“18”,“automationName”:“Appium”}
info: Appium REST http interface listener started on 127.0.0.1:4723
info: LogLevel: debug
info: → POST /wd/hub/session {“desiredCapabilities”:{“app”:“C:\Users\awanw\Downloads\com.whatsapp-2.apk”,“platformVersion”:“4.4.2”,“browserName”:“”,“platformName”:“Android”,“deviceName”:“SM-N900V”}}
debug: Appium request initiated at /wd/hub/session
debug: Request received with params: {“desiredCapabilities”:{“app”:“C:\Users\awanw\Downloads\com.whatsapp-2.apk”,“platformVersion”:“4.4.2”,“browserName”:“”,“platformName”:“Android”,“deviceName”:“SM-N900V”}}
info: Starting android appium
debug: No appActivity desired capability or server param. Parsing from apk.
info: Retrieving device
debug: No appPackage desired capability or server param. Parsing from apk.
debug: Using local app from desired caps: C:\Users\awanw\Downloads\com.whatsapp-2.apk
debug: Creating new appium session 5f297b70-d90d-421a-8f98-b3a0a865d03b
debug: Using fast reset? false
debug: Preparing device for session
debug: Checking whether app is actually present
debug: Checking whether adb is present
debug: Using adb from C:\Users\awanw\Downloads\adt-bundle-windows-x86_64-20140702\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb.exe
debug: Trying to find a connected android device
debug: Getting connected devices…
debug: executing: “C:\Users\awanw\Downloads\adt-bundle-windows-x86_64-20140702\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb.exe” devices
debug: 1 device(s) connected
info: Found device 0e40b630
debug: Setting device id to 0e40b630
debug: Waiting for device to be ready and to respond to shell commands (timeout = 5)
debug: executing: “C:\Users\awanw\Downloads\adt-bundle-windows-x86_64-20140702\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb.exe” -s 0e40b630 wait-for-device
debug: executing: “C:\Users\awanw\Downloads\adt-bundle-windows-x86_64-20140702\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb.exe” -s 0e40b630 shell “echo ‘ready’”
debug: Starting logcat capture
debug: Parsing package and activity from app manifest
debug: Checking whether aapt is present
debug: Using aapt from C:\Users\awanw\Downloads\adt-bundle-windows-x86_64-20140702\adt-bundle-windows-x86_64-20140702\sdk\build-tools\19.1.0\aapt.exe
debug: packageAndLaunchActivityFromManifest: “C:\Users\awanw\Downloads\adt-bundle-windows-x86_64-20140702\adt-bundle-windows-x86_64-20140702\sdk\build-tools\19.1.0\aapt.exe” dump badging C:\Users\awanw\Downloads\com.whatsapp-2.apk
debug: badging package: com.whatsapp
debug: badging act: com.whatsapp.Main
debug: Parsed package and activity are: com.whatsapp/com.whatsapp.Main
debug: Getting device API level
debug: executing: “C:\Users\awanw\Downloads\adt-bundle-windows-x86_64-20140702\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb.exe” -s 0e40b630 shell “getprop ro.build.version.sdk”
debug: Device is at API Level 19
info: Device API level is: 19
debug: executing: “C:\Users\awanw\Downloads\adt-bundle-windows-x86_64-20140702\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb.exe” -s 0e40b630 shell “getprop persist.sys.language”
debug: Current device language: en
debug: java -jar “C:\Users\awanw\Desktop\Mobile Automation\Appium\node_modules\appium\node_modules\appium-adb\jars\strings_from_apk.jar” “C:\Users\awanw\Downloads\com.whatsapp-2.apk” “C:\Windows\Temp\com.whatsapp” en
debug: No strings.xml for language ‘en’, getting default strings.xml
debug: java -jar “C:\Users\awanw\Desktop\Mobile Automation\Appium\node_modules\appium\node_modules\appium-adb\jars\strings_from_apk.jar” “C:\Users\awanw\Downloads\com.whatsapp-2.apk” “C:\Windows\Temp\com.whatsapp”
debug: executing: “C:\Users\awanw\Downloads\adt-bundle-windows-x86_64-20140702\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb.exe” -s 0e40b630 push “C:\Windows\Temp\com.whatsapp\strings.json” /data/local/tmp
debug: Checking whether aapt is present
debug: Using aapt from C:\Users\awanw\Downloads\adt-bundle-windows-x86_64-20140702\adt-bundle-windows-x86_64-20140702\sdk\build-tools\19.1.0\aapt.exe
debug: processFromManifest: “C:\Users\awanw\Downloads\adt-bundle-windows-x86_64-20140702\adt-bundle-windows-x86_64-20140702\sdk\build-tools\19.1.0\aapt.exe” dump xmltree “C:\Users\awanw\Downloads\com.whatsapp-2.apk” AndroidManifest.xml
debug: Set app process to: com.whatsapp
debug: Not uninstalling app since server not started with --full-reset
debug: Checking app cert for C:\Users\awanw\Downloads\com.whatsapp-2.apk: java -jar “C:\Users\awanw\Desktop\Mobile Automation\Appium\node_modules\appium\node_modules\appium-adb\jars\verify.jar” “C:\Users\awanw\Downloads\com.whatsapp-2.apk”
debug: App already signed.
debug: Zip-aligning C:\Users\awanw\Downloads\com.whatsapp-2.apk
debug: Checking whether zipalign is present
debug: Using zipalign from C:\Users\awanw\Downloads\adt-bundle-windows-x86_64-20140702\adt-bundle-windows-x86_64-20140702\sdk\build-tools\19.1.0\zipalign.exe
debug: zipAlignApk: “C:\Users\awanw\Downloads\adt-bundle-windows-x86_64-20140702\adt-bundle-windows-x86_64-20140702\sdk\build-tools\19.1.0\zipalign.exe” -f 4 “C:\Users\awanw\Downloads\com.whatsapp-2.apk” “C:\Users\awanw\AppData\Local\Temp\appium1141015-5136-18bygrj.tmp”
debug: MD5 for app is ef5cbd229db7dcc8d5f84dfdfeb5505c
debug: executing: “C:\Users\awanw\Downloads\adt-bundle-windows-x86_64-20140702\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb.exe” -s 0e40b630 shell “ls /data/local/tmp/ef5cbd229db7dcc8d5f84dfdfeb5505c.apk”
debug: Getting install status for com.whatsapp
debug: executing: “C:\Users\awanw\Downloads\adt-bundle-windows-x86_64-20140702\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb.exe” -s 0e40b630 shell “pm list packages -3 com.whatsapp”
debug: App is installed
debug: Forwarding system:4724 to device:4724
debug: executing: “C:\Users\awanw\Downloads\adt-bundle-windows-x86_64-20140702\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb.exe” -s 0e40b630 forward tcp:4724 tcp:4724
debug: Pushing appium bootstrap to device…
debug: executing: “C:\Users\awanw\Downloads\adt-bundle-windows-x86_64-20140702\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb.exe” -s 0e40b630 push “C:\Users\awanw\Desktop\Mobile Automation\Appium\node_modules\appium\build\android_bootstrap\AppiumBootstrap.jar” /data/local/tmp/
debug: Pushing settings apk to device…
debug: executing: “C:\Users\awanw\Downloads\adt-bundle-windows-x86_64-20140702\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb.exe” -s 0e40b630 install “C:\Users\awanw\Desktop\Mobile Automation\Appium\node_modules\appium\build\settings_apk\settings_apk-debug.apk”
debug: Pushing unlock helper app to device…
debug: executing: “C:\Users\awanw\Downloads\adt-bundle-windows-x86_64-20140702\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb.exe” -s 0e40b630 install “C:\Users\awanw\Desktop\Mobile Automation\Appium\node_modules\appium\build\unlock_apk\unlock_apk-debug.apk”
info: Starting App
debug: Attempting to kill all ‘uiautomator’ processes
debug: Getting all processes with ‘uiautomator’
debug: executing: “C:\Users\awanw\Downloads\adt-bundle-windows-x86_64-20140702\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb.exe” -s 0e40b630 shell “ps ‘uiautomator’”
debug: No matching processes found
debug: Running bootstrap
debug: spawning: C:\Users\awanw\Downloads\adt-bundle-windows-x86_64-20140702\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb.exe -s 0e40b630 shell uiautomator runtest AppiumBootstrap.jar -c io.appium.android.bootstrap.Bootstrap
debug: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: numtests=1
debug: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: stream=
debug: [UIAUTOMATOR STDOUT] io.appium.android.bootstrap.Bootstrap:
debug: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: id=UiAutomatorTestRunner
debug: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: test=testRunServer
debug: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: class=io.appium.android.bootstrap.Bootstrap
debug: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: current=1
debug: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS_CODE: 1
debug: [BOOTSTRAP] [debug] Socket opened on port 4724
debug: [BOOTSTRAP] [debug] Appium Socket Server Ready
debug: [BOOTSTRAP] [debug] Loading json…
debug: Waking up device if it’s not alive
debug: Pushing command to appium work queue: [“wake”,{}]
debug: [BOOTSTRAP] [debug] json loading complete.
debug: [BOOTSTRAP] [debug] Registered crash watchers.
debug: [BOOTSTRAP] [debug] Client connected
debug: [BOOTSTRAP] [debug] Got data from client: {“cmd”:“action”,“action”:“wake”,“params”:{}}
debug: [BOOTSTRAP] [debug] Got command of type ACTION
debug: [BOOTSTRAP] [debug] Got command action: wake
debug: [BOOTSTRAP] [debug] Returning result: {“value”:true,“status”:0}
debug: executing: “C:\Users\awanw\Downloads\adt-bundle-windows-x86_64-20140702\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb.exe” -s 0e40b630 shell “dumpsys window”
debug: Writing dumpsys output to C:\Users\awanw\Desktop\Mobile Automation\Appium\node_modules\appium.dumpsys.log
debug: Screen already unlocked, continuing.
debug: Pushing command to appium work queue: [“getDataDir”,{}]
debug: [BOOTSTRAP] [debug] Got data from client: {“cmd”:“action”,“action”:“getDataDir”,“params”:{}}
debug: [BOOTSTRAP] [debug] Got command of type ACTION
debug: [BOOTSTRAP] [debug] Got command action: getDataDir
debug: [BOOTSTRAP] [debug] Returning result: {“value”:“/data/local/tmp”,“status”:0}
debug: dataDir set to: /data/local/tmp
debug: executing: “C:\Users\awanw\Downloads\adt-bundle-windows-x86_64-20140702\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb.exe” -s 0e40b630 shell “am start -S -a android.intent.action.MAIN -c android.intent.category.LAUNCHER -f 0x10200000 -n com.whatsapp/com.whatsapp.Main”
debug: Waiting for pkg “com.whatsapp” and activity “com.whatsapp.Main” to be focused
debug: Getting focused package and activity
debug: executing: “C:\Users\awanw\Downloads\adt-bundle-windows-x86_64-20140702\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb.exe” -s 0e40b630 shell “dumpsys window windows”
debug: Device launched! Ready for commands
info: ← POST /wd/hub/session 303 66591.044 ms - 9
debug: Setting command timeout to the default of 60 secs
debug: Appium session started with sessionId 5f297b70-d90d-421a-8f98-b3a0a865d03b
info: → GET /wd/hub/session/5f297b70-d90d-421a-8f98-b3a0a865d03b {}
debug: Appium request initiated at /wd/hub/session/5f297b70-d90d-421a-8f98-b3a0a865d03b
debug: Request received with params: {}
debug: Responding to client with success: {“status”:0,“value”:{“platform”:“LINUX”,“browserName”:“”,“platformVersion”:“4.4.2”,“webStorageEnabled”:false,“takesScreenshot”:true,“javascriptEnabled”:true,“databaseEnabled”:false,“warnings”:{},“desired”:{“app”:“C:\Users\awanw\Downloads\com.whatsapp-2.apk”,“platformVersion”:“4.4.2”,“browserName”:“”,“platformName”:“Android”,“deviceName”:“SM-N900V”},“app”:“C:\Users\awanw\Downloads\com.whatsapp-2.apk”,“platformName”:“Android”,“deviceName”:“SM-N900V”},“sessionId”:“5f297b70-d90d-421a-8f98-b3a0a865d03b”}
info: ← GET /wd/hub/session/5f297b70-d90d-421a-8f98-b3a0a865d03b 200 2.191 ms - 512 {“status”:0,“value”:{“platform”:“LINUX”,“browserName”:“”,“platformVersion”:“4.4.2”,“webStorageEnabled”:false,“takesScreenshot”:true,“javascriptEnabled”:true,“databaseEnabled”:false,“warnings”:{},“desired”:{“app”:“C:\Users\awanw\Downloads\com.whatsapp-2.apk”,“platformVersion”:“4.4.2”,“browserName”:“”,“platformName”:“Android”,“deviceName”:“SM-N900V”},“app”:“C:\Users\awanw\Downloads\com.whatsapp-2.apk”,“platformName”:“Android”,“deviceName”:“SM-N900V”},“sessionId”:“5f297b70-d90d-421a-8f98-b3a0a865d03b”}
info: → POST /wd/hub/session/5f297b70-d90d-421a-8f98-b3a0a865d03b/timeouts/implicit_wait {“ms”:10000}
debug: Appium request initiated at /wd/hub/session/5f297b70-d90d-421a-8f98-b3a0a865d03b/timeouts/implicit_wait
info: ← POST /wd/hub/session/5f297b70-d90d-421a-8f98-b3a0a865d03b/timeouts/implicit_wait 200 1.984 ms - 76 {“status”:0,“value”:null,“sessionId”:“5f297b70-d90d-421a-8f98-b3a0a865d03b”}
debug: Request received with params: {“ms”:10000}
debug: Set Android implicit wait to 10000ms
debug: Responding to client with success: {“status”:0,“value”:null,“sessionId”:“5f297b70-d90d-421a-8f98-b3a0a865d03b”}
debug: Didn’t get a new command in 60 secs, shutting down…
info: Shutting down appium session
debug: Pressing the HOME button
debug: executing: “C:\Users\awanw\Downloads\adt-bundle-windows-x86_64-20140702\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb.exe” -s 0e40b630 shell “input keyevent 3”
debug: Stopping logcat capture
debug: Logcat terminated with code null, signal SIGTERM
debug: [BOOTSTRAP] [debug] Got data from client: {“cmd”:“shutdown”}
debug: [BOOTSTRAP] [debug] Got command of type SHUTDOWN
debug: [BOOTSTRAP] [debug] Returning result: {“value”:“OK, shutting down”,“status”:0}
debug: [BOOTSTRAP] [debug] Closed client connection
debug: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: numtests=1
debug: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: stream=.
debug: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: id=UiAutomatorTestRunner
debug: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: test=testRunServer
debug: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: class=io.appium.android.bootstrap.Bootstrap
debug: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: current=1
debug: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS_CODE: 0
debug: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: stream=
debug: [UIAUTOMATOR STDOUT] Test results for WatcherResultPrinter=.
debug: [UIAUTOMATOR STDOUT] Time: 62.776
debug: [UIAUTOMATOR STDOUT] OK (1 test)
debug: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS_CODE: -1
debug: Sent shutdown command, waiting for UiAutomator to stop…
debug: UiAutomator shut down normally
debug: Cleaning up android objects
debug: Cleaning up appium session
debug: We shut down because no new commands came in
Killed Node Server.
Node Server Process Ended
Starting Node Server
info: Welcome to Appium v1.2.0 (REV e53f49c706a25242e66d36685c268b599cc18da5)
debug: Non-default server args: {“address”:“127.0.0.1”,“noReset”:true,“logNoColors”:true,“platformName”:“Android”,“platformVersion”:“18”,“automationName”:“Appium”}
info: Appium REST http interface listener started on 127.0.0.1:4723
info: LogLevel: debug
info: → POST /wd/hub/session {“desiredCapabilities”:{“app”:“C:\Users\awanw\Downloads\com.dominospizza.apk”,“platformVersion”:“4.4.2”,“browserName”:“”,“platformName”:“Android”,“deviceName”:“SM-N900V”}}
debug: Appium request initiated at /wd/hub/session
debug: Request received with params: {“desiredCapabilities”:{“app”:“C:\Users\awanw\Downloads\com.dominospizza.apk”,“platformVersion”:“4.4.2”,“browserName”:“”,“platformName”:“Android”,“deviceName”:“SM-N900V”}}
info: Starting android appium
debug: No appActivity desired capability or server param. Parsing from apk.
info: Retrieving device
debug: No appPackage desired capability or server param. Parsing from apk.
debug: Using local app from desired caps: C:\Users\awanw\Downloads\com.dominospizza.apk
debug: Creating new appium session cb237329-7129-402a-95f5-e998dbf05c2f
debug: Using fast reset? false
debug: Preparing device for session
debug: Checking whether app is actually present
debug: Checking whether adb is present
debug: Using adb from C:\Users\awanw\Downloads\adt-bundle-windows-x86_64-20140702\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb.exe
debug: Trying to find a connected android device
debug: Getting connected devices…
debug: executing: “C:\Users\awanw\Downloads\adt-bundle-windows-x86_64-20140702\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb.exe” devices
debug: 1 device(s) connected
info: Found device 0e40b630
debug: Setting device id to 0e40b630
debug: Waiting for device to be ready and to respond to shell commands (timeout = 5)
debug: executing: “C:\Users\awanw\Downloads\adt-bundle-windows-x86_64-20140702\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb.exe” -s 0e40b630 wait-for-device
debug: executing: “C:\Users\awanw\Downloads\adt-bundle-windows-x86_64-20140702\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb.exe” -s 0e40b630 shell “echo ‘ready’”
debug: Starting logcat capture
debug: Parsing package and activity from app manifest
debug: Checking whether aapt is present
debug: Using aapt from C:\Users\awanw\Downloads\adt-bundle-windows-x86_64-20140702\adt-bundle-windows-x86_64-20140702\sdk\build-tools\19.1.0\aapt.exe
debug: packageAndLaunchActivityFromManifest: “C:\Users\awanw\Downloads\adt-bundle-windows-x86_64-20140702\adt-bundle-windows-x86_64-20140702\sdk\build-tools\19.1.0\aapt.exe” dump badging C:\Users\awanw\Downloads\com.dominospizza.apk
debug: badging package: com.dominospizza
debug: badging act: com.dominospizza.activities.InitialLaunchActivity
debug: Parsed package and activity are: com.dominospizza/com.dominospizza.activities.InitialLaunchActivity
debug: Getting device API level
debug: executing: “C:\Users\awanw\Downloads\adt-bundle-windows-x86_64-20140702\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb.exe” -s 0e40b630 shell “getprop ro.build.version.sdk”
debug: Device is at API Level 19
info: Device API level is: 19
debug: executing: “C:\Users\awanw\Downloads\adt-bundle-windows-x86_64-20140702\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb.exe” -s 0e40b630 shell “getprop persist.sys.language”
debug: Current device language: en
debug: java -jar “C:\Users\awanw\Desktop\Mobile Automation\Appium\node_modules\appium\node_modules\appium-adb\jars\strings_from_apk.jar” “C:\Users\awanw\Downloads\com.dominospizza.apk” “C:\Windows\Temp\com.dominospizza” en
debug: No strings.xml for language ‘en’, getting default strings.xml
debug: java -jar “C:\Users\awanw\Desktop\Mobile Automation\Appium\node_modules\appium\node_modules\appium-adb\jars\strings_from_apk.jar” “C:\Users\awanw\Downloads\com.dominospizza.apk” “C:\Windows\Temp\com.dominospizza”
debug: executing: “C:\Users\awanw\Downloads\adt-bundle-windows-x86_64-20140702\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb.exe” -s 0e40b630 push “C:\Windows\Temp\com.dominospizza\strings.json” /data/local/tmp
debug: Checking whether aapt is present
debug: Using aapt from C:\Users\awanw\Downloads\adt-bundle-windows-x86_64-20140702\adt-bundle-windows-x86_64-20140702\sdk\build-tools\19.1.0\aapt.exe
debug: processFromManifest: “C:\Users\awanw\Downloads\adt-bundle-windows-x86_64-20140702\adt-bundle-windows-x86_64-20140702\sdk\build-tools\19.1.0\aapt.exe” dump xmltree “C:\Users\awanw\Downloads\com.dominospizza.apk” AndroidManifest.xml
debug: Set app process to: com.dominospizza
debug: Not uninstalling app since server not started with --full-reset
debug: Checking app cert for C:\Users\awanw\Downloads\com.dominospizza.apk: java -jar “C:\Users\awanw\Desktop\Mobile Automation\Appium\node_modules\appium\node_modules\appium-adb\jars\verify.jar” “C:\Users\awanw\Downloads\com.dominospizza.apk”
debug: App already signed.
debug: Zip-aligning C:\Users\awanw\Downloads\com.dominospizza.apk
debug: Checking whether zipalign is present
debug: Using zipalign from C:\Users\awanw\Downloads\adt-bundle-windows-x86_64-20140702\adt-bundle-windows-x86_64-20140702\sdk\build-tools\19.1.0\zipalign.exe
debug: zipAlignApk: “C:\Users\awanw\Downloads\adt-bundle-windows-x86_64-20140702\adt-bundle-windows-x86_64-20140702\sdk\build-tools\19.1.0\zipalign.exe” -f 4 “C:\Users\awanw\Downloads\com.dominospizza.apk” “C:\Users\awanw\AppData\Local\Temp\appium1141015-6708-j9wn11.tmp”
debug: MD5 for app is a4e530a3d2957385874cacc5ccce7801
debug: executing: “C:\Users\awanw\Downloads\adt-bundle-windows-x86_64-20140702\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb.exe” -s 0e40b630 shell “ls /data/local/tmp/a4e530a3d2957385874cacc5ccce7801.apk”
debug: Getting install status for com.dominospizza
debug: executing: “C:\Users\awanw\Downloads\adt-bundle-windows-x86_64-20140702\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb.exe” -s 0e40b630 shell “pm list packages -3 com.dominospizza”
debug: App is installed
debug: Forwarding system:4724 to device:4724
debug: executing: “C:\Users\awanw\Downloads\adt-bundle-windows-x86_64-20140702\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb.exe” -s 0e40b630 forward tcp:4724 tcp:4724
debug: Pushing appium bootstrap to device…
debug: executing: “C:\Users\awanw\Downloads\adt-bundle-windows-x86_64-20140702\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb.exe” -s 0e40b630 push “C:\Users\awanw\Desktop\Mobile Automation\Appium\node_modules\appium\build\android_bootstrap\AppiumBootstrap.jar” /data/local/tmp/
debug: Pushing settings apk to device…
debug: executing: “C:\Users\awanw\Downloads\adt-bundle-windows-x86_64-20140702\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb.exe” -s 0e40b630 install “C:\Users\awanw\Desktop\Mobile Automation\Appium\node_modules\appium\build\settings_apk\settings_apk-debug.apk”
debug: Pushing unlock helper app to device…
debug: executing: “C:\Users\awanw\Downloads\adt-bundle-windows-x86_64-20140702\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb.exe” -s 0e40b630 install “C:\Users\awanw\Desktop\Mobile Automation\Appium\node_modules\appium\build\unlock_apk\unlock_apk-debug.apk”
info: Starting App
debug: Attempting to kill all ‘uiautomator’ processes
debug: Getting all processes with ‘uiautomator’
debug: executing: “C:\Users\awanw\Downloads\adt-bundle-windows-x86_64-20140702\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb.exe” -s 0e40b630 shell “ps ‘uiautomator’”
debug: No matching processes found
debug: Running bootstrap
debug: spawning: C:\Users\awanw\Downloads\adt-bundle-windows-x86_64-20140702\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb.exe -s 0e40b630 shell uiautomator runtest AppiumBootstrap.jar -c io.appium.android.bootstrap.Bootstrap
debug: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: numtests=1
debug: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: stream=
debug: [UIAUTOMATOR STDOUT] io.appium.android.bootstrap.Bootstrap:
debug: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: id=UiAutomatorTestRunner
debug: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: test=testRunServer
debug: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: class=io.appium.android.bootstrap.Bootstrap
debug: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: current=1
debug: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS_CODE: 1
debug: [BOOTSTRAP] [debug] Socket opened on port 4724
debug: [BOOTSTRAP] [debug] Appium Socket Server Ready
debug: [BOOTSTRAP] [debug] Loading json…
debug: Waking up device if it’s not alive
debug: Pushing command to appium work queue: [“wake”,{}]
debug: [BOOTSTRAP] [debug] json loading complete.
debug: [BOOTSTRAP] [debug] Registered crash watchers.
debug: [BOOTSTRAP] [debug] Client connected
debug: [BOOTSTRAP] [debug] Got data from client: {“cmd”:“action”,“action”:“wake”,“params”:{}}
debug: [BOOTSTRAP] [debug] Got command of type ACTION
debug: [BOOTSTRAP] [debug] Got command action: wake
debug: [BOOTSTRAP] [debug] Returning result: {“value”:true,“status”:0}
debug: executing: “C:\Users\awanw\Downloads\adt-bundle-windows-x86_64-20140702\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb.exe” -s 0e40b630 shell “dumpsys window”
debug: Writing dumpsys output to C:\Users\awanw\Desktop\Mobile Automation\Appium\node_modules\appium.dumpsys.log
debug: Screen already unlocked, continuing.
debug: Pushing command to appium work queue: [“getDataDir”,{}]
debug: [BOOTSTRAP] [debug] Got data from client: {“cmd”:“action”,“action”:“getDataDir”,“params”:{}}
debug: [BOOTSTRAP] [debug] Got command of type ACTION
debug: [BOOTSTRAP] [debug] Got command action: getDataDir
debug: [BOOTSTRAP] [debug] Returning result: {“value”:“/data/local/tmp”,“status”:0}
debug: dataDir set to: /data/local/tmp
debug: executing: “C:\Users\awanw\Downloads\adt-bundle-windows-x86_64-20140702\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb.exe” -s 0e40b630 shell “am start -S -a android.intent.action.MAIN -c android.intent.category.LAUNCHER -f 0x10200000 -n com.dominospizza/com.dominospizza.activities.InitialLaunchActivity”
debug: Waiting for pkg “com.dominospizza” and activity “com.dominospizza.activities.InitialLaunchActivity” to be focused
debug: Getting focused package and activity
debug: executing: “C:\Users\awanw\Downloads\adt-bundle-windows-x86_64-20140702\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb.exe” -s 0e40b630 shell “dumpsys window windows”
debug: Getting focused package and activity
debug: executing: “C:\Users\awanw\Downloads\adt-bundle-windows-x86_64-20140702\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb.exe” -s 0e40b630 shell “dumpsys window windows”
debug: Getting focused package and activity
debug: executing: “C:\Users\awanw\Downloads\adt-bundle-windows-x86_64-20140702\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb.exe” -s 0e40b630 shell “dumpsys window windows”
debug: Getting focused package and activity
debug: executing: “C:\Users\awanw\Downloads\adt-bundle-windows-x86_64-20140702\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb.exe” -s 0e40b630 shell “dumpsys window windows”
debug: Getting focused package and activity
debug: executing: “C:\Users\awanw\Downloads\adt-bundle-windows-x86_64-20140702\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb.exe” -s 0e40b630 shell “dumpsys window windows”
debug: Getting focused package and activity
debug: executing: “C:\Users\awanw\Downloads\adt-bundle-windows-x86_64-20140702\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb.exe” -s 0e40b630 shell “dumpsys window windows”
debug: Getting focused package and activity
debug: executing: “C:\Users\awanw\Downloads\adt-bundle-windows-x86_64-20140702\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb.exe” -s 0e40b630 shell “dumpsys window windows”
debug: Getting focused package and activity
debug: executing: “C:\Users\awanw\Downloads\adt-bundle-windows-x86_64-20140702\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb.exe” -s 0e40b630 shell “dumpsys window windows”
debug: Getting focused package and activity
debug: executing: “C:\Users\awanw\Downloads\adt-bundle-windows-x86_64-20140702\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb.exe” -s 0e40b630 shell “dumpsys window windows”
debug: Getting focused package and activity
debug: executing: “C:\Users\awanw\Downloads\adt-bundle-windows-x86_64-20140702\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb.exe” -s 0e40b630 shell “dumpsys window windows”
debug: Getting focused package and activity
debug: executing: “C:\Users\awanw\Downloads\adt-bundle-windows-x86_64-20140702\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb.exe” -s 0e40b630 shell “dumpsys window windows”
debug: Getting focused package and activity
debug: executing: “C:\Users\awanw\Downloads\adt-bundle-windows-x86_64-20140702\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb.exe” -s 0e40b630 shell “dumpsys window windows”
debug: Getting focused package and activity
debug: executing: “C:\Users\awanw\Downloads\adt-bundle-windows-x86_64-20140702\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb.exe” -s 0e40b630 shell “dumpsys window windows”
debug: Getting focused package and activity
debug: executing: “C:\Users\awanw\Downloads\adt-bundle-windows-x86_64-20140702\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb.exe” -s 0e40b630 shell “dumpsys window windows”
debug: Getting focused package and activity
debug: executing: “C:\Users\awanw\Downloads\adt-bundle-windows-x86_64-20140702\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb.exe” -s 0e40b630 shell “dumpsys window windows”
debug: Getting focused package and activity
debug: executing: “C:\Users\awanw\Downloads\adt-bundle-windows-x86_64-20140702\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb.exe” -s 0e40b630 shell “dumpsys window windows”
debug: Getting focused package and activity
debug: executing: “C:\Users\awanw\Downloads\adt-bundle-windows-x86_64-20140702\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb.exe” -s 0e40b630 shell “dumpsys window windows”
debug: Getting focused package and activity
debug: executing: “C:\Users\awanw\Downloads\adt-bundle-windows-x86_64-20140702\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb.exe” -s 0e40b630 shell “dumpsys window windows”
debug: Getting focused package and activity
debug: executing: “C:\Users\awanw\Downloads\adt-bundle-windows-x86_64-20140702\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb.exe” -s 0e40b630 shell “dumpsys window windows”
debug: Getting focused package and activity
debug: executing: “C:\Users\awanw\Downloads\adt-bundle-windows-x86_64-20140702\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb.exe” -s 0e40b630 shell “dumpsys window windows”
debug: Getting focused package and activity
debug: executing: “C:\Users\awanw\Downloads\adt-bundle-windows-x86_64-20140702\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb.exe” -s 0e40b630 shell “dumpsys window windows”
debug: Getting focused package and activity
debug: executing: “C:\Users\awanw\Downloads\adt-bundle-windows-x86_64-20140702\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb.exe” -s 0e40b630 shell “dumpsys window windows”
error: com.dominospizza/.activities.InitialLaunchActivity never started. Current: com.dominospizza/com.dominos.activities.LandingActivity_
debug: Stopping logcat capture
debug: Logcat terminated with code null, signal SIGTERM
debug: [BOOTSTRAP] [debug] Got data from client: {“cmd”:“shutdown”}
debug: [BOOTSTRAP] [debug] Got command of type SHUTDOWN
debug: [BOOTSTRAP] [debug] Returning result: {“value”:“OK, shutting down”,“status”:0}
debug: [BOOTSTRAP] [debug] Closed client connection
debug: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: numtests=1
debug: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: stream=.
debug: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: id=UiAutomatorTestRunner
debug: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: test=testRunServer
debug: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: class=io.appium.android.bootstrap.Bootstrap
debug: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: current=1
debug: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS_CODE: 0
debug: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: stream=
debug: [UIAUTOMATOR STDOUT] Test results for WatcherResultPrinter=.
debug: [UIAUTOMATOR STDOUT] Time: 21.814
debug: [UIAUTOMATOR STDOUT] OK (1 test)
debug: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS_CODE: -1
debug: Sent shutdown command, waiting for UiAutomator to stop…
debug: UiAutomator shut down normally
debug: Cleaning up android objects
debug: Cleaning up appium session
error: Failed to start an Appium session, err was: Error: com.dominospizza/.activities.InitialLaunchActivity never started. Current: com.dominospizza/com.dominos.activities.LandingActivity_
debug: Error: com.dominospizza/.activities.InitialLaunchActivity never started. Current: com.dominospizza/com.dominos.activities.LandingActivity_
at null. (C:\Users\awanw\Desktop\Mobile Automation\Appium\node_modules\appium\node_modules\appium-adb\lib\adb.js:1273:12)
at null. (C:\Users\awanw\Desktop\Mobile Automation\Appium\node_modules\appium\node_modules\appium-adb\lib\adb.js:1218:7)
at C:\Users\awanw\Desktop\Mobile Automation\Appium\node_modules\appium\node_modules\appium-adb\lib\adb.js:162:5
at ChildProcess.exithandler (child_process.js:635:7)
at ChildProcess.EventEmitter.emit (events.js:98:17)
at maybeClose (child_process.js:743:16)
at Process.ChildProcess.handle.onexit (child_process.js:810:5)
debug: Responding to client with error: {“status”:33,“value”:{“message”:"A new session could not be created. (Original error: com.dominospizza/.activities.InitialLaunchActivity never started. Current: com.dominospizza/com.dominos.activities.LandingActivity)",“origValue”:“com.dominospizza/.activities.InitialLaunchActivity never started. Current: com.dominospizza/com.dominos.activities.LandingActivity_”},“sessionId”:null}

Using below code

import io.appium.java_client.AppiumDriver;

//import io.appium.java_client.android.AndroidDriver;
import java.io.File;
import java.net.MalformedURLException;
import java.net.URL;
import java.util.concurrent.TimeUnit;

import org.openqa.selenium.By;
import org.openqa.selenium.WebDriver;
import org.openqa.selenium.WebElement;
import org.openqa.selenium.remote.CapabilityType;
import org.openqa.selenium.remote.DesiredCapabilities;
import org.testng.annotations.AfterTest;
import org.testng.annotations.Test;

public class DominosApp {
static WebDriver dr;

@Test
public static void main(String arg) throws MalformedURLException, InterruptedException{
String contact=“1jyot”;
File app = new File (“C:\Users\awanw\Downloads\com.dominospizza.apk”);
DesiredCapabilities capabilities = new DesiredCapabilities();
capabilities.setCapability(CapabilityType.BROWSER_NAME, “”);
capabilities.setCapability(“deviceName”,“SM-N900V”);
capabilities.setCapability(“platformVersion”,“4.4.2”);
capabilities.setCapability(“platformName”,“Android”);
capabilities.setCapability(“app”, app.getAbsolutePath());

			//capabilities.setCapability("appPackage","com.dominospizza");
			//capabilities.setCapability("appActivity","com.dominospizza.activities.InitialLaunchActivity");
			                                         
			dr=new AppiumDriver(new URL("http://127.0.0.1:4723/wd/hub"), capabilities);
			dr.manage().timeouts().implicitlyWait(5, TimeUnit.SECONDS);
			Thread.sleep(5000);
			dr.findElement(By.id("com.dominospizza:id/deliveryButton")).click();	
			
		}
@AfterTest
public void quit(){
	dr.quit();

}

	 }

Dyktus · November 27, 2014, 2:24pm

+1 for this issue

I have the same issue but with chrome browser on real device (Android 4.4.2), when I run appium on Windows and Mac. Two days ago everything was fine .

@jonahss or someone do You have any advice for it ?
It is random. I worked two weeks without problems, and now it happened again.

jonahss · January 5, 2015, 7:58pm

Hmmmmm, my gut-feeling here is it might be general Android and ADB flakiness. If you look at the code we use to detect whether or not the activity starts (adb.js), it could yield a better answer. Perhaps you could just tweak the timeout to give your app more time to start.

wajahat5139 · January 8, 2015, 2:08am

Doesn’t make any difference. Giving more time or not still does the same.
Before app fully display the landing page it displays another page before the landing page. Do you guys think that could be the issue?

sdubov · January 9, 2015, 8:12am

I had the same issue. Found a solution for my case in adding the desired capability property “appWaitActivity”. After this everything works fine and test pass.

wajahat5139 · January 28, 2015, 1:11am

It worked fine for few times but still facing the same issue
DesiredCapabilities capabilities = new DesiredCapabilities(“appWaitActivity”, null, null);
This is what i did and added extra time to launch the app but it doesn’t work all the times

Chathura_Dhanushka · August 7, 2015, 10:14am

wow this works for me
capabilities.SetCapability(“appWaitActivity”, null);
im on appium + .net

Gourav_jain · September 24, 2015, 6:56am

Better make a folder name “Application” under your project, and put that apk file to application folder.This solved my problem. Because Sometimes when we provide the path for the application, server error gets display

Prajakta_Kolhe · December 7, 2016, 11:53am

Hi,

i am facing same issue but my app is hybrid and only has mainactivity so cannot use appwaitactivity.
Error-Mainactivity never started.
Android -6.0.1
Appium-1.4.16
Real phone

Please help out.

Aleksei · December 7, 2016, 12:12pm

enable server logs. you will see what expected and what found.

Prajakta_Kolhe · December 7, 2016, 1:27pm

yes i get original activity and current activity as same except one comma in current activity.

com…mainactivity is original
com…mainactivity, is current

I even tried to put appwaitactivity with a comma but didnt work.

Aleksei · December 7, 2016, 1:38pm

add server logs.
and mention do you use correct “appWaitPackage” ?

Prajakta_Kolhe · December 7, 2016, 2:12pm

Launching Appium server with command: C:\Program Files (x86)\Appium\node.exe lib\server\main.js --address 127.0.0.1 --port 4723 --app C:\Users\Smartalyse\Downloads\Jedi.apk --platform-name Android --platform-version 23 --automation-name Appium --log-no-color
info: Welcome to Appium v1.4.16 (REV ae6877eff263066b26328d457bd285c0cc62430d)
info: Appium REST http interface listener started on 127.0.0.1:4723
info: [debug] Non-default server args: {“app”:“C:\Users\Smartalyse\Downloads\Jedi.apk”,“address”:“127.0.0.1”,“logNoColors”:true,“platformName”:“Android”,“platformVersion”:“23”,“automationName”:“Appium”}
info: Console LogLevel: debug
info: → POST /wd/hub/session {“capabilities”:{“desiredCapabilities”:{“app”:“C:\Users\Smartalyse\workspace\appium\src\Jedi.apk”,“newCommandTimeout”:“1000”,“xyz”:“.MainActivity”,“appWaitActivity”:“.MainActivity,”,“platformName”:“Android”,“deviceName”:“56622c2a”},“requiredCapabilities”:{}},“desiredCapabilities”:{“app”:“C:\Users\Smartalyse\workspace\appium\src\Jedi.apk”,“newCommandTimeout”:“1000”,“xyz”:“.MainActivity”,“appWaitActivity”:“.MainActivity,”,“platformName”:“Android”,“deviceName”:“56622c2a”},“requiredCapabilities”:{}}
info: Client User-Agent string: Apache-HttpClient/4.5.2 (Java/1.8.0_111)
info: [debug] The following desired capabilities were provided, but not recognized by appium. They will be passed on to any other services running on this server. : xyz
info: [debug] No appActivity desired capability or server param. Parsing from apk.
info: [debug] No appPackage desired capability or server param. Parsing from apk.
info: [debug] Using local app from desired caps: C:\Users\Smartalyse\workspace\appium\src\Jedi.apk
info: [debug] Creating new appium session eacfb439-7d50-4ecc-94a1-f3a572ab57d1
info: Starting android appium
info: [debug] Getting Java version
info: Java version is: 1.8.0_111
info: [debug] Checking whether adb is present
info: [debug] Using adb from C:\android-sdk-windows\platform-tools\adb.exe
info: [debug] Parsing package and activity from app manifest
info: [debug] Checking whether aapt is present
info: [debug] Using aapt from C:\android-sdk-windows\build-tools\25.0.0\aapt.exe
info: [debug] Extracting package and launch activity from manifest.
info: [debug] executing cmd: C:\android-sdk-windows\build-tools\25.0.0\aapt.exe dump badging C:\Users\Smartalyse\workspace\appium\src\Jedi.apk
info: [debug] badging package: com.smartalyse.iot.app.jedi
info: [debug] badging act: com.smartalyse.iot.app.jedi.MainActivity
info: [debug] Parsed package and activity are: com.smartalyse.iot.app.jedi/com.smartalyse.iot.app.jedi.MainActivity
info: [debug] Using fast reset? true
info: [debug] Preparing device for session
info: [debug] Checking whether app is actually present
info: Retrieving device
info: [debug] Trying to find a connected android device
info: [debug] Getting connected devices…
info: [debug] executing cmd: C:\android-sdk-windows\platform-tools\adb.exe devices
info: [debug] 1 device(s) connected
info: Found device 56622c2a
info: [debug] Setting device id to 56622c2a
info: [debug] Waiting for device to be ready and to respond to shell commands (timeout = 5)
info: [debug] executing cmd: C:\android-sdk-windows\platform-tools\adb.exe -s 56622c2a wait-for-device
info: [debug] executing cmd: C:\android-sdk-windows\platform-tools\adb.exe -s 56622c2a shell “echo ‘ready’”
info: [debug] Starting logcat capture
info: [debug] Getting device API level
info: [debug] executing cmd: C:\android-sdk-windows\platform-tools\adb.exe -s 56622c2a shell “getprop ro.build.version.sdk”
info: [debug] Device is at API Level 23
info: Device API level is: 23
info: [debug] Extracting strings for language: default
info: [debug] executing cmd: C:\android-sdk-windows\platform-tools\adb.exe -s 56622c2a shell “getprop persist.sys.language”
info: [debug] Current device persist.sys.language:
info: [debug] java -jar “C:\Program Files (x86)\Appium\node_modules\appium\node_modules\appium-adb\jars\appium_apk_tools.jar” “stringsFromApk” “C:\Users\Smartalyse\workspace\appium\src\Jedi.apk” “C:\Users\SMARTA~1\AppData\Local\Temp\com.smartalyse.iot.app.jedi”
info: [debug] Reading strings from converted strings.json
info: [debug] Setting language to default
info: [debug] executing cmd: C:\android-sdk-windows\platform-tools\adb.exe -s 56622c2a push “C:\Users\SMARTA~1\AppData\Local\Temp\com.smartalyse.iot.app.jedi\strings.json” /data/local/tmp
info: [debug] Checking whether aapt is present
info: [debug] Using aapt from C:\android-sdk-windows\build-tools\25.0.0\aapt.exe
info: [debug] Retrieving process from manifest.
info: [debug] executing cmd: C:\android-sdk-windows\build-tools\25.0.0\aapt.exe dump xmltree C:\Users\Smartalyse\workspace\appium\src\Jedi.apk AndroidManifest.xml
info: [debug] Set app process to: com.smartalyse.iot.app.jedi
info: [debug] Not uninstalling app since server not started with --full-reset
info: [debug] Checking app cert for C:\Users\Smartalyse\workspace\appium\src\Jedi.apk.
info: [debug] executing cmd: java -jar “C:\Program Files (x86)\Appium\node_modules\appium\node_modules\appium-adb\jars\verify.jar” C:\Users\Smartalyse\workspace\appium\src\Jedi.apk
info: [debug] App already signed.
info: [debug] Zip-aligning C:\Users\Smartalyse\workspace\appium\src\Jedi.apk
info: [debug] Checking whether zipalign is present
info: [debug] Using zipalign from C:\android-sdk-windows\build-tools\25.0.0\zipalign.exe
info: [debug] Zip-aligning apk.
info: [debug] executing cmd: C:\android-sdk-windows\build-tools\25.0.0\zipalign.exe -f 4 C:\Users\Smartalyse\workspace\appium\src\Jedi.apk C:\Users\SMARTA~1\AppData\Local\Temp\116117-3520-ldellc\appium.tmp
info: [debug] MD5 for app is da09a34e368caedaa87522db80bb3691
info: [debug] executing cmd: C:\android-sdk-windows\platform-tools\adb.exe -s 56622c2a shell “ls /data/local/tmp/da09a34e368caedaa87522db80bb3691.apk”
info: [debug] Getting install status for com.smartalyse.iot.app.jedi
info: [debug] Getting device API level
info: [debug] executing cmd: C:\android-sdk-windows\platform-tools\adb.exe -s 56622c2a shell “getprop ro.build.version.sdk”
info: [debug] Device is at API Level 23
info: [debug] executing cmd: C:\android-sdk-windows\platform-tools\adb.exe -s 56622c2a shell “pm list packages -3 com.smartalyse.iot.app.jedi”
info: [debug] App is installed
info: Installing App
info: [debug] executing cmd: C:\android-sdk-windows\platform-tools\adb.exe -s 56622c2a shell “mkdir -p /data/local/tmp/”
info: [debug] Removing any old apks
info: [debug] executing cmd: C:\android-sdk-windows\platform-tools\adb.exe -s 56622c2a shell “ls /data/local/tmp/*.apk”
info: [debug] executing cmd: C:\android-sdk-windows\platform-tools\adb.exe -s 56622c2a shell rm “/data/local/tmp/f31197c712b638cf8bb5f6c4053c9860.apk”
info: [debug] executing cmd: C:\android-sdk-windows\platform-tools\adb.exe -s 56622c2a push “C:\Users\Smartalyse\workspace\appium\src\Jedi.apk” /data/local/tmp/da09a34e368caedaa87522db80bb3691.apk
info: [debug] Uninstalling com.smartalyse.iot.app.jedi
info: [debug] executing cmd: C:\android-sdk-windows\platform-tools\adb.exe -s 56622c2a shell “am force-stop com.smartalyse.iot.app.jedi”
info: [debug] executing cmd: C:\android-sdk-windows\platform-tools\adb.exe -s 56622c2a uninstall com.smartalyse.iot.app.jedi
info: [debug] App was uninstalled
info: [debug] executing cmd: C:\android-sdk-windows\platform-tools\adb.exe -s 56622c2a shell “pm install -r /data/local/tmp/da09a34e368caedaa87522db80bb3691.apk”
info: [debug] Forwarding system:4724 to device:4724
info: [debug] executing cmd: C:\android-sdk-windows\platform-tools\adb.exe -s 56622c2a forward tcp:4724 tcp:4724
info: [debug] Pushing appium bootstrap to device…
info: [debug] executing cmd: C:\android-sdk-windows\platform-tools\adb.exe -s 56622c2a push “C:\Program Files (x86)\Appium\node_modules\appium\build\android_bootstrap\AppiumBootstrap.jar” /data/local/tmp/
info: [debug] Pushing settings apk to device…
info: [debug] executing cmd: C:\android-sdk-windows\platform-tools\adb.exe -s 56622c2a install “C:\Program Files (x86)\Appium\node_modules\appium\build\settings_apk\settings_apk-debug.apk”
info: [debug] Pushing unlock helper app to device…
info: [debug] executing cmd: C:\android-sdk-windows\platform-tools\adb.exe -s 56622c2a install “C:\Program Files (x86)\Appium\node_modules\appium\build\unlock_apk\unlock_apk-debug.apk”
info: Starting App
info: [debug] Attempting to kill all ‘uiautomator’ processes
info: [debug] Getting all processes with ‘uiautomator’
info: [debug] executing cmd: C:\android-sdk-windows\platform-tools\adb.exe -s 56622c2a shell “ps ‘uiautomator’”
info: [debug] No matching processes found
info: [debug] Running bootstrap
info: [debug] spawning: C:\android-sdk-windows\platform-tools\adb.exe -s 56622c2a shell uiautomator runtest AppiumBootstrap.jar -c io.appium.android.bootstrap.Bootstrap -e pkg com.smartalyse.iot.app.jedi -e disableAndroidWatchers false
info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: numtests=1
info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: stream=
info: [debug] [UIAUTOMATOR STDOUT] io.appium.android.bootstrap.Bootstrap:
info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: id=UiAutomatorTestRunner
info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: test=testRunServer
info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: class=io.appium.android.bootstrap.Bootstrap
info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: current=1
info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS_CODE: 1
info: [debug] [BOOTSTRAP] [debug] Socket opened on port 4724
info: [debug] [BOOTSTRAP] [debug] Appium Socket Server Ready
info: [debug] [BOOTSTRAP] [debug] Loading json…
info: [debug] [BOOTSTRAP] [debug] json loading complete.
info: [debug] [BOOTSTRAP] [debug] Registered crash watchers.
info: [debug] Waking up device if it’s not alive
info: [debug] Pushing command to appium work queue: [“wake”,{}]
info: [debug] [BOOTSTRAP] [debug] Client connected
info: [debug] [BOOTSTRAP] [debug] Got data from client: {“cmd”:“action”,“action”:“wake”,“params”:{}}
info: [debug] [BOOTSTRAP] [debug] Got command of type ACTION
info: [debug] executing cmd: C:\android-sdk-windows\platform-tools\adb.exe -s 56622c2a shell “dumpsys window”
info: [debug] [BOOTSTRAP] [debug] Got command action: wake
info: [debug] [BOOTSTRAP] [debug] Returning result: {“status”:0,“value”:true}
info: [debug] Screen already unlocked, continuing.
info: [debug] Pushing command to appium work queue: [“getDataDir”,{}]
info: [debug] [BOOTSTRAP] [debug] Got data from client: {“cmd”:“action”,“action”:“getDataDir”,“params”:{}}
info: [debug] [BOOTSTRAP] [debug] Got command of type ACTION
info: [debug] [BOOTSTRAP] [debug] Got command action: getDataDir
info: [debug] [BOOTSTRAP] [debug] Returning result: {“status”:0,“value”:“/data/local/tmp”}
info: [debug] dataDir set to: /data/local/tmp
info: [debug] Pushing command to appium work queue: [“compressedLayoutHierarchy”,{“compressLayout”:false}]
info: [debug] [BOOTSTRAP] [debug] Got data from client: {“cmd”:“action”,“action”:“compressedLayoutHierarchy”,“params”:{“compressLayout”:false}}
info: [debug] [BOOTSTRAP] [debug] Got command of type ACTION
info: [debug] [BOOTSTRAP] [debug] Got command action: compressedLayoutHierarchy
info: [debug] Getting device API level
info: [debug] executing cmd: C:\android-sdk-windows\platform-tools\adb.exe -s 56622c2a shell “getprop ro.build.version.sdk”
info: [debug] [BOOTSTRAP] [debug] Returning result: {“status”:0,“value”:false}
info: [debug] Device is at API Level 23
info: [debug] executing cmd: C:\android-sdk-windows\platform-tools\adb.exe -s 56622c2a shell “am start -S -a android.intent.action.MAIN -c android.intent.category.LAUNCHER -f 0x10200000 -n com.smartalyse.iot.app.jedi/com.smartalyse.iot.app.jedi.MainActivity”
info: [debug] Waiting for pkg “com.smartalyse.iot.app.jedi” and activity “.MainActivity,” to be focused
info: [debug] Getting focused package and activity
info: [debug] executing cmd: C:\android-sdk-windows\platform-tools\adb.exe -s 56622c2a shell “dumpsys window windows”
info: [debug] Getting focused package and activity
info: [debug] executing cmd: C:\android-sdk-windows\platform-tools\adb.exe -s 56622c2a shell “dumpsys window windows”
info: [debug] Getting focused package and activity
info: [debug] executing cmd: C:\android-sdk-windows\platform-tools\adb.exe -s 56622c2a shell “dumpsys window windows”
info: [debug] Getting focused package and activity
info: [debug] executing cmd: C:\android-sdk-windows\platform-tools\adb.exe -s 56622c2a shell “dumpsys window windows”
info: [debug] Getting focused package and activity
info: [debug] executing cmd: C:\android-sdk-windows\platform-tools\adb.exe -s 56622c2a shell “dumpsys window windows”
info: [debug] Getting focused package and activity
info: [debug] executing cmd: C:\android-sdk-windows\platform-tools\adb.exe -s 56622c2a shell “dumpsys window windows”
info: [debug] Getting focused package and activity
info: [debug] executing cmd: C:\android-sdk-windows\platform-tools\adb.exe -s 56622c2a shell “dumpsys window windows”
info: [debug] Getting focused package and activity
info: [debug] executing cmd: C:\android-sdk-windows\platform-tools\adb.exe -s 56622c2a shell “dumpsys window windows”
info: [debug] Getting focused package and activity
info: [debug] executing cmd: C:\android-sdk-windows\platform-tools\adb.exe -s 56622c2a shell “dumpsys window windows”
info: [debug] Getting focused package and activity
info: [debug] executing cmd: C:\android-sdk-windows\platform-tools\adb.exe -s 56622c2a shell “dumpsys window windows”
info: [debug] Getting focused package and activity
info: [debug] executing cmd: C:\android-sdk-windows\platform-tools\adb.exe -s 56622c2a shell “dumpsys window windows”
info: [debug] Getting focused package and activity
info: [debug] executing cmd: C:\android-sdk-windows\platform-tools\adb.exe -s 56622c2a shell “dumpsys window windows”
info: [debug] Getting focused package and activity
info: [debug] executing cmd: C:\android-sdk-windows\platform-tools\adb.exe -s 56622c2a shell “dumpsys window windows”
info: [debug] Getting focused package and activity
info: [debug] executing cmd: C:\android-sdk-windows\platform-tools\adb.exe -s 56622c2a shell “dumpsys window windows”
info: [debug] Getting focused package and activity
info: [debug] executing cmd: C:\android-sdk-windows\platform-tools\adb.exe -s 56622c2a shell “dumpsys window windows”
info: [debug] Getting focused package and activity
info: [debug] executing cmd: C:\android-sdk-windows\platform-tools\adb.exe -s 56622c2a shell “dumpsys window windows”
info: [debug] Getting focused package and activity
info: [debug] executing cmd: C:\android-sdk-windows\platform-tools\adb.exe -s 56622c2a shell “dumpsys window windows”
info: [debug] Getting focused package and activity
info: [debug] executing cmd: C:\android-sdk-windows\platform-tools\adb.exe -s 56622c2a shell “dumpsys window windows”
info: [debug] Getting focused package and activity
info: [debug] executing cmd: C:\android-sdk-windows\platform-tools\adb.exe -s 56622c2a shell “dumpsys window windows”
info: [debug] Getting focused package and activity
info: [debug] executing cmd: C:\android-sdk-windows\platform-tools\adb.exe -s 56622c2a shell “dumpsys window windows”
info: [debug] Getting focused package and activity
info: [debug] executing cmd: C:\android-sdk-windows\platform-tools\adb.exe -s 56622c2a shell “dumpsys window windows”
info: [debug] Getting focused package and activity
info: [debug] executing cmd: C:\android-sdk-windows\platform-tools\adb.exe -s 56622c2a shell “dumpsys window windows”
info: [debug] Getting focused package and activity
info: [debug] executing cmd: C:\android-sdk-windows\platform-tools\adb.exe -s 56622c2a shell “dumpsys window windows”
info: [debug] Getting focused package and activity
info: [debug] executing cmd: C:\android-sdk-windows\platform-tools\adb.exe -s 56622c2a shell “dumpsys window windows”
info: [debug] Getting focused package and activity
info: [debug] executing cmd: C:\android-sdk-windows\platform-tools\adb.exe -s 56622c2a shell “dumpsys window windows”
error: com.smartalyse.iot.app.jedi/.MainActivity, never started. Current: com.smartalyse.iot.app.jedi/.MainActivity,
info: [debug] Stopping logcat capture
info: [debug] Logcat terminated with code null, signal SIGTERM
info: [debug] [BOOTSTRAP] [debug] Got data from client: {“cmd”:“shutdown”}
info: [debug] [BOOTSTRAP] [debug] Got command of type SHUTDOWN
info: [debug] [BOOTSTRAP] [debug] Returning result: {“status”:0,“value”:“OK, shutting down”}
info: [debug] Sent shutdown command, waiting for UiAutomator to stop…
info: [debug] [BOOTSTRAP] [debug] Closed client connection
info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: numtests=1
info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: stream=.
info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: id=UiAutomatorTestRunner
info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: test=testRunServer
info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: class=io.appium.android.bootstrap.Bootstrap
info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: current=1
info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS_CODE: 0
info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: stream=
info: [debug] [UIAUTOMATOR STDOUT] Test results for WatcherResultPrinter=.
info: [debug] [UIAUTOMATOR STDOUT] Time: 21.696
info: [debug] [UIAUTOMATOR STDOUT] OK (1 test)
info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS_CODE: -1
info: [debug] UiAutomator shut down normally
info: [debug] Cleaning up android objects
info: [debug] Cleaning up appium session
error: Failed to start an Appium session, err was: Error: com.smartalyse.iot.app.jedi/.MainActivity, never started. Current: com.smartalyse.iot.app.jedi/.MainActivity,
info: [debug] Error: com.smartalyse.iot.app.jedi/.MainActivity, never started. Current: com.smartalyse.iot.app.jedi/.MainActivity,
at [object Object]. (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\appium-adb\lib\adb.js:1314:12)
at [object Object]. (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\appium-adb\lib\adb.js:1258:7)
at [object Object]. (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\appium-adb\lib\adb.js:180:9)
at ChildProcess.exithandler (child_process.js:742:7)
at ChildProcess.emit (events.js:110:17)
at maybeClose (child_process.js:1016:16)
at Process.ChildProcess._handle.onexit (child_process.js:1088:5)
info: [debug] Responding to client with error: {“status”:33,“value”:{“message”:“A new session could not be created. (Original error: com.smartalyse.iot.app.jedi/.MainActivity, never started. Current: com.smartalyse.iot.app.jedi/.MainActivity,)”,“origValue”:“com.smartalyse.iot.app.jedi/.MainActivity, never started. Current: com.smartalyse.iot.app.jedi/.MainActivity,”},“sessionId”:null}
info: ← POST /wd/hub/session 500 33180.667 ms - 340

cap.setcapabilties(“appwaitActivity”, “.Mainactivity,”);

Aleksei · December 7, 2016, 2:51pm

try:

do not set appWaitPackage
add full activity name like:

capabilities.setCapability(“appWaitActivity”,
"ee.xxxxx.activity.LandingPageActivity, " +
"ee.xxxxx.activity.SplashScreenActivity, ");