.MainActivity never started.
1,549 views
Skip to first unread message
Diana Menezes
Mar 28, 2014, 1:53:31 PM3/28/14
to appium-...@googlegroups.com
I am trying to run test on android device. Nexus 5 with android 4.4
The app is succesfully installed and launched, after launching the appium logs show:
info: Waiting for activity to be focused
info: Getting focused package and activity
debug: executing: "/Applications/AndroidStudio.app/sdk/platform-tools/adb" -s (device-id) shell "dumpsys window windows"
This goes on until the error returned in the logs is .MainActivity never started.
Starting appium server with appium --full-reset helped once. I am back to the same issue again.
Any thoughts?
Jonathan Lipps
Mar 28, 2014, 2:09:56 PM3/28/14
to Diana Menezes, appium-...@googlegroups.com
Please paste in the full logs if you'd like help diagnosing the issue.
--
http://appium.io
---
You received this message because you are subscribed to the Google Groups "Appium-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to appium-discus...@googlegroups.com.
Visit this group at http://groups.google.com/group/appium-discuss.
For more options, visit https://groups.google.com/d/optout.
Diana Menezes
Mar 28, 2014, 2:12:31 PM3/28/14
to appium-...@googlegroups.com, Diana Menezes
Hi Jonathan,
Here is the full logcat from start to finish.
It is for Nexus 5, android 4.4
The tests run fine on Galaxy S4, LG G2, MotoX
dianamenezes$ appium --full-reset
info: Welcome to Appium v0.17.6 (REV 7b32947e166a4338047f31ac14457c2b0eb432aa)
info: Appium REST http interface listener started on 0.0.0.0:4723
info - socket.io started
info: Non-default server args: {"fullReset":true,"merciful":true}
debug: Appium request initiated at /wd/hub/session
debug: Request received with params: {"sessionId":null,"desiredCapabilities":{"device":"Android","app-activity":".MainActivity","app":"/Users/dianamenezes/work/socialcast/socialcast-ios/socialcast-uitest/build/Socialcast.apk","version":"4.3","app-package":"com.vmware.socialcast"}}
warn: [DEPRECATED] The device capability has been deprecated and will be removed. Please use the platformName capability instead.
warn: [DEPRECATED] The version capability has been deprecated and will be removed. Please use the platformVersion capability instead.
info: Using local app from desired caps: /Users/dianamenezes/work/socialcast/socialcast-ios/socialcast-uitest/build/Socialcast.apk
info: Creating new appium session 08fe3c0e-9676-4f7d-ab50-d58c1f9953ba
info: Starting android appium
debug: Using fast reset? false
info: Preparing device for session
info: Checking whether app is actually present
info: Checking whether adb is present
info: [ADB] Using adb from /Applications/AndroidStudio.app/sdk/platform-tools/adb
info: Trying to find a connected android device
info: [ADB] Getting connected devices...
debug: executing: "/Applications/AndroidStudio.app/sdk/platform-tools/adb" devices
info: [ADB] 1 device(s) connected
info: Setting device id to 03098228094dd8af
info: [ADB] Waiting for device to be ready and to respond to shell commands (timeout = 5)
debug: executing: "/Applications/AndroidStudio.app/sdk/platform-tools/adb" -s 03098228094dd8af wait-for-device
debug: executing: "/Applications/AndroidStudio.app/sdk/platform-tools/adb" -s 03098228094dd8af shell "echo 'ready'"
info: Starting logcat capture
info: Getting device API level
debug: executing: "/Applications/AndroidStudio.app/sdk/platform-tools/adb" -s 03098228094dd8af shell "getprop ro.build.version.sdk"
info: Device is at API Level 19
debug: java -jar "/usr/local/lib/node_modules/appium/lib/devices/android/helpers/strings_from_apk.jar" "/Users/dianamenezes/work/socialcast/socialcast-ios/socialcast-uitest/build/Socialcast.apk" "/tmp/com.vmware.socialcast"
debug: executing: "/Applications/AndroidStudio.app/sdk/platform-tools/adb" -s 03098228094dd8af push "/tmp/com.vmware.socialcast/strings.json" /data/local/tmp
info: Checking whether aapt is present
info: [ADB] Using aapt from /Applications/AndroidStudio.app/sdk/build-tools/19.0.1/aapt
debug: processFromManifest: "/Applications/AndroidStudio.app/sdk/build-tools/19.0.1/aapt" dump xmltree /Users/dianamenezes/work/socialcast/socialcast-ios/socialcast-uitest/build/Socialcast.apk AndroidManifest.xml
debug: Set app process to: ware.socialcast
info: Uninstalling com.vmware.socialcast
debug: executing: "/Applications/AndroidStudio.app/sdk/platform-tools/adb" -s 03098228094dd8af uninstall com.vmware.socialcast
debug: App was uninstalled
info: MD5 for app is 4a16ab0a33c4a40cd1d08d2d1410f44a
debug: executing: "/Applications/AndroidStudio.app/sdk/platform-tools/adb" -s 03098228094dd8af shell "ls /data/local/tmp/4a16ab0a33c4a40cd1d08d2d1410f44a.apk"
debug: Getting install status for com.vmware.socialcast
debug: executing: "/Applications/AndroidStudio.app/sdk/platform-tools/adb" -s 03098228094dd8af shell "pm list packages -3 com.vmware.socialcast"
info: [ADB] App is not installed
debug: Checking app cert for /Users/dianamenezes/work/socialcast/socialcast-ios/socialcast-uitest/build/Socialcast.apk: java -jar "/usr/local/lib/node_modules/appium/lib/devices/android/helpers/verify.jar" "/Users/dianamenezes/work/socialcast/socialcast-ios/socialcast-uitest/build/Socialcast.apk"
debug: App already signed.
info: Zip-aligning /Users/dianamenezes/work/socialcast/socialcast-ios/socialcast-uitest/build/Socialcast.apk
info: Checking whether zipalign is present
info: [ADB] Using zipalign from /Applications/AndroidStudio.app/sdk/tools/zipalign
debug: zipAlignApk: "/Applications/AndroidStudio.app/sdk/tools/zipalign" -f 4 "/Users/dianamenezes/work/socialcast/socialcast-ios/socialcast-uitest/build/Socialcast.apk" "/var/folders/56/vwfw6qk138jbfy6sj9f0jrmr0000gn/T/appium114228-16139-1ogmewr.tmp"
debug: executing: "/Applications/AndroidStudio.app/sdk/platform-tools/adb" -s 03098228094dd8af shell "mkdir -p /data/local/tmp/"
info: Removing any old apks
debug: executing: "/Applications/AndroidStudio.app/sdk/platform-tools/adb" -s 03098228094dd8af shell "ls /data/local/tmp/*.apk"
info: Found an apk we want to keep at /data/local/tmp/4a16ab0a33c4a40cd1d08d2d1410f44a.apk
info: Couldn't find any apks to remove
debug: executing: "/Applications/AndroidStudio.app/sdk/platform-tools/adb" -s 03098228094dd8af shell "pm install -r /data/local/tmp/4a16ab0a33c4a40cd1d08d2d1410f44a.apk"
info: [ADB] Forwarding system:4724 to device:4724
debug: executing: "/Applications/AndroidStudio.app/sdk/platform-tools/adb" -s 03098228094dd8af forward tcp:4724 tcp:4724
debug: Pushing appium bootstrap to device...
debug: executing: "/Applications/AndroidStudio.app/sdk/platform-tools/adb" -s 03098228094dd8af push "/usr/local/lib/node_modules/appium/build/android_bootstrap/AppiumBootstrap.jar" /data/local/tmp/
debug: Pushing unlock helper app to device...
debug: executing: "/Applications/AndroidStudio.app/sdk/platform-tools/adb" -s 03098228094dd8af install "/usr/local/lib/node_modules/appium/build/unlock_apk/unlock_apk-debug.apk"
info: Attempting to kill all 'uiautomator' processes
info: Getting all processes with 'uiautomator'
debug: executing: "/Applications/AndroidStudio.app/sdk/platform-tools/adb" -s 03098228094dd8af shell "ps 'uiautomator'"
info: No matching processes found
info: Running bootstrap
debug: spawning: /Applications/AndroidStudio.app/sdk/platform-tools/adb -s 03098228094dd8af shell uiautomator runtest AppiumBootstrap.jar -c io.appium.android.bootstrap.Bootstrap
info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: numtests=1
info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: stream=
info: [UIAUTOMATOR STDOUT] io.appium.android.bootstrap.Bootstrap:
info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: id=UiAutomatorTestRunner
info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: test=testRunServer
info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: class=io.appium.android.bootstrap.Bootstrap
info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: current=1
info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS_CODE: 1
info: [BOOTSTRAP] [info] Socket opened on port 4724
info: [BOOTSTRAP] [info] Appium Socket Server Ready
info: [BOOTSTRAP] [info] Loading json...
debug: Waking up device if it's not alive
info: Pushing command to appium work queue: ["wake",{}]
info: [BOOTSTRAP] [info] json loading complete.
info: [BOOTSTRAP] [info] Registered crash watchers.
info: [BOOTSTRAP] [info] Client connected
info: [BOOTSTRAP] [info] Got data from client: {"cmd":"action","action":"wake","params":{}}
info: [BOOTSTRAP] [info] Got command of type ACTION
info: [BOOTSTRAP] [debug] Got command action: wake
info: [BOOTSTRAP] [info] Returning result: {"value":true,"status":0}
debug: executing: "/Applications/AndroidStudio.app/sdk/platform-tools/adb" -s 03098228094dd8af shell "dumpsys window"
info: Writing dumpsys output to /usr/local/lib/node_modules/appium/.dumpsys.log
debug: Screen already unlocked, continuing.
info: Pushing command to appium work queue: ["getDataDir",{}]
info: [BOOTSTRAP] [info] Got data from client: {"cmd":"action","action":"getDataDir","params":{}}
info: [BOOTSTRAP] [info] Got command of type ACTION
info: [BOOTSTRAP] [debug] Got command action: getDataDir
info: [BOOTSTRAP] [info] Returning result: {"value":"\/data\/local\/tmp","status":0}
debug: dataDir set to: /data/local/tmp
debug: executing: "/Applications/AndroidStudio.app/sdk/platform-tools/adb" -s 03098228094dd8af shell "am start -S -a android.intent.action.MAIN -c android.intent.category.LAUNCHER -f 0x10200000 -n com.vmware.socialcast/.MainActivity"
info: Waiting for activity to be focused
info: Getting focused package and activity
debug: executing: "/Applications/AndroidStudio.app/sdk/platform-tools/adb" -s 03098228094dd8af shell "dumpsys window windows"
info: Getting focused package and activity
debug: executing: "/Applications/AndroidStudio.app/sdk/platform-tools/adb" -s 03098228094dd8af shell "dumpsys window windows"
info: Getting focused package and activity
debug: executing: "/Applications/AndroidStudio.app/sdk/platform-tools/adb" -s 03098228094dd8af shell "dumpsys window windows"
info: Getting focused package and activity
debug: executing: "/Applications/AndroidStudio.app/sdk/platform-tools/adb" -s 03098228094dd8af shell "dumpsys window windows"
info: Getting focused package and activity
debug: executing: "/Applications/AndroidStudio.app/sdk/platform-tools/adb" -s 03098228094dd8af shell "dumpsys window windows"
info: Getting focused package and activity
debug: executing: "/Applications/AndroidStudio.app/sdk/platform-tools/adb" -s 03098228094dd8af shell "dumpsys window windows"
info: Getting focused package and activity
debug: executing: "/Applications/AndroidStudio.app/sdk/platform-tools/adb" -s 03098228094dd8af shell "dumpsys window windows"
info: Getting focused package and activity
debug: executing: "/Applications/AndroidStudio.app/sdk/platform-tools/adb" -s 03098228094dd8af shell "dumpsys window windows"
info: Getting focused package and activity
debug: executing: "/Applications/AndroidStudio.app/sdk/platform-tools/adb" -s 03098228094dd8af shell "dumpsys window windows"
info: Getting focused package and activity
debug: executing: "/Applications/AndroidStudio.app/sdk/platform-tools/adb" -s 03098228094dd8af shell "dumpsys window windows"
info: Getting focused package and activity
debug: executing: "/Applications/AndroidStudio.app/sdk/platform-tools/adb" -s 03098228094dd8af shell "dumpsys window windows"
info: Getting focused package and activity
debug: executing: "/Applications/AndroidStudio.app/sdk/platform-tools/adb" -s 03098228094dd8af shell "dumpsys window windows"
info: Getting focused package and activity
debug: executing: "/Applications/AndroidStudio.app/sdk/platform-tools/adb" -s 03098228094dd8af shell "dumpsys window windows"
info: Getting focused package and activity
debug: executing: "/Applications/AndroidStudio.app/sdk/platform-tools/adb" -s 03098228094dd8af shell "dumpsys window windows"
info: Getting focused package and activity
debug: executing: "/Applications/AndroidStudio.app/sdk/platform-tools/adb" -s 03098228094dd8af shell "dumpsys window windows"
info: Getting focused package and activity
debug: executing: "/Applications/AndroidStudio.app/sdk/platform-tools/adb" -s 03098228094dd8af shell "dumpsys window windows"
info: Getting focused package and activity
debug: executing: "/Applications/AndroidStudio.app/sdk/platform-tools/adb" -s 03098228094dd8af shell "dumpsys window windows"
info: Getting focused package and activity
debug: executing: "/Applications/AndroidStudio.app/sdk/platform-tools/adb" -s 03098228094dd8af shell "dumpsys window windows"
info: Getting focused package and activity
debug: executing: "/Applications/AndroidStudio.app/sdk/platform-tools/adb" -s 03098228094dd8af shell "dumpsys window windows"
info: Getting focused package and activity
debug: executing: "/Applications/AndroidStudio.app/sdk/platform-tools/adb" -s 03098228094dd8af shell "dumpsys window windows"
info: Getting focused package and activity
debug: executing: "/Applications/AndroidStudio.app/sdk/platform-tools/adb" -s 03098228094dd8af shell "dumpsys window windows"
info: Getting focused package and activity
debug: executing: "/Applications/AndroidStudio.app/sdk/platform-tools/adb" -s 03098228094dd8af shell "dumpsys window windows"
info: Getting focused package and activity
debug: executing: "/Applications/AndroidStudio.app/sdk/platform-tools/adb" -s 03098228094dd8af shell "dumpsys window windows"
info: Getting focused package and activity
debug: executing: "/Applications/AndroidStudio.app/sdk/platform-tools/adb" -s 03098228094dd8af shell "dumpsys window windows"
info: Getting focused package and activity
debug: executing: "/Applications/AndroidStudio.app/sdk/platform-tools/adb" -s 03098228094dd8af shell "dumpsys window windows"
info: Getting focused package and activity
debug: executing: "/Applications/AndroidStudio.app/sdk/platform-tools/adb" -s 03098228094dd8af shell "dumpsys window windows"
error: com.vmware.socialcast/.MainActivity never started. Current: com.vmware.socialcast/.account.SocialcastAccountAuthenticatorActivity
info: Stopping logcat capture
debug: Logcat terminated with code null, signal SIGTERM
info: [BOOTSTRAP] [info] Got data from client: {"cmd":"shutdown"}
info: [BOOTSTRAP] [info] Got command of type SHUTDOWN
info: [BOOTSTRAP] [info] Returning result: {"value":"OK, shutting down","status":0}
info: [BOOTSTRAP] [info] Closed client connection
info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: numtests=1
info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: stream=.
info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: id=UiAutomatorTestRunner
info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: test=testRunServer
info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: class=io.appium.android.bootstrap.Bootstrap
info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: current=1
info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS_CODE: 0
info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: stream=
info: [UIAUTOMATOR STDOUT] Test results for WatcherResultPrinter=.
info: [UIAUTOMATOR STDOUT] Time: 21.676
info: [UIAUTOMATOR STDOUT] OK (1 test)
info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS_CODE: -1
info: Sent shutdown command, waiting for UiAutomator to stop...
info: UiAutomator shut down normally
info: Cleaning up android objects
info: Cleaning up appium session
error: Failed to start an Appium session, err was: Error: com.vmware.socialcast/.MainActivity never started. Current: com.vmware.socialcast/.account.SocialcastAccountAuthenticatorActivity
info: Error: com.vmware.socialcast/.MainActivity never started. Current: com.vmware.socialcast/.account.SocialcastAccountAuthenticatorActivity
at null.<anonymous> (/usr/local/lib/node_modules/appium/lib/devices/android/adb.js:1253:12)
at null.<anonymous> (/usr/local/lib/node_modules/appium/lib/devices/android/adb.js:1199:7)
at /usr/local/lib/node_modules/appium/lib/devices/android/adb.js:153: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 Socket.<anonymous> (child_process.js:956:11)
at Socket.EventEmitter.emit (events.js:95:17)
at Pipe.close (net.js:465:12)
info: Responding to client with error: {"status":33,"value":{"message":"A new session could not be created. (Original error: com.vmware.socialcast/.MainActivity never started. Current: com.vmware.socialcast/.account.SocialcastAccountAuthenticatorActivity)","origValue":"com.vmware.socialcast/.MainActivity never started. Current: com.vmware.socialcast/.account.SocialcastAccountAuthenticatorActivity"},"sessionId":null}
POST /wd/hub/session 500 29387ms - 408b
Jonathan Lipps
Mar 28, 2014, 2:14:18 PM3/28/14
to Diana Menezes, appium-...@googlegroups.com
This is the problem:
error: com.vmware.socialcast/.MainActivity never started. Current: com.vmware.socialcast/.account.SocialcastAccountAuthenticatorActivity
You need to use app-wait-activity if the activity your app moves to on launch is different from the launch activity.
Diana Menezes
Mar 28, 2014, 2:16:16 PM3/28/14
to appium-...@googlegroups.com, Diana Menezes
I tried that as well.
But I get the same error.
Here is what android43.json has:
{"device":"Android",
"version":"4.3",
"app":"build/Socialcast.apk",
"app-package":"com.vmware.socialcast",
"app-wait-activity":".MainActivity"
}
Jonathan Lipps
Mar 28, 2014, 2:21:38 PM3/28/14
to Diana Menezes, appium-...@googlegroups.com
You need to wait for the activity which will actually become active. I posted it below. It is: .SocialcastAccountAuthenticatorActivity
Sangeetha Srinivasan
Mar 28, 2014, 2:29:47 PM3/28/14
to appium-...@googlegroups.com, Diana Menezes
@jlipps
{"device":"Android",
"version":"4.4",
"app":"build/Socialcast.apk",
"app-package":"com.vmware.socialcast",
"app-activity":".MainActivity",
"app-wait-activity":".account.SocialcastAccountAuthenticatorActivity"
}
tests run fine with motox with same android version but not with nexus
Jonathan Lipps
Mar 28, 2014, 2:32:11 PM3/28/14
to Sangeetha Srinivasan, appium-...@googlegroups.com, Diana Menezes
What error do you get on the nexus then. What are the full logs.
Diana Menezes
Mar 28, 2014, 2:34:19 PM3/28/14
to appium-...@googlegroups.com, Sangeetha Srinivasan, Diana Menezes
Hi Jonathan,
here are the logs for Nexus
dianamenezes$ appium --full-reset
info: Welcome to Appium v0.17.6 (REV 7b32947e166a4338047f31ac14457c2b0eb432aa)
info: Appium REST http interface listener started on 0.0.0.0:4723
info - socket.io started
info: Non-default server args: {"fullReset":true,"merciful":true}
debug: Appium request initiated at /wd/hub/session
debug: Request received with params: {"sessionId":null,"desiredCapabilities":{"app-package":"com.vmware.socialcast","app":"/Users/dianamenezes/work/socialcast/socialcast-ios/socialcast-uitest/build/Socialcast.apk","app-wait-activity":".SocialcastAccountAuthenticatorActivity","version":"4.4","device":"Android","app-activity":".MainActivity"}}
warn: [DEPRECATED] The version capability has been deprecated and will be removed. Please use the platformVersion capability instead.
warn: [DEPRECATED] The device capability has been deprecated and will be removed. Please use the platformName capability instead.
info: Using local app from desired caps: /Users/dianamenezes/work/socialcast/socialcast-ios/socialcast-uitest/build/Socialcast.apk
info: Creating new appium session 2a5405eb-3286-460c-a57b-30778c700436
debug: zipAlignApk: "/Applications/AndroidStudio.app/sdk/tools/zipalign" -f 4 "/Users/dianamenezes/work/socialcast/socialcast-ios/socialcast-uitest/build/Socialcast.apk" "/var/folders/56/vwfw6qk138jbfy6sj9f0jrmr0000gn/T/appium114228-16914-8xsx0.tmp"
debug: executing: "/Applications/AndroidStudio.app/sdk/platform-tools/adb" -s 03098228094dd8af shell "mkdir -p /data/local/tmp/"
info: Removing any old apks
debug: executing: "/Applications/AndroidStudio.app/sdk/platform-tools/adb" -s 03098228094dd8af shell "ls /data/local/tmp/*.apk"
info: Found an apk we want to keep at /data/local/tmp/4a16ab0a33c4a40cd1d08d2d1410f44a.apk
info: Couldn't find any apks to remove
debug: executing: "/Applications/AndroidStudio.app/sdk/platform-tools/adb" -s 03098228094dd8af shell "pm install -r /data/local/tmp/4a16ab0a33c4a40cd1d08d2d1410f44a.apk"
info: [ADB] Forwarding system:4724 to device:4724
debug: executing: "/Applications/AndroidStudio.app/sdk/platform-tools/adb" -s 03098228094dd8af forward tcp:4724 tcp:4724
debug: Pushing appium bootstrap to device...
debug: executing: "/Applications/AndroidStudio.app/sdk/platform-tools/adb" -s 03098228094dd8af push "/usr/local/lib/node_modules/appium/build/android_bootstrap/AppiumBootstrap.jar" /data/local/tmp/
debug: Pushing unlock helper app to device...
debug: executing: "/Applications/AndroidStudio.app/sdk/platform-tools/adb" -s 03098228094dd8af install "/usr/local/lib/node_modules/appium/build/unlock_apk/unlock_apk-debug.apk"
info: Attempting to kill all 'uiautomator' processes
info: Getting all processes with 'uiautomator'
debug: executing: "/Applications/AndroidStudio.app/sdk/platform-tools/adb" -s 03098228094dd8af shell "ps 'uiautomator'"
info: Attempting to kill process 4566
debug: executing: "/Applications/AndroidStudio.app/sdk/platform-tools/adb" -s 03098228094dd8af shell "kill 4566"
error: com.vmware.socialcast/.SocialcastAccountAuthenticatorActivity never started. Current: com.vmware.socialcast/.account.SocialcastAccountAuthenticatorActivity
info: Stopping logcat capture
debug: Logcat terminated with code null, signal SIGTERM
info: [BOOTSTRAP] [info] Got data from client: {"cmd":"shutdown"}
info: [BOOTSTRAP] [info] Got command of type SHUTDOWN
info: [BOOTSTRAP] [info] Returning result: {"value":"OK, shutting down","status":0}
info: [BOOTSTRAP] [info] Closed client connection
info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: numtests=1
info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: stream=.
info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: id=UiAutomatorTestRunner
info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: test=testRunServer
info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: class=io.appium.android.bootstrap.Bootstrap
info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: current=1
info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS_CODE: 0
info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: stream=
info: [UIAUTOMATOR STDOUT] Test results for WatcherResultPrinter=.
info: [UIAUTOMATOR STDOUT] Time: 21.623
info: [UIAUTOMATOR STDOUT] OK (1 test)
info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS_CODE: -1
info: Sent shutdown command, waiting for UiAutomator to stop...
info: UiAutomator shut down normally
info: Cleaning up android objects
info: Cleaning up appium session
error: Failed to start an Appium session, err was: Error: com.vmware.socialcast/.SocialcastAccountAuthenticatorActivity never started. Current: com.vmware.socialcast/.account.SocialcastAccountAuthenticatorActivity
info: Error: com.vmware.socialcast/.SocialcastAccountAuthenticatorActivity never started. Current: com.vmware.socialcast/.account.SocialcastAccountAuthenticatorActivity
at null.<anonymous> (/usr/local/lib/node_modules/appium/lib/devices/android/adb.js:1253:12)
at null.<anonymous> (/usr/local/lib/node_modules/appium/lib/devices/android/adb.js:1199:7)
at /usr/local/lib/node_modules/appium/lib/devices/android/adb.js:153: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 Socket.<anonymous> (child_process.js:956:11)
at Socket.EventEmitter.emit (events.js:95:17)
at Pipe.close (net.js:465:12)
info: Responding to client with error: {"status":33,"value":{"message":"A new session could not be created. (Original error: com.vmware.socialcast/.SocialcastAccountAuthenticatorActivity never started. Current: com.vmware.socialcast/.account.SocialcastAccountAuthenticatorActivity)","origValue":"com.vmware.socialcast/.SocialcastAccountAuthenticatorActivity never started. Current: com.vmware.socialcast/.account.SocialcastAccountAuthenticatorActivity"},"sessionId":null}
POST /wd/hub/session 500 30812ms - 460b
Jonathan Lipps
Mar 28, 2014, 2:36:38 PM3/28/14
to Diana Menezes, appium-...@googlegroups.com, Sangeetha Srinivasan
I accidentally didn't include ".account" when I copied and pasted the activity before. The app-wait-activity should be what it shows as current here:
Error: com.vmware.socialcast/.SocialcastAccountAuthenticatorActivity never started. Current: com.vmware.socialcast/.account.SocialcastAccountAuthenticatorActivity
See how it shows you what the current activity is? This is designed for just this situation where you need to know what activity to wait for.
Diana Menezes
Mar 28, 2014, 2:39:22 PM3/28/14
to appium-...@googlegroups.com, Diana Menezes, Sangeetha Srinivasan
That worked!
Thank you Jonathan for helping.
Tests are now running on Nexus!
-Diana
...
Siva Subramanian
Jun 2, 2014, 10:37:37 AM6/2/14
to appium-...@googlegroups.com, menezes...@gmail.com, sangeethas...@gmail.com
Hi Diana,
I am facing the similar issue below . could you please resolve it for me ..
logs Attached :
> Starting Node Server
> info: Welcome to Appium v1.0.0 (REV f0a00fab2335fa88cb355ab4dc43a9cd3f3236c0)
> info: Appium REST http interface listener started on 127.0.0.1:4723
> info: socket.io started
> info: Non-default server args: {"address":"127.0.0.1","logNoColors":true}
> ERROR: debug: Appium request initiated at /wd/hub/session
> info: No appActivity desired capability or server param. Parsing from apk.
> ERROR: debug: Request received with params: {"desiredCapabilities":{"newCommandTimeout":"300","platform":"WINDOWS","app":"D:\\adt-bundle-windows-x86_64-20131030\\adt-bundle-windows-x86_64-20131030\\sdk\\platform-tools\\mvip-Android-2.2.apk","javascriptEnabled":true,"acceptSslCerts":true,"browserName":"","app-package":"com.verisign.mvip.main","device":"Android","hasTouchScreen":true,"app-wait-activity":"com.verisign.mvip.main.EulaActivity","app-activity":"com.verisign.mvip.main.MainScreenActivity","version":"4.3"}}
> info: No appPackage desired capability or server param. Parsing from apk.
> ERROR: debug: Using fast reset? true
> info: Using local app from desired caps: D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\mvip-Android-2.2.apk
> info: Creating new appium session df864cfd-8d96-4280-a95c-f190ebcbc29c
> info: Starting android appium
> info: Preparing device for session
> info: Checking whether app is actually present
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" devices
> info: Checking whether adb is present
> info: [ADB] Using adb from D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe
> info: Trying to find a connected android device
> info: [ADB] Getting connected devices...
> info: [ADB] 1 device(s) connected
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 wait-for-device
> info: Setting device id to 7d746172
> info: [ADB] Waiting for device to be ready and to respond to shell commands (timeout = 5)
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 shell "echo 'ready'"
> info: Starting logcat capture
> info: Checking whether aapt is present
> ERROR: debug: packageAndLaunchActivityFromManifest: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\build-tools\android-4.4\aapt.exe" dump badging D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\mvip-Android-2.2.apk
> info: [ADB] Using aapt from D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\build-tools\android-4.4\aapt.exe
> ERROR: debug: badging package: com.verisign.mvip.main
> info: Getting device API level
> ERROR: debug: badging act: com.verisign.mvip.main.MainActivity
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 shell "getprop ro.build.version.sdk"
> info: Device is at API Level 18
> ERROR: debug: java -jar "D:\Appium-version1.0\AppiumForWindows-1.0.0.3\Appium\node_modules\appium\lib\devices\android\helpers\strings_from_apk.jar" "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\mvip-Android-2.2.apk" "C:\Windows\Temp\com.verisign.mvip.main"
> warn: Error getting strings.xml from apk
> ERROR: debug: Exception in thread "main" java.lang.Exception: Output is not an existing readable directory.
> ERROR: at strings.StringsXML.e(StringsXML.java:105)
> ERROR: at strings.StringsXML.main(StringsXML.java:140)
> ERROR:
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 shell "echo '{}' > D:\data\local\tmp\strings.json"
> info: Checking whether aapt is present
> ERROR: debug: processFromManifest: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\build-tools\android-4.4\aapt.exe" dump xmltree "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\mvip-Android-2.2.apk" AndroidManifest.xml
> info: [ADB] Using aapt from D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\build-tools\android-4.4\aapt.exe
> ERROR: debug: Set app process to: isign.mvip.main
> ERROR: debug: Not uninstalling app since server not started with --full-reset
> ERROR: debug: Checking app cert for D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\mvip-Android-2.2.apk: java -jar "D:\Appium-version1.0\AppiumForWindows-1.0.0.3\Appium\node_modules\appium\lib\devices\android\helpers\verify.jar" "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\mvip-Android-2.2.apk"
> ERROR: debug: App already signed.
> info: Zip-aligning D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\mvip-Android-2.2.apk
> ERROR: debug: zipAlignApk: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\tools\zipalign.exe" -f 4 "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\mvip-Android-2.2.apk" "C:\Users\SIVASU~1\AppData\Local\Temp\appium11452-3508-52ip8o.tmp"
> info: [ADB] Using zipalign from D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\tools\zipalign.exe
> info: MD5 for app is 050044ebd10440cdcc1e41c9d12641c0
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 shell "ls /data/local/tmp/050044ebd10440cdcc1e41c9d12641c0.apk"
> ERROR: debug: Getting install status for com.verisign.mvip.main
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 shell "pm list packages -3 com.verisign.mvip.main"
> info: [ADB] App is installed
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 shell "am force-stop com.verisign.mvip.main"
> info: Running fast reset (stop and clear)
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 shell "pm clear com.verisign.mvip.main"
> info: [ADB] Forwarding system:4724 to device:4724
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 forward tcp:4724 tcp:4724
> ERROR: debug: Pushing appium bootstrap to device...
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 push "D:\\Appium-version1.0\\AppiumForWindows-1.0.0.3\\Appium\\node_modules\\appium\\build\\android_bootstrap\\AppiumBootstrap.jar" /data/local/tmp/
> ERROR: debug: Pushing unlock helper app to device...
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 install "D:\Appium-version1.0\AppiumForWindows-1.0.0.3\Appium\node_modules\appium\build\unlock_apk\unlock_apk-debug.apk"
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 shell "ps 'uiautomator'"
> info: Getting all processes with 'uiautomator'
> info: No matching processes found
> ERROR: debug: spawning: D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe -s 7d746172 shell uiautomator runtest AppiumBootstrap.jar -c io.appium.android.bootstrap.Bootstrap
> info: Running bootstrap
> info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: current=1
> info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: id=UiAutomatorTestRunner
> info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: class=io.appium.android.bootstrap.Bootstrap
> info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: stream=
> info: [UIAUTOMATOR STDOUT] io.appium.android.bootstrap.Bootstrap:
> info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: numtests=1
> info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: test=testRunServer
> info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS_CODE: 1
> info: [BOOTSTRAP] [info] Socket opened on port 4724
> info: [BOOTSTRAP] [info] Appium Socket Server Ready
> ERROR: debug: Waking up device if it's not alive
> info: [BOOTSTRAP] [info] Loading json...
> info: Pushing command to appium work queue: ["wake",{}]
> info: [BOOTSTRAP] [info] json loading complete.
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 shell "dumpsys window"
> info: [BOOTSTRAP] [info] Registered crash watchers.
> info: [BOOTSTRAP] [info] Client connected
> info: [BOOTSTRAP] [info] Got data from client: {"cmd":"action","action":"wake","params":{}}
> info: [BOOTSTRAP] [info] Got command of type ACTION
> info: [BOOTSTRAP] [debug] Got command action: wake
> info: [BOOTSTRAP] [info] Returning result: {"value":true,"status":0}
> info: Writing dumpsys output to D:\Appium-version1.0\AppiumForWindows-1.0.0.3\Appium\node_modules\appium\.dumpsys.log
> ERROR: debug: Screen already unlocked, continuing.
> info: Pushing command to appium work queue: ["getDataDir",{}]
> info: [BOOTSTRAP] [info] Got data from client: {"cmd":"action","action":"getDataDir","params":{}}
> info: [BOOTSTRAP] [info] Got command of type ACTION
> info: [BOOTSTRAP] [debug] Got command action: getDataDir
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 shell "am start -S -a android.intent.action.MAIN -c android.intent.category.LAUNCHER -f 0x10200000 -n com.verisign.mvip.main/com.verisign.mvip.main.MainActivity"
> info: [BOOTSTRAP] [info] Returning result: {"value":"\/data\/local\/tmp","status":0}
> info: Waiting for activity to be focused
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 shell "dumpsys window windows"
> info: Getting focused package and activity
> info: Getting focused package and activity
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 shell "dumpsys window windows"
> ERROR: error: com.verisign.mvip.main/.MainActivity never started. Current: com.verisign.mvip.main/.EulaActivity
> info: Stopping logcat capture
> ERROR: debug: Logcat terminated with code null, signal SIGTERM
> info: [BOOTSTRAP] [info] Got data from client: {"cmd":"shutdown"}
> info: [BOOTSTRAP] [info] Got command of type SHUTDOWN
> info: Sent shutdown command, waiting for UiAutomator to stop...
> info: [BOOTSTRAP] [info] Returning result: {"value":"OK, shutting down","status":0}
> info: [BOOTSTRAP] [info] Closed client connection
> info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: current=1
> info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: id=UiAutomatorTestRunner
> info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: class=io.appium.android.bootstrap.Bootstrap
> info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: stream=.
> info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: numtests=1
> info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: test=testRunServer
> info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS_CODE: 0
> info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: stream=
> info: [UIAUTOMATOR STDOUT] Test results for WatcherResultPrinter=.
> info: [UIAUTOMATOR STDOUT] Time: 22.641
> info: [UIAUTOMATOR STDOUT] OK (1 test)
> info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS_CODE: -1
> info: UiAutomator shut down normally
> ERROR: error: Failed to start an Appium session, err was: Error: com.verisign.mvip.main/.MainActivity never started. Current: com.verisign.mvip.main/.EulaActivity
> info: Cleaning up android objects
> info: Cleaning up appium session
> info: Error: com.verisign.mvip.main/.MainActivity never started. Current: com.verisign.mvip.main/.EulaActivity
> at null.<anonymous> (D:\Appium-version1.0\AppiumForWindows-1.0.0.3\Appium\node_modules\appium\lib\devices\android\adb.js:1268:12)
> at null.<anonymous> (D:\Appium-version1.0\AppiumForWindows-1.0.0.3\Appium\node_modules\appium\lib\devices\android\adb.js:1214:7)
> at D:\Appium-version1.0\AppiumForWindows-1.0.0.3\Appium\node_modules\appium\lib\devices\android\adb.js:154: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)
> info: Responding to client with error: {"status":33,"value":{"message":"A new session could not be created. (Original error: com.verisign.mvip.main/.MainActivity never started. Current: com.verisign.mvip.main/.EulaActivity)","origValue":"com.verisign.mvip.main/.MainActivity never started. Current: com.verisign.mvip.main/.EulaActivity"},"sessionId":null}
> POST /wd/hub/session 500 50943ms - 344b
Thanks
Siva
Isaac Murchie
Jun 2, 2014, 12:48:02 PM6/2/14
to Siva Subramanian, appium-...@googlegroups.com, menezes...@gmail.com, Sangeetha Srinivasan
Make sure you are using the right capabilities for appActivity, appPackage, appWaitActivity and appWaitPackage.
--
Siva Subramanian
Jun 2, 2014, 1:22:41 PM6/2/14
to Isaac Murchie, appium-...@googlegroups.com, menezes...@gmail.com, Sangeetha Srinivasan
HI Isaac,
Thanks for your reply. Following were my capabilities which i have set ..
DesiredCapabilities capabilities = new DesiredCapabilities();
capabilities.setCapability(CapabilityType.BROWSER_NAME,"");
capabilities.setCapability("newCommandTimeout","300");
capabilities.setCapability("device","Android");
capabilities.setCapability(CapabilityType.VERSION,"4.3");
capabilities.setCapability(CapabilityType.PLATFORM,"WINDOWS");
capabilities.setCapability(CapabilityType.SUPPORTS_JAVASCRIPT,true);
capabilities.setCapability(CapabilityType.HAS_TOUCHSCREEN,true);
capabilities.setCapability(CapabilityType.ACCEPT_SSL_CERTS,true);
capabilities.setCapability("app", "D:\\adt-bundle-windows-x86_64-20131030\\adt-bundle-windows-x86_64-20131030\\sdk\\platform-tools\\mvip-Android-2.2.apk");//If you want to run it on emulator.
capabilities.setCapability("app-package", "com.verisign.mvip.main"); // This is package name of your app (you can get it from apk info app)
capabilities.setCapability("app-wait-activity", ".EulaActivity");
capabilities.setCapability("app-activity", "./MainActivity");
//Create RemoteWebDriver instance and connect to the Appium server.
//It will launch the Calculator App in Android Device using the configurations specified in Desired Capabilities
driver = new RemoteWebDriver(new URL("http://127.0.0.1:4723/wd/hub"), capabilities);
driver.manage().timeouts().implicitlyWait(80, TimeUnit.SECONDS);
Logs :
> Killed Node Server.
> Node Server Process Ended
> Starting Node Server
> info: Welcome to Appium v1.1.0 (REV e433bbc31511f199287db7724e1ce692bcb32117)
> info: Appium REST http interface listener started on 127.0.0.1:4723
> info: socket.io started
> info: Non-default server args: {"address":"127.0.0.1","logNoColors":true,"platformName":"Android","platformVersion":"18","automationName":"Appium"}
> ERROR: debug: Appium request initiated at /wd/hub/session
> info: No appActivity desired capability or server param. Parsing from apk.
> info: No appPackage desired capability or server param. Parsing from apk.
> ERROR: debug: Request received with params: {"desiredCapabilities":{"newCommandTimeout":"300","platform":"WINDOWS","app":"D:\\adt-bundle-windows-x86_64-20131030\\adt-bundle-windows-x86_64-20131030\\sdk\\platform-tools\\mvip-Android-2.2.apk","javascriptEnabled":true,"acceptSslCerts":true,"browserName":"","device":"Android","hasTouchScreen":true,"app-wait-activity":".EulaActivity","version":"4.3"}}
> info: Using local app from desired caps: D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\mvip-Android-2.2.apk
> ERROR: debug: Using fast reset? true
> info: Creating new appium session 1a5d57c3-d64f-4b1d-8376-a5846a0a90e8
> info: Starting android appium
> info: Preparing device for session
> info: Checking whether app is actually present
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" devices
> info: Checking whether adb is present
> info: [ADB] Using adb from D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe
> info: Trying to find a connected android device
> info: [ADB] Getting connected devices...
> info: [ADB] 1 device(s) connected
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 wait-for-device
> info: Setting device id to 7d746172
> info: [ADB] Waiting for device to be ready and to respond to shell commands (timeout = 5)
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 shell "echo 'ready'"
> info: Starting logcat capture
> info: Checking whether aapt is present
> ERROR: debug: packageAndLaunchActivityFromManifest: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\build-tools\android-4.4\aapt.exe" dump badging D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\mvip-Android-2.2.apk
> info: [ADB] Using aapt from D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\build-tools\android-4.4\aapt.exe
> ERROR: debug: badging package: com.verisign.mvip.main
> info: Getting device API level
> ERROR: debug: badging act: com.verisign.mvip.main.MainActivity
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 shell "getprop ro.build.version.sdk"
> info: Device is at API Level 18
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 shell "getprop persist.sys.language"
> ERROR: debug: Current device language: en
> ERROR: debug: java -jar "D:\Appium-version1.0\AppiumForWindows-1.1.0.0\Appium\node_modules\appium\lib\devices\android\helpers\strings_from_apk.jar" "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\mvip-Android-2.2.apk" "C:\Windows\Temp\com.verisign.mvip.main" en
> info: No strings.xml for language 'en', getting default strings.xml
> ERROR: debug: java -jar "D:\Appium-version1.0\AppiumForWindows-1.1.0.0\Appium\node_modules\appium\lib\devices\android\helpers\strings_from_apk.jar" "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\mvip-Android-2.2.apk" "C:\Windows\Temp\com.verisign.mvip.main"
> warn: Error getting strings.xml from apk
> ERROR: debug: Exception in thread "main" java.lang.Exception: Output is not an existing readable directory.
> ERROR: at strings.StringsXML.e(StringsXML.java:105)
> ERROR: at strings.StringsXML.main(StringsXML.java:140)
> ERROR:
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 shell "echo '{}' > /data/local/tmp/strings.json"
> info: Checking whether aapt is present
> ERROR: debug: processFromManifest: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\build-tools\android-4.4\aapt.exe" dump xmltree "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\mvip-Android-2.2.apk" AndroidManifest.xml
> info: [ADB] Using aapt from D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\build-tools\android-4.4\aapt.exe
> ERROR: debug: Set app process to: isign.mvip.main
> ERROR: debug: Not uninstalling app since server not started with --full-reset
> ERROR: debug: Checking app cert for D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\mvip-Android-2.2.apk: java -jar "D:\Appium-version1.0\AppiumForWindows-1.1.0.0\Appium\node_modules\appium\lib\devices\android\helpers\verify.jar" "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\mvip-Android-2.2.apk"
> ERROR: debug: App already signed.
> info: Zip-aligning D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\mvip-Android-2.2.apk
> info: Checking whether zipalign is present
> ERROR: debug: zipAlignApk: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\tools\zipalign.exe" -f 4 "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\mvip-Android-2.2.apk" "C:\Users\SIVASU~1\AppData\Local\Temp\appium11452-4264-c561al.tmp"
> info: [ADB] Using zipalign from D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\tools\zipalign.exe
> info: MD5 for app is 050044ebd10440cdcc1e41c9d12641c0
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 shell "ls /data/local/tmp/050044ebd10440cdcc1e41c9d12641c0.apk"
> ERROR: debug: Getting install status for com.verisign.mvip.main
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 shell "pm list packages -3 com.verisign.mvip.main"
> info: [ADB] App is installed
> info: Running fast reset (stop and clear)
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 shell "am force-stop com.verisign.mvip.main"
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 shell "pm clear com.verisign.mvip.main"
> info: [ADB] Forwarding system:4724 to device:4724
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 forward tcp:4724 tcp:4724
> ERROR: debug: Pushing appium bootstrap to device...
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 push "D:\\Appium-version1.0\\AppiumForWindows-1.1.0.0\\Appium\\node_modules\\appium\\build\\android_bootstrap\\AppiumBootstrap.jar" /data/local/tmp/
> ERROR: debug: Pushing unlock helper app to device...
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 install "D:\Appium-version1.0\AppiumForWindows-1.1.0.0\Appium\node_modules\appium\build\unlock_apk\unlock_apk-debug.apk"
> info: Attempting to kill all 'uiautomator' processes
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 shell "ps 'uiautomator'"
> info: Getting all processes with 'uiautomator'
> info: No matching processes found
> ERROR: debug: spawning: D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe -s 7d746172 shell uiautomator runtest AppiumBootstrap.jar -c io.appium.android.bootstrap.Bootstrap
> info: Running bootstrap
> info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: current=1
> info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: id=UiAutomatorTestRunner
> info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: class=io.appium.android.bootstrap.Bootstrap
> info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: stream=
> info: [UIAUTOMATOR STDOUT] io.appium.android.bootstrap.Bootstrap:
> info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: numtests=1
> info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: test=testRunServer
> info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS_CODE: 1
> info: [BOOTSTRAP] [info] Socket opened on port 4724
> info: [BOOTSTRAP] [info] Appium Socket Server Ready
> ERROR: debug: Waking up device if it's not alive
> info: [BOOTSTRAP] [info] Loading json...
> info: [BOOTSTRAP] [info] json loading complete.
> info: [BOOTSTRAP] [info] Registered crash watchers.
> info: Pushing command to appium work queue: ["wake",{}]
> info: [BOOTSTRAP] [info] Client connected
> info: [BOOTSTRAP] [info] Got data from client: {"cmd":"action","action":"wake","params":{}}
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 shell "dumpsys window"
> info: [BOOTSTRAP] [info] Got command of type ACTION
> info: [BOOTSTRAP] [debug] Got command action: wake
> info: [BOOTSTRAP] [info] Returning result: {"value":true,"status":0}
> info: Writing dumpsys output to D:\Appium-version1.0\AppiumForWindows-1.1.0.0\Appium\node_modules\appium\.dumpsys.log
> ERROR: debug: Screen already unlocked, continuing.
> info: Pushing command to appium work queue: ["getDataDir",{}]
> info: [BOOTSTRAP] [info] Got data from client: {"cmd":"action","action":"getDataDir","params":{}}
> ERROR: debug: dataDir set to: /data/local/tmp
> info: [BOOTSTRAP] [info] Got command of type ACTION
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 shell "am start -S -a android.intent.action.MAIN -c android.intent.category.LAUNCHER -f 0x10200000 -n com.verisign.mvip.main/com.verisign.mvip.main.MainActivity"
> info: [BOOTSTRAP] [debug] Got command action: getDataDir
> info: [BOOTSTRAP] [info] Returning result: {"value":"\/data\/local\/tmp","status":0}
> info: Waiting for pkg "com.verisign.mvip.main" and activity "com.verisign.mvip.main.MainActivity" to be focused
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 shell "dumpsys window windows"
> info: Getting focused package and activity
> info: Getting focused package and activity
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 shell "dumpsys window windows"
> info: Getting focused package and activity
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 shell "dumpsys window windows"
> ERROR: error: com.verisign.mvip.main/.MainActivity never started. Current: com.verisign.mvip.main/.EulaActivity
> info: Stopping logcat capture
> ERROR: debug: Logcat terminated with code null, signal SIGTERM
> info: [BOOTSTRAP] [info] Got data from client: {"cmd":"shutdown"}
> info: [BOOTSTRAP] [info] Got command of type SHUTDOWN
> info: Sent shutdown command, waiting for UiAutomator to stop...
> info: [BOOTSTRAP] [info] Returning result: {"value":"OK, shutting down","status":0}
> info: [BOOTSTRAP] [info] Closed client connection
> info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: current=1
> info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: id=UiAutomatorTestRunner
> info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: class=io.appium.android.bootstrap.Bootstrap
> info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: stream=.
> info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: numtests=1
> info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: test=testRunServer
> info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS_CODE: 0
> info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: stream=
> info: [UIAUTOMATOR STDOUT] Test results for WatcherResultPrinter=.
> info: [UIAUTOMATOR STDOUT] Time: 23.831
> info: [UIAUTOMATOR STDOUT] OK (1 test)
> info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS_CODE: -1
> ERROR: error: Failed to start an Appium session, err was: Error: com.verisign.mvip.main/.MainActivity never started. Current: com.verisign.mvip.main/.EulaActivity
> info: Cleaning up android objects
> info: Cleaning up appium session
> info: Error: com.verisign.mvip.main/.MainActivity never started. Current: com.verisign.mvip.main/.EulaActivity
> at null.<anonymous> (D:\Appium-version1.0\AppiumForWindows-1.1.0.0\Appium\node_modules\appium\lib\devices\android\adb.js:1276:12)
> at null.<anonymous> (D:\Appium-version1.0\AppiumForWindows-1.1.0.0\Appium\node_modules\appium\lib\devices\android\adb.js:1221:7)
> at D:\Appium-version1.0\AppiumForWindows-1.1.0.0\Appium\node_modules\appium\lib\devices\android\adb.js:153: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)
> info: Responding to client with error: {"status":33,"value":{"message":"A new session could not be created. (Original error: com.verisign.mvip.main/.MainActivity never started. Current: com.verisign.mvip.main/.EulaActivity)","origValue":"com.verisign.mvip.main/.MainActivity never started. Current: com.verisign.mvip.main/.EulaActivity"},"sessionId":null}
> POST /wd/hub/session 500 54094ms - 344b
Could you please correct me if i have done any mistakes in my code .. I am using the latest appium version 1.1.0
Please help .
Thanks
Siva
Isaac Murchie
Jun 2, 2014, 1:26:22 PM6/2/14
to Siva Subramanian, appium-...@googlegroups.com, menezes...@gmail.com, Sangeetha Srinivasan
These are wrong:
capabilities.setCapability("app-package", "com.verisign.mvip.main");
capabilities.setCapability("app-wait-activity", ".EulaActivity");
capabilities.setCapability("app-activity", "./MainActivity");
You need to use appPackage, appActivity, and appWaitActivity in Appium 1.0/1.1. See the docs (https://github.com/appium/appium/blob/master/docs/en/caps.md#android-only).
Siva Subramanian
Jun 2, 2014, 1:58:02 PM6/2/14
to Isaac Murchie, appium-...@googlegroups.com, menezes.diana22, Sangeetha Srinivasan
My bad !!! I didnt look into it properly . Thanks a lot for your help ....
Now appium session is creating successfully.
One last question, Can we launch any intermediate activity ( other than main activity) for creating a appium session.
I was able to do it during the lower version of appium. But now i am unable to do it from version 0.18 to version 1.1
Could you please clarify it .
Thanks
Siva
Siva Subramanian
Jun 2, 2014, 2:33:28 PM6/2/14
to Isaac Murchie, appium-...@googlegroups.com, menezes.diana22, Sangeetha Srinivasan
Hi Issac,
Our app has some list of activites below .
com.verisign.mvip.main.EulaActivity
com.verisign.mvip.main.MainActivity -- Launching activity
com.verisign.mvip.main.MainScreenActivity
com.verisign.mvip.main.ActivationActivity
com.verisign.mvip.main.HowtoUseActivity
com.verisign.mvip.main.SettingsActivity
Our app functions such as ... Main Activity is a dummy activity which doesnt have any page on it.
It will just invoke the EULA Activity and clicking on button "YES" in EULA activity , will take us to the "Activation Activity" Screen
and that in turn ends up in MainScreen Activity Page at the end(which is the home page of our application).
Previously when i was using appium version 0.14 or 0.16, i was able to launch the activation activity directly without any issues. Because i dont want to
automate Main activity as it doesnt have any UI physically and EULA activity is also not of so importance for my automation.
Now from the appium version 0.18 onwards, it is always defaulting to the MainActivity , even though i tried to launch the Activation activity directly.
Why this is happening ? Why i am unable to launch the Activation activity directly by skipping the Main activity, which is nothing but a dummy page in
my app .
Hope you understand my problem.
Could you please kindly help me in clarifying this issue, by reading the above mail patiently.
Thanks
Siva
On Mon, Jun 2, 2014 at 11:39 PM, Isaac Murchie <is...@saucelabs.com> wrote:
I'm sure you can. I'm not sure how to do it, though.What was the code like to do it in 0.18?
Isaac Murchie
Jun 2, 2014, 2:37:19 PM6/2/14
to Siva Subramanian, appium-...@googlegroups.com
Does it not work to set the "appActivity" to one of the others?
Rather than
try
Siva Subramanian
Jun 2, 2014, 2:49:37 PM6/2/14
to Isaac Murchie, appium-...@googlegroups.com
Yeah the same i tried .
if i am trying with some other activity other than Main Activity, it is not launching the specified activity correctly and session doesnt gets created
successfully. :(
here are my observations
if we use
capabilities.setCapability("app-activity", "./HowtoUseActivity");
Then it will always launch the Main Activity, regardless of whatever may be the activity name given in the
capabilities.
if we use ,
capabilities.setCapability("appActivity", "./HowtoUseActivity");
Then it will not launch any activity.The mobile phone will be idle.
Could you please confirm it as an issue ?
Thanks
Siva
Isaac Murchie
Jun 2, 2014, 2:50:32 PM6/2/14
to Siva Subramanian, appium-...@googlegroups.com
Can you provide the server log for the second case?
Siva Subramanian
Jun 2, 2014, 3:04:46 PM6/2/14
to Isaac Murchie, appium-...@googlegroups.com
Sure . I am using Appium 1.1 version . I am running the tests on a real device with android version 4.3.
I have highlighted the error in yellow color in the server logs. Even though the activity name is correct , it says please try with the launch able activity.
My Code :
WebDriver driver;
DesiredCapabilities capabilities = new DesiredCapabilities();
capabilities.setCapability(CapabilityType.BROWSER_NAME,"");
capabilities.setCapability("newCommandTimeout","300");
capabilities.setCapability("device","Android");
capabilities.setCapability(CapabilityType.VERSION,"4.3");
capabilities.setCapability(CapabilityType.PLATFORM,"WINDOWS");
capabilities.setCapability(CapabilityType.SUPPORTS_JAVASCRIPT,true);
capabilities.setCapability(CapabilityType.HAS_TOUCHSCREEN,true);
capabilities.setCapability(CapabilityType.ACCEPT_SSL_CERTS,true);
capabilities.setCapability("app", "D:\\adt-bundle-windows-x86_64-20131030\\adt-bundle-windows-x86_64-20131030\\sdk\\platform-tools\\mvip-Android-2.2.apk");
capabilities.setCapability("appPackage", "com.verisign.mvip.main"); // This is package name of your app (you can get it from apk info app)
capabilities.setCapability("appActivity", "com.verisign.mvip.main.ActivationActivity"); ( Trying to launch other than main activity)
//Create RemoteWebDriver instance and connect to the Appium server.
driver = new RemoteWebDriver(new URL("http://127.0.0.1:4723/wd/hub"), capabilities);
driver.manage().timeouts().implicitlyWait(80, TimeUnit.SECONDS);
SERVER LOGS :
> Starting Node Server
> info: Welcome to Appium v1.1.0 (REV e433bbc31511f199287db7724e1ce692bcb32117)
> info: Appium REST http interface listener started on 127.0.0.1:4723
> info: socket.io started
> info: Non-default server args: {"address":"127.0.0.1","logNoColors":true,"platformName":"Android","platformVersion":"18","automationName":"Appium"}
> ERROR: debug: Appium request initiated at /wd/hub/session
> info: Using local app from desired caps: D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\mvip-Android-2.2.apk
> ERROR: debug: Request received with params: {"desiredCapabilities":{"newCommandTimeout":"300","platform":"WINDOWS","app":"D:\\adt-bundle-windows-x86_64-20131030\\adt-bundle-windows-x86_64-20131030\\sdk\\platform-tools\\mvip-Android-2.2.apk","javascriptEnabled":true,"acceptSslCerts":true,"browserName":"","appActivity":"com.verisign.mvip.main.HowToUseActivity","device":"Android","hasTouchScreen":true,"appPackage":"com.verisign.mvip.main","version":"4.3"}}
> info: Creating new appium session 93c2243f-d2df-4abc-bc54-10fe25a564ff
> ERROR: debug: Using fast reset? true
> info: Starting android appium
> info: Preparing device for session
> info: Checking whether app is actually present
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" devices
> info: Checking whether adb is present
> info: [ADB] Using adb from D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe
> info: Trying to find a connected android device
> info: [ADB] Getting connected devices...
> info: [ADB] 1 device(s) connected
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 wait-for-device
> info: Setting device id to 7d746172
> info: [ADB] Waiting for device to be ready and to respond to shell commands (timeout = 5)
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 shell "echo 'ready'"
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 kill-server
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 devices
> info: [ADB] Getting connected devices...
> info: [ADB] 1 device(s) connected
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 wait-for-device
> info: [ADB] Waiting for device to be ready and to respond to shell commands (timeout = 5)
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 shell "echo 'ready'"
> info: Starting logcat capture
> info: Getting device API level
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 shell "getprop ro.build.version.sdk"
> info: Device is at API Level 18
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 shell "getprop persist.sys.language"
> ERROR: debug: Current device language: en
> ERROR: debug: java -jar "D:\Appium-version1.0\AppiumForWindows-1.1.0.0\Appium\node_modules\appium\lib\devices\android\helpers\strings_from_apk.jar" "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\mvip-Android-2.2.apk" "C:\Windows\Temp\com.verisign.mvip.main" en
> info: No strings.xml for language 'en', getting default strings.xml
> ERROR: debug: java -jar "D:\Appium-version1.0\AppiumForWindows-1.1.0.0\Appium\node_modules\appium\lib\devices\android\helpers\strings_from_apk.jar" "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\mvip-Android-2.2.apk" "C:\Windows\Temp\com.verisign.mvip.main"
> ERROR: debug: Exception in thread "main" java.lang.Exception: Output is not an existing readable directory.
> ERROR: at strings.StringsXML.e(StringsXML.java:105)
> ERROR: at strings.StringsXML.main(StringsXML.java:140)
> ERROR:
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 shell "echo '{}' > /data/local/tmp/strings.json"
> info: Checking whether aapt is present
> ERROR: debug: processFromManifest: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\build-tools\android-4.4\aapt.exe" dump xmltree "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\mvip-Android-2.2.apk" AndroidManifest.xml
> info: [ADB] Using aapt from D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\build-tools\android-4.4\aapt.exe
> ERROR: debug: Set app process to: isign.mvip.main
> ERROR: debug: Not uninstalling app since server not started with --full-reset
> ERROR: debug: Checking app cert for D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\mvip-Android-2.2.apk: java -jar "D:\Appium-version1.0\AppiumForWindows-1.1.0.0\Appium\node_modules\appium\lib\devices\android\helpers\verify.jar" "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\mvip-Android-2.2.apk"
> ERROR: debug: App already signed.
> info: Zip-aligning D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\mvip-Android-2.2.apk
> ERROR: debug: zipAlignApk: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\tools\zipalign.exe" -f 4 "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\mvip-Android-2.2.apk" "C:\Users\SIVASU~1\AppData\Local\Temp\appium11453-9308-f0ama6.tmp"
> info: Checking whether zipalign is present
> info: [ADB] Using zipalign from D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\tools\zipalign.exe
> info: MD5 for app is 050044ebd10440cdcc1e41c9d12641c0
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 shell "ls /data/local/tmp/050044ebd10440cdcc1e41c9d12641c0.apk"
> ERROR: debug: Getting install status for com.verisign.mvip.main
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 shell "pm list packages -3 com.verisign.mvip.main"
> info: [ADB] App is installed
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 shell "am force-stop com.verisign.mvip.main"
> info: Running fast reset (stop and clear)
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 shell "pm clear com.verisign.mvip.main"
> info: [ADB] Forwarding system:4724 to device:4724
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 forward tcp:4724 tcp:4724
> ERROR: debug: Pushing appium bootstrap to device...
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 push "D:\\Appium-version1.0\\AppiumForWindows-1.1.0.0\\Appium\\node_modules\\appium\\build\\android_bootstrap\\AppiumBootstrap.jar" /data/local/tmp/
> ERROR: debug: Pushing unlock helper app to device...
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 install "D:\Appium-version1.0\AppiumForWindows-1.1.0.0\Appium\node_modules\appium\build\unlock_apk\unlock_apk-debug.apk"
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 shell "ps 'uiautomator'"
> info: Getting all processes with 'uiautomator'
> info: No matching processes found
> ERROR: debug: spawning: D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe -s 7d746172 shell uiautomator runtest AppiumBootstrap.jar -c io.appium.android.bootstrap.Bootstrap
> info: Running bootstrap
> info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: current=1
> info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: id=UiAutomatorTestRunner
> info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: class=io.appium.android.bootstrap.Bootstrap
> info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: stream=
> info: [UIAUTOMATOR STDOUT] io.appium.android.bootstrap.Bootstrap:
> info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: numtests=1
> info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: test=testRunServer
> info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS_CODE: 1
> info: [BOOTSTRAP] [info] Socket opened on port 4724
> ERROR: debug: Waking up device if it's not alive
> info: [BOOTSTRAP] [info] Appium Socket Server Ready
> info: [BOOTSTRAP] [info] Loading json...
> info: [BOOTSTRAP] [info] json loading complete.
> info: [BOOTSTRAP] [info] Registered crash watchers.
> info: Pushing command to appium work queue: ["wake",{}]
> info: [BOOTSTRAP] [info] Client connected
> info: [BOOTSTRAP] [info] Got data from client: {"cmd":"action","action":"wake","params":{}}
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 shell "dumpsys window"
> info: [BOOTSTRAP] [info] Got command of type ACTION
> info: [BOOTSTRAP] [debug] Got command action: wake
> info: [BOOTSTRAP] [info] Returning result: {"value":true,"status":0}
> info: Writing dumpsys output to D:\Appium-version1.0\AppiumForWindows-1.1.0.0\Appium\node_modules\appium\.dumpsys.log
> ERROR: debug: Screen already unlocked, continuing.
> info: Pushing command to appium work queue: ["getDataDir",{}]
> info: [BOOTSTRAP] [info] Got data from client: {"cmd":"action","action":"getDataDir","params":{}}
> info: [BOOTSTRAP] [info] Got command of type ACTION
> info: [BOOTSTRAP] [debug] Got command action: getDataDir
> info: [BOOTSTRAP] [info] Returning result: {"value":"\/data\/local\/tmp","status":0}
> ERROR: debug: dataDir set to: /data/local/tmp
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 shell "am start -S -a android.intent.action.MAIN -c android.intent.category.LAUNCHER -f 0x10200000 -n com.verisign.mvip.main/com.verisign.mvip.main.HowToUseActivity"
> info: We tried to start an activity that doesn't exist, retrying with . prepended to activity
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 shell "am start -S -a android.intent.action.MAIN -c android.intent.category.LAUNCHER -f 0x10200000 -n com.verisign.mvip.main/.com.verisign.mvip.main.HowToUseActivity"
> ERROR: error: Activity used to start app doesn't exist or cannot be launched! Make sure it exists and is a launchable activity
> info: Stopping logcat capture
> ERROR: debug: Logcat terminated with code null, signal SIGTERM
> info: [BOOTSTRAP] [info] Got data from client: {"cmd":"shutdown"}
> info: [BOOTSTRAP] [info] Got command of type SHUTDOWN
> info: [BOOTSTRAP] [info] Returning result: {"value":"OK, shutting down","status":0}
> info: Sent shutdown command, waiting for UiAutomator to stop...
> info: [BOOTSTRAP] [info] Closed client connection
> info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: current=1
> info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: id=UiAutomatorTestRunner
> info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: class=io.appium.android.bootstrap.Bootstrap
> info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: stream=.
> info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: numtests=1
> info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: test=testRunServer
> info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS_CODE: 0
> info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: stream=
> info: [UIAUTOMATOR STDOUT] Test results for WatcherResultPrinter=.
> info: [UIAUTOMATOR STDOUT] Time: 3.96
> info: [UIAUTOMATOR STDOUT] OK (1 test)
> info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS_CODE: -1
> info: UiAutomator shut down normally
> ERROR: error: Failed to start an Appium session, err was: Error: Activity used to start app doesn't exist or cannot be launched! Make sure it exists and is a launchable activity
> info: Cleaning up android objects
> info: Cleaning up appium session
> info: Error: Activity used to start app doesn't exist or cannot be launched! Make sure it exists and is a launchable activity
> at null.<anonymous> (D:\Appium-version1.0\AppiumForWindows-1.1.0.0\Appium\node_modules\appium\lib\devices\android\adb.js:1112:19)
> at D:\Appium-version1.0\AppiumForWindows-1.1.0.0\Appium\node_modules\appium\lib\devices\android\adb.js:153: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)
> info: Responding to client with error: {"status":33,"value":{"message":"A new session could not be created. (Original error: Activity used to start app doesn't exist or cannot be launched! Make sure it exists and is a launchable activity)","origValue":"Activity used to start app doesn't exist or cannot be launched! Make sure it exists and is a launchable activity"},"sessionId":null}
> POST /wd/hub/session 500 43753ms - 374b
Thanks
Siva
Isaac Murchie
Jun 2, 2014, 3:07:35 PM6/2/14
to Siva Subramanian, appium-...@googlegroups.com
Don't use the fully qualified classname for the activity. the "appPackage" capability sets the path.
Instead of
capabilities.setCapability("appActivity", "com.verisign.mvip.main.ActivationActivity");
use
capabilities.setCapability("appActivity", "ActivationActivity");
Siva Subramanian
Jun 2, 2014, 3:19:58 PM6/2/14
to Isaac Murchie, appium-...@googlegroups.com
Hi Issac,
Even after using the activity name ,
capabilities.setCapability("app", "D:\\adt-bundle-windows-x86_64-20131030\\adt-bundle-windows-x86_64-20131030\\sdk\\platform-tools\\mvip-Android-2.2.apk");//If you want to run it on emulator.
capabilities.setCapability("appPackage", "com.verisign.mvip.main"); // This is package name of your app (you can get it from apk info app)
capabilities.setCapability("appActivity", "ActivationActivity");
I am getting the below error .
SERVER LOGS
> Starting Node Server
> info: Welcome to Appium v1.1.0 (REV e433bbc31511f199287db7724e1ce692bcb32117)
> info: Appium REST http interface listener started on 127.0.0.1:4723
> info: socket.io started
> info: Non-default server args: {"address":"127.0.0.1","logNoColors":true,"platformName":"Android","platformVersion":"18","automationName":"Appium"}
> ERROR: debug: Appium request initiated at /wd/hub/session
> info: Using local app from desired caps: D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\mvip-Android-2.2.apk
> ERROR: debug: Request received with params: {"desiredCapabilities":{"newCommandTimeout":"300","platform":"WINDOWS","app":"D:\\adt-bundle-windows-x86_64-20131030\\adt-bundle-windows-x86_64-20131030\\sdk\\platform-tools\\mvip-Android-2.2.apk","javascriptEnabled":true,"acceptSslCerts":true,"browserName":"","appActivity":"ActivationActivity","device":"Android","hasTouchScreen":true,"appPackage":"com.verisign.mvip.main","version":"4.3"}}
> info: Creating new appium session c5235e5d-83c8-4dc9-93e5-33f251f14acd
> ERROR: debug: Using fast reset? true
> info: Starting android appium
> info: Preparing device for session
> info: Checking whether app is actually present
> info: Checking whether adb is present
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" devices
> info: [ADB] Using adb from D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe
> info: Trying to find a connected android device
> info: [ADB] Getting connected devices...
> info: [ADB] 1 device(s) connected
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 wait-for-device
> info: Setting device id to 7d746172
> info: [ADB] Waiting for device to be ready and to respond to shell commands (timeout = 5)
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 shell "echo 'ready'"
> info: Starting logcat capture
> info: Getting device API level
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 shell "getprop ro.build.version.sdk"
> info: Device is at API Level 18
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 shell "getprop persist.sys.language"
> ERROR: debug: Current device language: en
> ERROR: debug: java -jar "D:\Appium-version1.0\AppiumForWindows-1.1.0.0\Appium\node_modules\appium\lib\devices\android\helpers\strings_from_apk.jar" "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\mvip-Android-2.2.apk" "C:\Windows\Temp\com.verisign.mvip.main" en
> info: No strings.xml for language 'en', getting default strings.xml
> ERROR: debug: java -jar "D:\Appium-version1.0\AppiumForWindows-1.1.0.0\Appium\node_modules\appium\lib\devices\android\helpers\strings_from_apk.jar" "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\mvip-Android-2.2.apk" "C:\Windows\Temp\com.verisign.mvip.main"
> warn: Error getting strings.xml from apk
> ERROR: debug: Exception in thread "main" java.lang.Exception: Output is not an existing readable directory.
> ERROR: at strings.StringsXML.e(StringsXML.java:105)
> ERROR: at strings.StringsXML.main(StringsXML.java:140)
> ERROR:
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 shell "echo '{}' > /data/local/tmp/strings.json"
> info: Checking whether aapt is present
> ERROR: debug: processFromManifest: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\build-tools\android-4.4\aapt.exe" dump xmltree "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\mvip-Android-2.2.apk" AndroidManifest.xml
> info: [ADB] Using aapt from D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\build-tools\android-4.4\aapt.exe
> ERROR: debug: Set app process to: isign.mvip.main
> ERROR: debug: Not uninstalling app since server not started with --full-reset
> ERROR: debug: Checking app cert for D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\mvip-Android-2.2.apk: java -jar "D:\Appium-version1.0\AppiumForWindows-1.1.0.0\Appium\node_modules\appium\lib\devices\android\helpers\verify.jar" "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\mvip-Android-2.2.apk"
> ERROR: debug: App already signed.
> info: Zip-aligning D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\mvip-Android-2.2.apk
> ERROR: debug: zipAlignApk: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\tools\zipalign.exe" -f 4 "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\mvip-Android-2.2.apk" "C:\Users\SIVASU~1\AppData\Local\Temp\appium11453-8604-1s26w5x.tmp"
> info: Checking whether zipalign is present
> info: [ADB] Using zipalign from D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\tools\zipalign.exe
> info: MD5 for app is 050044ebd10440cdcc1e41c9d12641c0
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 shell "ls /data/local/tmp/050044ebd10440cdcc1e41c9d12641c0.apk"
> ERROR: debug: Getting install status for com.verisign.mvip.main
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 shell "pm list packages -3 com.verisign.mvip.main"
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 shell "am force-stop com.verisign.mvip.main"
> info: Running fast reset (stop and clear)
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 shell "pm clear com.verisign.mvip.main"
> info: [ADB] Forwarding system:4724 to device:4724
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 forward tcp:4724 tcp:4724
> ERROR: debug: Pushing appium bootstrap to device...
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 push "D:\\Appium-version1.0\\AppiumForWindows-1.1.0.0\\Appium\\node_modules\\appium\\build\\android_bootstrap\\AppiumBootstrap.jar" /data/local/tmp/
> ERROR: debug: Pushing unlock helper app to device...
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 install "D:\Appium-version1.0\AppiumForWindows-1.1.0.0\Appium\node_modules\appium\build\unlock_apk\unlock_apk-debug.apk"
> info: Attempting to kill all 'uiautomator' processes
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 shell "ps 'uiautomator'"
> info: Getting all processes with 'uiautomator'
> info: No matching processes found
> ERROR: debug: spawning: D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe -s 7d746172 shell uiautomator runtest AppiumBootstrap.jar -c io.appium.android.bootstrap.Bootstrap
> info: Running bootstrap
> info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: current=1
> info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: id=UiAutomatorTestRunner
> info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: class=io.appium.android.bootstrap.Bootstrap
> info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: stream=
> info: [UIAUTOMATOR STDOUT] io.appium.android.bootstrap.Bootstrap:
> info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: numtests=1
> info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: test=testRunServer
> info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS_CODE: 1
> info: [BOOTSTRAP] [info] Socket opened on port 4724
> info: [BOOTSTRAP] [info] Appium Socket Server Ready
> ERROR: debug: Waking up device if it's not alive
> info: [BOOTSTRAP] [info] Loading json...
> info: [BOOTSTRAP] [info] json loading complete.
> info: [BOOTSTRAP] [info] Registered crash watchers.
> info: Pushing command to appium work queue: ["wake",{}]
> info: [BOOTSTRAP] [info] Client connected
> info: [BOOTSTRAP] [info] Got data from client: {"cmd":"action","action":"wake","params":{}}
> info: [BOOTSTRAP] [info] Got command of type ACTION
> info: [BOOTSTRAP] [debug] Got command action: wake
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 shell "dumpsys window"
> info: [BOOTSTRAP] [info] Returning result: {"value":true,"status":0}
> info: Writing dumpsys output to D:\Appium-version1.0\AppiumForWindows-1.1.0.0\Appium\node_modules\appium\.dumpsys.log
> ERROR: debug: Screen already unlocked, continuing.
> info: Pushing command to appium work queue: ["getDataDir",{}]
> info: [BOOTSTRAP] [info] Got data from client: {"cmd":"action","action":"getDataDir","params":{}}
> info: [BOOTSTRAP] [info] Got command of type ACTION
> info: [BOOTSTRAP] [debug] Got command action: getDataDir
> ERROR: debug: dataDir set to: /data/local/tmp
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 shell "am start -S -a android.intent.action.MAIN -c android.intent.category.LAUNCHER -f 0x10200000 -n com.verisign.mvip.main/ActivationActivity"
> info: We tried to start an activity that doesn't exist, retrying with . prepended to activity
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 shell "am start -S -a android.intent.action.MAIN -c android.intent.category.LAUNCHER -f 0x10200000 -n com.verisign.mvip.main/.ActivationActivity"
> info: Waiting for pkg "com.verisign.mvip.main" and activity "ActivationActivity" to be focused
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 shell "dumpsys window windows"
> info: Getting focused package and activity
> info: Getting focused package and activity
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 shell "dumpsys window windows"
> info: Getting focused package and activity
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 shell "dumpsys window windows"
> info: Getting focused package and activity
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 shell "dumpsys window windows"
> info: Getting focused package and activity
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 shell "dumpsys window windows"
> info: Getting focused package and activity
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 shell "dumpsys window windows"
> info: Getting focused package and activity
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 shell "dumpsys window windows"
> info: Getting focused package and activity
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 shell "dumpsys window windows"
> info: Getting focused package and activity
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 shell "dumpsys window windows"
> info: Getting focused package and activity
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 shell "dumpsys window windows"
> info: Getting focused package and activity
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 shell "dumpsys window windows"
> info: Getting focused package and activity
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 shell "dumpsys window windows"
> ERROR: error: com.verisign.mvip.main/ActivationActivity never started. Current: com.sec.android.app.launcher/com.android.launcher2.Launcher
> info: Stopping logcat capture
> ERROR: debug: Logcat terminated with code null, signal SIGTERM
> info: Sent shutdown command, waiting for UiAutomator to stop...
> info: [BOOTSTRAP] [info] Got data from client: {"cmd":"shutdown"}
> info: [BOOTSTRAP] [info] Got command of type SHUTDOWN
> info: [BOOTSTRAP] [info] Returning result: {"value":"OK, shutting down","status":0}
> info: [BOOTSTRAP] [info] Closed client connection
> info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: current=1
> info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: id=UiAutomatorTestRunner
> info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: class=io.appium.android.bootstrap.Bootstrap
> info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: stream=.
> info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: numtests=1
> info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: test=testRunServer
> info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS_CODE: 0
> info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: stream=
> info: [UIAUTOMATOR STDOUT] Test results for WatcherResultPrinter=.
> info: [UIAUTOMATOR STDOUT] Time: 34.695
> info: [UIAUTOMATOR STDOUT] OK (1 test)
> info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS_CODE: -1
> info: UiAutomator shut down normally
> ERROR: error: Failed to start an Appium session, err was: Error: com.verisign.mvip.main/ActivationActivity never started. Current: com.sec.android.app.launcher/com.android.launcher2.Launcher
> info: Cleaning up android objects
> info: Cleaning up appium session
> info: Error: com.verisign.mvip.main/ActivationActivity never started. Current: com.sec.android.app.launcher/com.android.launcher2.Launcher
> at null.<anonymous> (D:\Appium-version1.0\AppiumForWindows-1.1.0.0\Appium\node_modules\appium\lib\devices\android\adb.js:1276:12)
> at null.<anonymous> (D:\Appium-version1.0\AppiumForWindows-1.1.0.0\Appium\node_modules\appium\lib\devices\android\adb.js:1221:7)
> at D:\Appium-version1.0\AppiumForWindows-1.1.0.0\Appium\node_modules\appium\lib\devices\android\adb.js:153: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)
> info: Responding to client with error: {"status":33,"value":{"message":"A new session could not be created. (Original error: com.verisign.mvip.main/ActivationActivity never started. Current: com.sec.android.app.launcher/com.android.launcher2.Launcher)","origValue":"com.verisign.mvip.main/ActivationActivity never started. Current: com.sec.android.app.launcher/com.android.launcher2.Launcher"},"sessionId":null}
> POST /wd/hub/session 500 45832ms - 400b
Could you please look into the logs.
Thanks
Siva
Isaac Murchie
Jun 2, 2014, 3:22:42 PM6/2/14
to Siva Subramanian, appium-...@googlegroups.com
Sorry, I forgot the dot. You'll probably need ".ActivationActivity".
Siva Subramanian
Jun 2, 2014, 3:25:56 PM6/2/14
to Isaac Murchie, appium-...@googlegroups.com
Hi Isaac,
Still the same error .
SERVER_LOGS:
> Starting Node Server
> info: Welcome to Appium v1.1.0 (REV e433bbc31511f199287db7724e1ce692bcb32117)
> info: Appium REST http interface listener started on 127.0.0.1:4723
> info: socket.io started
> info: Non-default server args: {"address":"127.0.0.1","logNoColors":true,"platformName":"Android","platformVersion":"18","automationName":"Appium"}
> ERROR: debug: Appium request initiated at /wd/hub/session
> info: Using local app from desired caps: D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\mvip-Android-2.2.apk
> ERROR: debug: Request received with params: {"desiredCapabilities":{"newCommandTimeout":"300","platform":"WINDOWS","app":"D:\\adt-bundle-windows-x86_64-20131030\\adt-bundle-windows-x86_64-20131030\\sdk\\platform-tools\\mvip-Android-2.2.apk","javascriptEnabled":true,"acceptSslCerts":true,"browserName":"","appActivity":".ActivationActivity","device":"Android","hasTouchScreen":true,"appPackage":"com.verisign.mvip.main","version":"4.3"}}
> info: Creating new appium session 85d0743a-f9d7-4ec8-8b3f-6bbafb9ff285
> ERROR: debug: Using fast reset? true
> info: Starting android appium
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" devices
> info: Preparing device for session
> info: Checking whether app is actually present
> info: Checking whether adb is present
> info: [ADB] Using adb from D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe
> info: Trying to find a connected android device
> info: [ADB] Getting connected devices...
> info: [ADB] 1 device(s) connected
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 wait-for-device
> info: Setting device id to 7d746172
> info: [ADB] Waiting for device to be ready and to respond to shell commands (timeout = 5)
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 shell "echo 'ready'"
> info: Starting logcat capture
> info: Getting device API level
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 shell "getprop ro.build.version.sdk"
> info: Device is at API Level 18
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 shell "getprop persist.sys.language"
> ERROR: debug: Current device language: en
> ERROR: debug: java -jar "D:\Appium-version1.0\AppiumForWindows-1.1.0.0\Appium\node_modules\appium\lib\devices\android\helpers\strings_from_apk.jar" "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\mvip-Android-2.2.apk" "C:\Windows\Temp\com.verisign.mvip.main" en
> ERROR: debug: java -jar "D:\Appium-version1.0\AppiumForWindows-1.1.0.0\Appium\node_modules\appium\lib\devices\android\helpers\strings_from_apk.jar" "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\mvip-Android-2.2.apk" "C:\Windows\Temp\com.verisign.mvip.main"
> warn: Error getting strings.xml from apk
> ERROR: debug: Exception in thread "main" java.lang.Exception: Output is not an existing readable directory.
> ERROR: at strings.StringsXML.e(StringsXML.java:105)
> ERROR: at strings.StringsXML.main(StringsXML.java:140)
> ERROR:
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 shell "echo '{}' > /data/local/tmp/strings.json"
> info: Checking whether aapt is present
> ERROR: debug: processFromManifest: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\build-tools\android-4.4\aapt.exe" dump xmltree "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\mvip-Android-2.2.apk" AndroidManifest.xml
> info: [ADB] Using aapt from D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\build-tools\android-4.4\aapt.exe
> ERROR: debug: Set app process to: isign.mvip.main
> ERROR: debug: Not uninstalling app since server not started with --full-reset
> ERROR: debug: Checking app cert for D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\mvip-Android-2.2.apk: java -jar "D:\Appium-version1.0\AppiumForWindows-1.1.0.0\Appium\node_modules\appium\lib\devices\android\helpers\verify.jar" "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\mvip-Android-2.2.apk"
> ERROR: debug: App already signed.
> info: Zip-aligning D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\mvip-Android-2.2.apk
> ERROR: debug: zipAlignApk: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\tools\zipalign.exe" -f 4 "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\mvip-Android-2.2.apk" "C:\Users\SIVASU~1\AppData\Local\Temp\appium11453-7272-q60w9u.tmp"
> info: Checking whether zipalign is present
> info: [ADB] Using zipalign from D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\tools\zipalign.exe
> info: MD5 for app is 050044ebd10440cdcc1e41c9d12641c0
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 shell "ls /data/local/tmp/050044ebd10440cdcc1e41c9d12641c0.apk"
> ERROR: debug: Getting install status for com.verisign.mvip.main
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 shell "pm list packages -3 com.verisign.mvip.main"
> info: [ADB] App is installed
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 shell "am force-stop com.verisign.mvip.main"
> info: Running fast reset (stop and clear)
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 shell "pm clear com.verisign.mvip.main"
> info: [ADB] Forwarding system:4724 to device:4724
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 forward tcp:4724 tcp:4724
> ERROR: debug: Pushing appium bootstrap to device...
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 push "D:\\Appium-version1.0\\AppiumForWindows-1.1.0.0\\Appium\\node_modules\\appium\\build\\android_bootstrap\\AppiumBootstrap.jar" /data/local/tmp/
> ERROR: debug: Pushing unlock helper app to device...
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 install "D:\Appium-version1.0\AppiumForWindows-1.1.0.0\Appium\node_modules\appium\build\unlock_apk\unlock_apk-debug.apk"
> info: Attempting to kill all 'uiautomator' processes
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 shell "ps 'uiautomator'"
> info: Getting all processes with 'uiautomator'
> info: No matching processes found
> ERROR: debug: spawning: D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe -s 7d746172 shell uiautomator runtest AppiumBootstrap.jar -c io.appium.android.bootstrap.Bootstrap
> info: Running bootstrap
> info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: current=1
> info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: id=UiAutomatorTestRunner
> info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: class=io.appium.android.bootstrap.Bootstrap
> info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: stream=
> info: [UIAUTOMATOR STDOUT] io.appium.android.bootstrap.Bootstrap:
> info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: numtests=1
> info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: test=testRunServer
> info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS_CODE: 1
> info: [BOOTSTRAP] [info] Socket opened on port 4724
> ERROR: debug: Waking up device if it's not alive
> info: [BOOTSTRAP] [info] Appium Socket Server Ready
> info: [BOOTSTRAP] [info] Loading json...
> info: [BOOTSTRAP] [info] json loading complete.
> info: Pushing command to appium work queue: ["wake",{}]
> info: [BOOTSTRAP] [info] Registered crash watchers.
> info: [BOOTSTRAP] [info] Client connected
> info: [BOOTSTRAP] [info] Got data from client: {"cmd":"action","action":"wake","params":{}}
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 shell "dumpsys window"
> info: [BOOTSTRAP] [info] Got command of type ACTION
> info: [BOOTSTRAP] [debug] Got command action: wake
> info: [BOOTSTRAP] [info] Returning result: {"value":true,"status":0}
> info: Writing dumpsys output to D:\Appium-version1.0\AppiumForWindows-1.1.0.0\Appium\node_modules\appium\.dumpsys.log
> info: Pushing command to appium work queue: ["getDataDir",{}]
> ERROR: debug: Screen already unlocked, continuing.
> info: [BOOTSTRAP] [info] Got data from client: {"cmd":"action","action":"getDataDir","params":{}}
> info: [BOOTSTRAP] [info] Got command of type ACTION
> info: [BOOTSTRAP] [debug] Got command action: getDataDir
> info: [BOOTSTRAP] [info] Returning result: {"value":"\/data\/local\/tmp","status":0}
> ERROR: debug: dataDir set to: /data/local/tmp
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 shell "am start -S -a android.intent.action.MAIN -c android.intent.category.LAUNCHER -f 0x10200000 -n com.verisign.mvip.main/.ActivationActivity"
> info: Waiting for pkg "com.verisign.mvip.main" and activity ".ActivationActivity" to be focused
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 shell "dumpsys window windows"
> info: Getting focused package and activity
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 shell "dumpsys window windows"
> info: Getting focused package and activity
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 shell "dumpsys window windows"
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 shell "dumpsys window windows"
> ERROR: error: com.verisign.mvip.main/.ActivationActivity never started. Current: com.sec.android.app.launcher/com.android.launcher2.Launcher
> info: Stopping logcat capture
> ERROR: debug: Logcat terminated with code null, signal SIGTERM
> info: [BOOTSTRAP] [info] Got data from client: {"cmd":"shutdown"}
> info: Sent shutdown command, waiting for UiAutomator to stop...
> info: [BOOTSTRAP] [info] Got command of type SHUTDOWN
> info: [BOOTSTRAP] [info] Returning result: {"value":"OK, shutting down","status":0}
> info: [BOOTSTRAP] [info] Closed client connection
> info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: current=1
> info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: id=UiAutomatorTestRunner
> info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: class=io.appium.android.bootstrap.Bootstrap
> info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: stream=.
> info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: numtests=1
> info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: test=testRunServer
> info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS_CODE: 0
> info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: stream=
> info: [UIAUTOMATOR STDOUT] Test results for WatcherResultPrinter=.
> info: [UIAUTOMATOR STDOUT] Time: 24.698
> info: [UIAUTOMATOR STDOUT] OK (1 test)
> info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS_CODE: -1
> info: UiAutomator shut down normally
> ERROR: error: Failed to start an Appium session, err was: Error: com.verisign.mvip.main/.ActivationActivity never started. Current: com.sec.android.app.launcher/com.android.launcher2.Launcher
> info: Cleaning up android objects
> info: Cleaning up appium session
> info: Error: com.verisign.mvip.main/.ActivationActivity never started. Current: com.sec.android.app.launcher/com.android.launcher2.Launcher
> at null.<anonymous> (D:\Appium-version1.0\AppiumForWindows-1.1.0.0\Appium\node_modules\appium\lib\devices\android\adb.js:1276:12)
> at null.<anonymous> (D:\Appium-version1.0\AppiumForWindows-1.1.0.0\Appium\node_modules\appium\lib\devices\android\adb.js:1221:7)
> at D:\Appium-version1.0\AppiumForWindows-1.1.0.0\Appium\node_modules\appium\lib\devices\android\adb.js:153: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)
> info: Responding to client with error: {"status":33,"value":{"message":"A new session could not be created. (Original error: com.verisign.mvip.main/.ActivationActivity never started. Current: com.sec.android.app.launcher/com.android.launcher2.Launcher)","origValue":"com.verisign.mvip.main/.ActivationActivity never started. Current: com.sec.android.app.launcher/com.android.launcher2.Launcher"},"sessionId":null}
> POST /wd/hub/session 500 73494ms - 402b
Thanks
Siva
Siva Subramanian
Jun 2, 2014, 3:40:34 PM6/2/14
to Isaac Murchie, appium-...@googlegroups.com
Is this an genuine issue or issue with my code ?
could you please kindly revert back ....
Isaac Murchie
Jun 2, 2014, 4:08:49 PM6/2/14
to Siva Subramanian, appium-...@googlegroups.com
It works for me, with the latest code from master.
Are you no longer waiting on the EulaActivity? I don't see any appWaitActivity in the caps.
Siva Subramanian
Jun 3, 2014, 2:36:21 AM6/3/14
to Isaac Murchie, appium-...@googlegroups.com
Hi issac,
CODE :
WebDriver driver;
DesiredCapabilities capabilities = new DesiredCapabilities();
capabilities.setCapability(CapabilityType.BROWSER_NAME,"");
capabilities.setCapability("newCommandTimeout","300");
capabilities.setCapability("device","Android");
capabilities.setCapability(CapabilityType.VERSION,"4.3");
capabilities.setCapability(CapabilityType.PLATFORM,"WINDOWS");
capabilities.setCapability(CapabilityType.SUPPORTS_JAVASCRIPT,true);
capabilities.setCapability(CapabilityType.HAS_TOUCHSCREEN,true);
capabilities.setCapability(CapabilityType.ACCEPT_SSL_CERTS,true);
capabilities.setCapability("app", "D:\\adt-bundle-windows-x86_64-20131030\\adt-bundle-windows-x86_64-20131030\\sdk\\platform-tools\\mvip-Android-2.2.apk");//If you want to run it on emulator.
capabilities.setCapability("appPackage", "com.verisign.mvip.main"); // This is package name of your app (you can get it from apk info app)
capabilities.setCapability("appWaitActivity", "com.verisign.mvip.main.EulaActivity");
capabilities.setCapability("appActivity", ".ActivationActivity");
//Create RemoteWebDriver instance and connect to the Appium server.
driver = new RemoteWebDriver(new URL("http://127.0.0.1:4723/wd/hub"), capabilities);
driver.manage().timeouts().implicitlyWait(80, TimeUnit.SECONDS);
Even after using app-wait activity on Eula activity ,
Even i tried with using the below line
capabilities.setCapability("appWaitActivity", ".EulaActivity");
The appium session is not getting created successfully.
Could you please have a look into the logs given below.
SERVER_LOGS:
> Starting Node Server
> info: Welcome to Appium v1.1.0 (REV e433bbc31511f199287db7724e1ce692bcb32117)
> info: Appium REST http interface listener started on 127.0.0.1:4723
> info: socket.io started
> info: Non-default server args: {"address":"127.0.0.1","logNoColors":true,"platformName":"Android","platformVersion":"18","automationName":"Appium"}
> ERROR: debug: Appium request initiated at /wd/hub/session
> info: Using local app from desired caps: D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\mvip-Android-2.2.apk
> ERROR: debug: Request received with params: {"desiredCapabilities":{"newCommandTimeout":"300","platform":"WINDOWS","app":"D:\\adt-bundle-windows-x86_64-20131030\\adt-bundle-windows-x86_64-20131030\\sdk\\platform-tools\\mvip-Android-2.2.apk","javascriptEnabled":true,"acceptSslCerts":true,"browserName":"","appActivity":".ActivationActivity","appWaitActivity":"com.verisign.mvip.main.EulaActivity","device":"Android","hasTouchScreen":true,"appPackage":"com.verisign.mvip.main","version":"4.3"}}
> info: Creating new appium session 3e274ceb-7019-4bce-8e18-cb32265f98f2
> ERROR: debug: Using fast reset? true
> info: Starting android appium
> info: Preparing device for session
> info: Checking whether app is actually present
> info: Checking whether adb is present
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" devices
> info: [ADB] Using adb from D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe
> info: Trying to find a connected android device
> info: [ADB] Getting connected devices...
> info: [ADB] 1 device(s) connected
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 wait-for-device
> info: Setting device id to 7d746172
> info: [ADB] Waiting for device to be ready and to respond to shell commands (timeout = 5)
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 shell "echo 'ready'"
> info: Starting logcat capture
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 shell "getprop ro.build.version.sdk"
> info: Getting device API level
> info: Device is at API Level 18
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 shell "getprop persist.sys.language"
> ERROR: debug: Current device language: en
> ERROR: debug: java -jar "D:\Appium-version1.0\AppiumForWindows-1.1.0.0\Appium\node_modules\appium\lib\devices\android\helpers\strings_from_apk.jar" "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\mvip-Android-2.2.apk" "C:\Windows\Temp\com.verisign.mvip.main" en
> info: No strings.xml for language 'en', getting default strings.xml
> ERROR: debug: java -jar "D:\Appium-version1.0\AppiumForWindows-1.1.0.0\Appium\node_modules\appium\lib\devices\android\helpers\strings_from_apk.jar" "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\mvip-Android-2.2.apk" "C:\Windows\Temp\com.verisign.mvip.main"
> warn: Error getting strings.xml from apk
> ERROR: debug: Exception in thread "main" java.lang.Exception: Output is not an existing readable directory.
> ERROR: at strings.StringsXML.e(StringsXML.java:105)
> ERROR: at strings.StringsXML.main(StringsXML.java:140)
> ERROR:
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 shell "echo '{}' > /data/local/tmp/strings.json"
> info: Checking whether aapt is present
> ERROR: debug: processFromManifest: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\build-tools\android-4.4\aapt.exe" dump xmltree "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\mvip-Android-2.2.apk" AndroidManifest.xml
> info: [ADB] Using aapt from D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\build-tools\android-4.4\aapt.exe
> ERROR: debug: Set app process to: isign.mvip.main
> ERROR: debug: Not uninstalling app since server not started with --full-reset
> ERROR: debug: Checking app cert for D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\mvip-Android-2.2.apk: java -jar "D:\Appium-version1.0\AppiumForWindows-1.1.0.0\Appium\node_modules\appium\lib\devices\android\helpers\verify.jar" "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\mvip-Android-2.2.apk"
> ERROR: debug: App already signed.
> info: Zip-aligning D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\mvip-Android-2.2.apk
> info: Checking whether zipalign is present
> info: [ADB] Using zipalign from D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\tools\zipalign.exe
> ERROR: debug: zipAlignApk: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\tools\zipalign.exe" -f 4 "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\mvip-Android-2.2.apk" "C:\Users\SIVASU~1\AppData\Local\Temp\appium11453-1188-bfvssy.tmp"
> info: [BOOTSTRAP] [info] Appium Socket Server Ready
> ERROR: debug: Waking up device if it's not alive
> info: [BOOTSTRAP] [info] Loading json...
> info: Pushing command to appium work queue: ["wake",{}]
> info: [BOOTSTRAP] [info] json loading complete.
> info: [BOOTSTRAP] [info] Registered crash watchers.
> info: [BOOTSTRAP] [info] Client connected
> info: [BOOTSTRAP] [info] Got data from client: {"cmd":"action","action":"wake","params":{}}
> info: [BOOTSTRAP] [info] Got command of type ACTION
> info: [BOOTSTRAP] [debug] Got command action: wake
> info: [BOOTSTRAP] [info] Returning result: {"value":true,"status":0}
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 shell "dumpsys window"
> info: Writing dumpsys output to D:\Appium-version1.0\AppiumForWindows-1.1.0.0\Appium\node_modules\appium\.dumpsys.log
> ERROR: debug: Screen already unlocked, continuing.
> info: Pushing command to appium work queue: ["getDataDir",{}]
> info: [BOOTSTRAP] [info] Got data from client: {"cmd":"action","action":"getDataDir","params":{}}
> ERROR: debug: dataDir set to: /data/local/tmp
> info: [BOOTSTRAP] [info] Got command of type ACTION
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 shell "am start -S -a android.intent.action.MAIN -c android.intent.category.LAUNCHER -f 0x10200000 -n com.verisign.mvip.main/.ActivationActivity"
> info: [BOOTSTRAP] [debug] Got command action: getDataDir
> info: [BOOTSTRAP] [info] Returning result: {"value":"\/data\/local\/tmp","status":0}
> info: Waiting for pkg "com.verisign.mvip.main" and activity "com.verisign.mvip.main.EulaActivity" to be focused
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 shell "dumpsys window windows"
> info: Getting focused package and activity
> info: Getting focused package and activity
> ERROR: debug: executing: "D:\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb.exe" -s 7d746172 shell "dumpsys window windows"
> ERROR: error: com.verisign.mvip.main/.EulaActivity never started. Current: com.sec.android.app.launcher/com.android.launcher2.Launcher
> info: Stopping logcat capture
> ERROR: debug: Logcat terminated with code null, signal SIGTERM
> info: [BOOTSTRAP] [info] Got data from client: {"cmd":"shutdown"}
> info: [BOOTSTRAP] [info] Got command of type SHUTDOWN
> info: [BOOTSTRAP] [info] Returning result: {"value":"OK, shutting down","status":0}
> info: [BOOTSTRAP] [info] Closed client connection
> info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: current=1
> info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: id=UiAutomatorTestRunner
> info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: class=io.appium.android.bootstrap.Bootstrap
> info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: stream=.
> info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: numtests=1
> info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: test=testRunServer
> info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS_CODE: 0
> info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: stream=
> info: [UIAUTOMATOR STDOUT] Test results for WatcherResultPrinter=.
> info: [UIAUTOMATOR STDOUT] Time: 22.267
> info: [UIAUTOMATOR STDOUT] OK (1 test)
> info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS_CODE: -1
> info: Sent shutdown command, waiting for UiAutomator to stop...
> info: UiAutomator shut down normally
> info: Cleaning up android objects
> info: Cleaning up appium session
> ERROR: error: Failed to start an Appium session, err was: Error: com.verisign.mvip.main/.EulaActivity never started. Current: com.sec.android.app.launcher/com.android.launcher2.Launcher
> info: Error: com.verisign.mvip.main/.EulaActivity never started. Current: com.sec.android.app.launcher/com.android.launcher2.Launcher
> at null.<anonymous> (D:\Appium-version1.0\AppiumForWindows-1.1.0.0\Appium\node_modules\appium\lib\devices\android\adb.js:1276:12)
> at null.<anonymous> (D:\Appium-version1.0\AppiumForWindows-1.1.0.0\Appium\node_modules\appium\lib\devices\android\adb.js:1221:7)
> at D:\Appium-version1.0\AppiumForWindows-1.1.0.0\Appium\node_modules\appium\lib\devices\android\adb.js:153: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)
> info: Responding to client with error: {"status":33,"value":{"message":"A new session could not be created. (Original error: com.verisign.mvip.main/.EulaActivity never started. Current: com.sec.android.app.launcher/com.android.launcher2.Launcher)","origValue":"com.verisign.mvip.main/.EulaActivity never started. Current: com.sec.android.app.launcher/com.android.launcher2.Launcher"},"sessionId":null}
> POST /wd/hub/session 500 43361ms - 390b
Thanks
Siva
sudharsan
Jun 3, 2014, 4:58:05 AM6/3/14
to appium-...@googlegroups.com
Hi Jonathan Lipps ,
can u please tell me where we can find the app package and app activity details of android while writing scripts.
Thanks
Sudharsan
On Friday, March 28, 2014 11:23:31 PM UTC+5:30, Diana Menezes wrote:
I am trying to run test on android device. Nexus 5 with android 4.4The app is succesfully installed and launched, after launching the appium logs show:
info: Waiting for activity to be focused
info: Getting focused package and activity
debug: executing: "/Applications/AndroidStudio.app/sdk/platform-tools/adb" -s (device-id) shell "dumpsys window windows"
Siva Subramanian
Jun 3, 2014, 5:29:04 AM6/3/14
to sudharsan, appium-...@googlegroups.com
Hi Sudharsan ,
Please install the "apkinfo.apk" file ( available at the android store- blue color icon with 'i' in it ) in your android mobile where your app is stored.
Now launch the apkinfo app and click on the 'ViewApp' Button , which will list all the installed apps in your mobile .
Now choose the your app and check for packages and activities pertaining to your app.
Hope you got it .
Thanks
Siva
--
http://appium.io
---
You received this message because you are subscribed to a topic in the Google Groups "Appium-discuss" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/appium-discuss/KlnPqY4gO6k/unsubscribe.
To unsubscribe from this group and all its topics, send an email to appium-discus...@googlegroups.com.
Isaac Murchie
Jun 4, 2014, 8:04:22 PM6/4/14
to Siva Subramanian, appium-...@googlegroups.com, menezes.diana22, Sangeetha Srinivasan
I'm sure you can. I'm not sure how to do it, though.
What was the code like to do it in 0.18?
Reply all
Reply to author
Forward
0 new messages