appium / appium

Cross-platform automation framework for all kinds of apps, built on top of the W3C WebDriver protocol
http://appium.io/
Apache License 2.0
18.89k stars 6.08k forks source link

Selendroid Server not found #737

Closed 1dson closed 11 years ago

1dson commented 11 years ago

I am running Appium on windows.

I have got a test that I want to run on device with API level < 16. I have successfully managed to install the app on my device using Selendroid but after the app has been installed on my device and appium tries to start the instrumentation process i.e.

info: Selendroid server is launching info: Making http request with opts:{"url":http://localhost:8080/wd/hub/status

I am getting the following error;

error: Failed to start an Appium session, err was: Error: Waited 20 secs for selendroid server and it never showed up.

bootstraponline commented 11 years ago

I think an oudated Appium probably explains the error.

1dson commented 11 years ago

I figured as much I had to copy the Clean.apk manifest manually into the app> android folder as it wasn't in there. But I have a bigger problem, I have downloaded the latest version 0.7.0 for windows from appium.io but when I run my test I am getting the following error in my log and the app does not launch

debug: java -jar "C:..\appium\node_modules\appium\app\android\strings_from_apk.jar" "" "C:\Windows\Temp\com.appname.mobilize.myapp" debug: Exception in thread "main" java.lang.Exception: Input is not an existing readable file. at strings.StringsXML.e(stringsXML.java:105)
at strings.StringsXML.main(stringsXML.java:131) error: error making strings error: Above error isn't fatal, maybe relaunching adb will help...

This error doesn't occur if i run version 0.6.0

bootstraponline commented 11 years ago

Does "C:\Windows\Temp\com.appname.mobilize.myapp" exist?

1dson commented 11 years ago

I reverted back to my API 17 test as I couldn't get the selendroid test to work as I am still getting the timeout issue 'error: Failed to start an Appium session, err was: Error: Waited 20 secs for selendroid server and it never showed up.'

"C:\Windows\Temp\com.appname.mobilize.myapp" exist? doesn't and I don't think it should, as the apk that I am testing is installed on my device (4.2.2) already. Unless maybe the logic has changed from appium v 0.6.0

These are the capabilities that I am passing

        var caps = new DesiredCapabilities();
         caps.SetCapability("app-package", "bbc.mobile.news.uk");
         caps.SetCapability("app-activity", "HomeUkActivity");
        caps.SetCapability("app-wait-activity", "HomeUkActivity"); 

If i use v0.6.0, the app get's started correctly and there are no issues.The issue only occurs in 0.7.0. I see that in v0.7.0 you've added the following 'strings_from_apk' jar file in the android folder and I think this is the file that is causing the issue

bootstraponline commented 11 years ago

"C:\Windows\Temp\com.appname.mobilize.myapp" exist? doesn't and I don't think it should, as the apk that I am testing is installed on my device (4.2.2) already.

If you're testing an apk that is only on the device and not available at a local path then extracting strings from the apk will fail. Appium should be updated so that if there's no local apk then find by id is disabled instead of refusing to run.

Selendroid launches for me so this issue is only when there's no local apk.

1dson commented 11 years ago

I am passing the following capabilities when trying to test API < 17

      var caps = new DesiredCapabilities();
       string myApp = "C:\\Users\\Wonderson.Chideya\\Documents\\ASZ10668-COPD.apk";
        caps.SetCapability("app-package", "com.excointouch.mobilize.ASZ10668");
        caps.SetCapability("device", "selendroid");
        caps.SetCapability("app", myApp);
        caps.SetCapability("app-activity", "ASZ10668Activity");
        caps.SetCapability("app-wait-activity", "ASZ10668Activity");

The App does get installed on the device but the selendroid session doesn't get started and I get the timeout error. Could it be possible that the link on the appium.io site is not the up to date version of appium? As you stated the reason that I am seeing the timeout issue is because I am using an outdated version of appium

bootstraponline commented 11 years ago

Unless you're running from source, then you're on an old version. I'm not sure how you'd run from source on Windows. When I launch Appium, I see info: Welcome to Appium v0.7.1 (REV f1f19b9a730885d9fd66e2d5f0fbccd2b393f2d1) which matches https://github.com/appium/appium/commit/f1f19b9a730885d9fd66e2d5f0fbccd2b393f2d1.

1dson commented 11 years ago

I just download the zip from http://appium.io/. it contains all the dlls, jar, Appium.exe etc. The latest Zip that was uploaded to the site is for v0.7.0. I am guessing someone needs to do another push to appium.io so that it contains the latest version.

bootstraponline commented 11 years ago

On Appium.app for OS X, you can download Appium from GitHub and run from source with Appium -> Preferences... -> Use External Appium Package. I think this will be possible in the future for Windows.

1dson commented 11 years ago

Hopefully sooner that later :-)

1dson commented 11 years ago

This is what I am seeing when I launch the Appium.exe

info: Welcome to Appium v0.7.1 (REV 055dcdf7ef15a0a15a4bc9daed1c748c98f2fa)

1dson commented 11 years ago

On further investigation this is what my log file is displaying

info: Determining app install/clean status debug: Getting install/clean status for com.mycomp.mobilize.ASZ10668 info: [ADB] Installing app apk info: Installing C:\Users\myname\Documents\ASZ10668-COPD.apk debug: pkg: /data/local/tmp/ASZ10668-COPD.apk Success info: [ADB] Forwarding system:8080 to device:8080 info: [ADB] Attempting to unlock screen info: Starting instrumentation process for selendroid with cmd: adb shell am ins trument -e main_activity 'com.mycomp.mobilize.ASZ10668.ASZ10668Activity' co m.excointouch.mobilize.ASZ10668.selendroid/io.selendroid.ServerInstrumentation info: Selendroid server is launching info: Making http request with opts: {"url":"http://localhost:8080/wd/hub/status ","method":"GET","headers":{"Content-Type":"application/json"}} info: Making http request with opts: {"url":"http://localhost:8080/wd/hub/status ","method":"GET","headers":{"Content-Type":"application/json"}} info: Making http request with opts: {"url":"http://localhost:8080/wd/hub/status ","method":"GET","headers":{"Content-Type":"application/json"}} info: Making http request with opts: {"url":"http://localhost:8080/wd/hub/status ","method":"GET","headers":{"Content-Type":"application/json"}} info: Making http request with opts: {"url":"http://localhost:8080/wd/hub/status ","method":"GET","headers":{"Content-Type":"application/json"}} info: Making http request with opts: {"url":"http://localhost:8080/wd/hub/status ","method":"GET","headers":{"Content-Type":"application/json"}} info: Making http request with opts: {"url":"http://localhost:8080/wd/hub/status ","method":"GET","headers":{"Content-Type":"application/json"}} info: Making http request with opts: {"url":"http://localhost:8080/wd/hub/status ","method":"GET","headers":{"Content-Type":"application/json"}} info: Making http request with opts: {"url":"http://localhost:8080/wd/hub/status ","method":"GET","headers":{"Content-Type":"application/json"}} info: Making http request with opts: {"url":"http://localhost:8080/wd/hub/status ","method":"GET","headers":{"Content-Type":"application/json"}} info: Making http request with opts: {"url":"http://localhost:8080/wd/hub/status ","method":"GET","headers":{"Content-Type":"application/json"}} info: Making http request with opts: {"url":"http://localhost:8080/wd/hub/status ","method":"GET","headers":{"Content-Type":"application/json"}} info: Making http request with opts: {"url":"http://localhost:8080/wd/hub/status ","method":"GET","headers":{"Content-Type":"application/json"}} info: Making http request with opts: {"url":"http://localhost:8080/wd/hub/status ","method":"GET","headers":{"Content-Type":"application/json"}} info: Making http request with opts: {"url":"http://localhost:8080/wd/hub/status ","method":"GET","headers":{"Content-Type":"application/json"}} info: Making http request with opts: {"url":"http://localhost:8080/wd/hub/status ","method":"GET","headers":{"Content-Type":"application/json"}} info: Making http request with opts: {"url":"http://localhost:8080/wd/hub/status ","method":"GET","headers":{"Content-Type":"application/json"}} info: Making http request with opts: {"url":"http://localhost:8080/wd/hub/status ","method":"GET","headers":{"Content-Type":"application/json"}} info: Making http request with opts: {"url":"http://localhost:8080/wd/hub/status ","method":"GET","headers":{"Content-Type":"application/json"}} info: Making http request with opts: {"url":"http://localhost:8080/wd/hub/status ","method":"GET","headers":{"Content-Type":"application/json"}} info: Making http request with opts: {"url":"http://localhost:8080/wd/hub/status ","method":"GET","headers":{"Content-Type":"application/json"}} info: Making http request with opts: {"url":"http://localhost:8080/wd/hub/status ","method":"GET","headers":{"Content-Type":"application/json"}} info: Making http request with opts: {"url":"http://localhost:8080/wd/hub/status ","method":"GET","headers":{"Content-Type":"application/json"}} info: Making http request with opts: {"url":"http://localhost:8080/wd/hub/status ","method":"GET","headers":{"Content-Type":"application/json"}} info: Making http request with opts: {"url":"http://localhost:8080/wd/hub/status ","method":"GET","headers":{"Content-Type":"application/json"}} info: Making http request with opts: {"url":"http://localhost:8080/wd/hub/status ","method":"GET","headers":{"Content-Type":"application/json"}} error: Failed to start an Appium session, err was: Error: Waited 20 secs for sel endroid server and it never showed up info: Responding to client with error: {"status":6,"value":{"message":"A session is either terminated or not started (Original error: Waited 20 secs for selendr oid server and it never showed up)","origValue":"Waited 20 secs for selendroid s erver and it never showed up"},"sessionId":"0edfc9f1-afa5-4fe8-8348-ae625691cd4b "} POST /wd/hub/session 500 30369ms - 311 info: Clearing out appium devices debug: Appium request initiated at /wd/hub/session GET /wd/hub/session 500 5ms - 106 TypeError: Cannot read property 'capabilities' of null at exports.getSession (C:\Users\myName\Documents\Appium\node_modu les\appium\app\controller.js:191:38)

What caught me was the following error { "status": 13, "value": "ERROR running Appium command: Cannot read property 'capabilities' of null" }

Any Idea why I would be getting the error when the same test works on 4.2 + devices? I am running appium 0.7.1 (REV 055dcdf7ef15a0a15a4bc9daed1c748c98f2fa)

jlipps commented 11 years ago

Are you running anything else on port 8080 on your machine?

It'd also be useful to run adb logcat while this is going on to see if the selendroid server announces that it has started.

On Jun 12, 2013, at 9:22 AM, 1dson notifications@github.com wrote:

On further investigation this is what my log file is displaying

info: Determining app install/clean status debug: Getting install/clean status for com.mycomp.mobilize.ASZ10668 info: [ADB] Installing app apk info: Installing C:\Users\myname\Documents\ASZ10668-COPD.apk debug: pkg: /data/local/tmp/ASZ10668-COPD.apk Success info: [ADB] Forwarding system:8080 to device:8080 info: [ADB] Attempting to unlock screen info: Starting instrumentation process for selendroid with cmd: adb shell am ins trument -e main_activity 'com.mycomp.mobilize.ASZ10668.ASZ10668Activity' co m.excointouch.mobilize.ASZ10668.selendroid/io.selendroid.ServerInstrumentation info: Selendroid server is launching info: Making http request with opts: {"url":"http://localhost:8080/wd/hub/status ","method":"GET","headers":{"Content-Type":"application/json"}} info: Making http request with opts: {"url":"http://localhost:8080/wd/hub/status ","method":"GET","headers":{"Content-Type":"application/json"}} info: Making http request with opts: {"url":"http://localhost:8080/wd/hub/status ","method":"GET","headers":{"Content-Type":"application/json"}} info: Making http request with opts: {"url":"http://localhost:8080/wd/hub/status ","method":"GET","headers":{"Content-Type":"application/json"}} info: Making http request with opts: {"url":"http://localhost:8080/wd/hub/status ","method":"GET","headers":{"Content-Type":"application/json"}} info: Making http request with opts: {"url":"http://localhost:8080/wd/hub/status ","method":"GET","headers":{"Content-Type":"application/json"}} info: Making http request with opts: {"url":"http://localhost:8080/wd/hub/status ","method":"GET","headers":{"Content-Type":"application/json"}} info: Making http request with opts: {"url":"http://localhost:8080/wd/hub/status ","method":"GET","headers":{"Content-Type":"application/json"}} info: Making http request with opts: {"url":"http://localhost:8080/wd/hub/status ","method":"GET","headers":{"Content-Type":"application/json"}} info: Making http request with opts: {"url":"http://localhost:8080/wd/hub/status ","method":"GET","headers":{"Content-Type":"application/json"}} info: Making http request with opts: {"url":"http://localhost:8080/wd/hub/status ","method":"GET","headers":{"Content-Type":"application/json"}} info: Making http request with opts: {"url":"http://localhost:8080/wd/hub/status ","method":"GET","headers":{"Content-Type":"application/json"}} info: Making http request with opts: {"url":"http://localhost:8080/wd/hub/status ","method":"GET","headers":{"Content-Type":"application/json"}} info: Making http request with opts: {"url":"http://localhost:8080/wd/hub/status ","method":"GET","headers":{"Content-Type":"application/json"}} info: Making http request with opts: {"url":"http://localhost:8080/wd/hub/status ","method":"GET","headers":{"Content-Type":"application/json"}} info: Making http request with opts: {"url":"http://localhost:8080/wd/hub/status ","method":"GET","headers":{"Content-Type":"application/json"}} info: Making http request with opts: {"url":"http://localhost:8080/wd/hub/status ","method":"GET","headers":{"Content-Type":"application/json"}} info: Making http request with opts: {"url":"http://localhost:8080/wd/hub/status ","method":"GET","headers":{"Content-Type":"application/json"}} info: Making http request with opts: {"url":"http://localhost:8080/wd/hub/status ","method":"GET","headers":{"Content-Type":"application/json"}} info: Making http request with opts: {"url":"http://localhost:8080/wd/hub/status ","method":"GET","headers":{"Content-Type":"application/json"}} info: Making http request with opts: {"url":"http://localhost:8080/wd/hub/status ","method":"GET","headers":{"Content-Type":"application/json"}} info: Making http request with opts: {"url":"http://localhost:8080/wd/hub/status ","method":"GET","headers":{"Content-Type":"application/json"}} info: Making http request with opts: {"url":"http://localhost:8080/wd/hub/status ","method":"GET","headers":{"Content-Type":"application/json"}} info: Making http request with opts: {"url":"http://localhost:8080/wd/hub/status ","method":"GET","headers":{"Content-Type":"application/json"}} info: Making http request with opts: {"url":"http://localhost:8080/wd/hub/status ","method":"GET","headers":{"Content-Type":"application/json"}} info: Making http request with opts: {"url":"http://localhost:8080/wd/hub/status ","method":"GET","headers":{"Content-Type":"application/json"}} error: Failed to start an Appium session, err was: Error: Waited 20 secs for sel endroid server and it never showed up info: Responding to client with error: {"status":6,"value":{"message":"A session is either terminated or not started (Original error: Waited 20 secs for selendr oid server and it never showed up)","origValue":"Waited 20 secs for selendroid s erver and it never showed up"},"sessionId":"0edfc9f1-afa5-4fe8-8348-ae625691cd4b "} POST /wd/hub/session 500 30369ms - 311 info: Clearing out appium devices debug: Appium request initiated at /wd/hub/session GET /wd/hub/session 500 5ms - 106 TypeError: Cannot read property 'capabilities' of null at exports.getSession (C:\Users\myName\Documents\Appium\node_modu les\appium\app\controller.js:191:38)

What caught me was the following error { "status": 13, "value": "ERROR running Appium command: Cannot read property 'capabilities' of null" }

Any Idea why I would be getting the error when the same test works on 4.2 + devices? I am running appium 0.7.1 (REV 055dcdf7ef15a0a15a4bc9daed1c748c98f2fa)

— Reply to this email directly or view it on GitHub.

1dson commented 11 years ago

This is my logcat

I/ActivityThread( 237): mRegistered=true mCurOrdered=false I/FMSystemService onReceive = ( 237): android.intent.action.PACKAGE_REMOVED I/FMSystemService( 237): onReceive pkgName = com.excointouch.mobilize.ASZ10668 I/ActivityThread( 237): finish dispatching broadcast to android.media.FMSystemS ervice$1@30fe3a70 I/ActivityThread( 237): Dispatching broadcast android.intent.action.PACKAGE_REM OVED to com.android.server.BackupManagerService$1@30fd6e28 I/ActivityThread( 237): mRegistered=true mCurOrdered=false I/ActivityThread( 237): finish dispatching broadcast to com.android.server.Back upManagerService$1@30fd6e28 I/ActivityThread( 237): Dispatching broadcast android.intent.action.PACKAGE_REM OVED to com.android.server.RecognitionManagerService$MyPackageMonitor@30f359c8 I/ActivityThread( 237): mRegistered=true mCurOrdered=false I/ActivityThread( 237): finish dispatching broadcast to com.android.server.Reco gnitionManagerService$MyPackageMonitor@30f359c8 I/ActivityThread( 237): Dispatching broadcast android.intent.action.PACKAGE_REM OVED to com.android.server.AppWidgetService$1@30ea93f8 I/ActivityThread( 237): mRegistered=true mCurOrdered=false I/ActivityThread( 237): finish dispatching broadcast to com.android.server.AppW idgetService$1@30ea93f8 I/ActivityThread( 237): Dispatching broadcast android.intent.action.PACKAGE_REM OVED to android.server.search.SearchManagerService$MyPackageMonitor@310a88e8 I/ActivityThread( 237): mRegistered=true mCurOrdered=false I/ActivityThread( 237): finish dispatching broadcast to android.server.search.S earchManagerService$MyPackageMonitor@310a88e8 I/ActivityThread( 237): Receiving broadcast android.intent.action.PACKAGE_ADDED to android.content.pm.RegisteredServicesCache$1@30f06038 I/ActivityThread( 237): Receiving broadcast android.intent.action.PACKAGE_ADDED to android.content.pm.RegisteredServicesCache$1@30fb8908 I/ActivityThread( 237): Receiving broadcast android.intent.action.PACKAGE_ADDED to com.android.server.DevicePolicyManagerService$MyPackageMonitor@30f784f0 I/ActivityThread( 237): Dispatching broadcast android.intent.action.PACKAGE_ADD ED to android.content.pm.RegisteredServicesCache$1@30f06038 I/ActivityThread( 237): mRegistered=true mCurOrdered=false I/ActivityThread( 237): finish dispatching broadcast to android.content.pm.Regi steredServicesCache$1@30f06038 I/ActivityThread( 237): Dispatching broadcast android.intent.action.PACKAGE_ADD ED to android.content.pm.RegisteredServicesCache$1@30fb8908 I/ActivityThread( 237): mRegistered=true mCurOrdered=false I/ActivityThread( 237): finish dispatching broadcast to android.content.pm.Regi steredServicesCache$1@30fb8908 I/ActivityThread( 237): Receiving broadcast android.intent.action.PACKAGE_ADDED to com.android.server.InputMethodManagerService$MyPackageMonitor@30f2ccf0 I/ActivityThread( 237): Receiving broadcast android.intent.action.PACKAGE_ADDED to com.android.server.AccessibilityManagerService$2@30fd45d0 I/ActivityThread( 237): Receiving broadcast android.intent.action.PACKAGE_ADDED to com.android.server.WallpaperManagerService$MyPackageMonitor@30fee348 I/ActivityThread( 237): Receiving broadcast android.intent.action.PACKAGE_ADDED to com.android.server.BackupManagerService$1@30fd6e28 I/ActivityThread( 237): Receiving broadcast android.intent.action.PACKAGE_ADDED to com.android.server.RecognitionManagerService$MyPackageMonitor@30f359c8 I/ActivityThread( 237): Receiving broadcast android.intent.action.PACKAGE_ADDED to com.android.server.AppWidgetService$1@30ea93f8 I/ActivityThread( 237): Receiving broadcast android.intent.action.PACKAGE_ADDED to android.server.search.SearchManagerService$MyPackageMonitor@310a88e8 I/ActivityThread( 237): Dispatching broadcast android.intent.action.PACKAGE_ADD ED to com.android.server.DevicePolicyManagerService$MyPackageMonitor@30f784f0 I/ActivityThread( 237): mRegistered=true mCurOrdered=false I/ActivityThread( 237): finish dispatching broadcast to com.android.server.Devi cePolicyManagerService$MyPackageMonitor@30f784f0 I/ActivityThread( 237): Dispatching broadcast android.intent.action.PACKAGE_ADD ED to com.android.server.InputMethodManagerService$MyPackageMonitor@30f2ccf0 I/ActivityThread( 237): mRegistered=true mCurOrdered=false I/ActivityThread( 9058): enter process activity msg = 113 I/ActivityThread( 9058): exit process activity msg = 113 I/ActivityThread( 6895): enter process activity msg = 113 D/InstallReceiver( 6895): com.excointouch.mobilize.ASZ10668 I/ActivityThread( 6895): exit process activity msg = 113 I/ActivityThread( 5349): Receiving broadcast android.intent.action.PACKAGE_REMOV ED to com.android.providers.applications.ApplicationsProvider$MyPackageMonitor@3 0e21010 I/ActivityThread( 5349): Receiving broadcast android.intent.action.PACKAGE_ADDED to com.android.providers.applications.ApplicationsProvider$MyPackageMonitor@30e 21010 I/ActivityThread( 5349): Dispatching broadcast android.intent.action.PACKAGE_REM OVED to com.android.providers.applications.ApplicationsProvider$MyPackageMonitor @30e21010 I/ActivityThread( 5349): mRegistered=true mCurOrdered=false I/ActivityThread( 5349): finish dispatching broadcast to com.android.providers.a pplications.ApplicationsProvider$MyPackageMonitor@30e21010 I/ActivityThread( 5349): Dispatching broadcast android.intent.action.PACKAGE_ADD ED to com.android.providers.applications.ApplicationsProvider$MyPackageMonitor@3 0e21010 I/ActivityThread( 5349): mRegistered=true mCurOrdered=false I/ActivityThread( 5349): finish dispatching broadcast to com.android.providers.a pplications.ApplicationsProvider$MyPackageMonitor@30e21010 I/ActivityThread( 315): Receiving broadcast android.intent.action.PACKAGE_REMOV ED to com.android.launcher2.LauncherModel@30e1dad8 I/ActivityThread( 315): Receiving broadcast android.intent.action.PACKAGE_ADDED to com.android.launcher2.LauncherModel@30e1dad8 I/ActivityThread( 315): Dispatching broadcast android.intent.action.PACKAGE_REM OVED to com.android.launcher2.LauncherModel@30e1dad8 I/ActivityThread( 315): mRegistered=true mCurOrdered=false I/ActivityThread( 315): finish dispatching broadcast to com.android.launcher2.L auncherModel@30e1dad8 I/ActivityThread( 315): Dispatching broadcast android.intent.action.PACKAGE_ADD ED to com.android.launcher2.LauncherModel@30e1dad8 I/ActivityThread( 315): mRegistered=true mCurOrdered=false I/ActivityThread( 237): finish dispatching broadcast to com.android.server.Inpu tMethodManagerService$MyPackageMonitor@30f2ccf0 I/ActivityThread( 237): Dispatching broadcast android.intent.action.PACKAGE_ADD ED to com.android.server.AccessibilityManagerService$2@30fd45d0 I/ActivityThread( 237): mRegistered=true mCurOrdered=false I/ActivityThread(12091): enter process activity msg = 113 I/ActivityThread( 237): finish dispatching broadcast to com.android.server.Acce ssibilityManagerService$2@30fd45d0 I/ActivityThread( 237): Dispatching broadcast android.intent.action.PACKAGE_ADD ED to com.android.server.WallpaperManagerService$MyPackageMonitor@30fee348 I/ActivityThread( 237): mRegistered=true mCurOrdered=false I/ActivityThread( 237): finish dispatching broadcast to com.android.server.Wall paperManagerService$MyPackageMonitor@30fee348 I/ActivityThread( 237): Dispatching broadcast android.intent.action.PACKAGE_ADD ED to com.android.server.BackupManagerService$1@30fd6e28 I/ActivityThread( 237): mRegistered=true mCurOrdered=false I/ActivityThread( 237): finish dispatching broadcast to com.android.server.Back upManagerService$1@30fd6e28 I/ActivityThread( 237): Dispatching broadcast android.intent.action.PACKAGE_ADD ED to com.android.server.RecognitionManagerService$MyPackageMonitor@30f359c8 I/ActivityThread( 237): mRegistered=true mCurOrdered=false I/ActivityThread( 237): finish dispatching broadcast to com.android.server.Reco gnitionManagerService$MyPackageMonitor@30f359c8 I/ActivityThread( 237): Dispatching broadcast android.intent.action.PACKAGE_ADD ED to com.android.server.AppWidgetService$1@30ea93f8 I/ActivityThread( 237): mRegistered=true mCurOrdered=false D/AlarmManager( 237): +++Alarm set:type=2 com.google.android.apps.maps Trigger after:1689348ms I/ActivityThread(12091): exit process activity msg = 113 I/ActivityThread(12091): enter process activity msg = 131 I/ActivityThread(12091): exit process activity msg = 131 I/ActivityThread( 315): finish dispatching broadcast to com.android.launcher2.L auncherModel@30e1dad8 I/ActivityThread( 237): finish dispatching broadcast to com.android.server.AppW idgetService$1@30ea93f8 I/ActivityThread( 237): Dispatching broadcast android.intent.action.PACKAGE_ADD ED to android.server.search.SearchManagerService$MyPackageMonitor@310a88e8 I/ActivityThread( 237): mRegistered=true mCurOrdered=false I/ActivityThread( 9071): enter process activity msg = 113 I/ActivityThread( 237): finish dispatching broadcast to android.server.search.S earchManagerService$MyPackageMonitor@310a88e8 I/ActivityThread( 9071): exit process activity msg = 113 I/SendKeyEvent(13991): 82 W/WindowManager( 237): waitForLastKey: mFinished=true, mLastWin=null D/PowerManagerService( 237): UnPartial wakeLock reactivate ,flags=0x6 tag=Sta yOnWhilePluggedIn Screen Dim D/PowerManagerService( 237): setPowerState: mPowerState=0x1 newState=0x3 noChan geLights=false reason=2 D/PowerManagerService( 237): setTimeoutLocked now=150030414 nextState=3 when=15 0036414 I/KeyguardUpdateMonitor( 237): enter isDeviceProvisioned ... I/WindowManager( 237): interceptKeyTi().hapticsEnabled = true E/enter ViewRoot( 315): Dispatching key KeyEvent{action=0 code=82 repeat=0 meta =0 scancode=0 mFlags=8} to com.android.internal.policy.impl.PhoneWindow$DecorVie w@30e95ce8 E/ViewRoot( 315): Sending key event to IME: seq=157 event=KeyEvent{action=0 cod e=82 repeat=0 meta=0 scancode=0 mFlags=8} E/exit ViewRoot( 315): Dispatching key KeyEvent{action=0 code=82 repeat=0 meta= 0 scancode=0 mFlags=8} to com.android.internal.policy.impl.PhoneWindow$DecorView @30e95ce8 E/ViewRoot( 315): rececive IME message viewRoot = Handler{30ea8148} E/ViewRoot( 315): IME finished event: seq=157 handled=false event=KeyEvent{acti on=0 code=82 repeat=0 meta=0 scancode=0 mFlags=8} W/KeyCharacterMap( 315): No keyboard for id 0 W/KeyCharacterMap( 315): Using default keymap: /system/usr/keychars/qwerty.kcm. bin E/!!!!!!!!!!!!!!!!!!!( 315): onKeyDown onKeyDown onKeyDown W/WindowManager( 237): waitForLastKey: mFinished=true, mLastWin=null D/PowerManagerService( 237): UnPartial wakeLock reactivate ,flags=0x6 tag=Sta yOnWhilePluggedIn Screen Dim D/PowerManagerService( 237): setTimeoutLocked now=150030426 nextState=3 when=15 0036426 W/WindowManager( 237): waitForLastKey: mFinished=true, mLastWin=null D/PowerManagerService( 237): UnPartial wakeLock reactivate ,flags=0x6 tag=Sta yOnWhilePluggedIn Screen Dim D/PowerManagerService( 237): setTimeoutLocked now=150030428 nextState=3 when=15 0036428 I/KeyguardUpdateMonitor( 237): enter isDeviceProvisioned ... I/WindowManager( 237): interceptKeyTi().hapticsEnabled = true W/WindowManager( 237): waitForLastKey: mFinished=false, mLastWin=Window{310e012 8 com.android.launcher/com.android.launcher2.Launcher paused=false} W/WindowManager( 237): Waiting for last key in android.os.BinderProxy@310dff60 target=Window{310e0128 com.android.launcher/com.android.launcher2.Launcher pause d=false} mFinished=false mDisplayFrozen=false targetIsNew=false paused=false mFo cusedApp=AppWindowToken{3106dbc0 token=HistoryRecord{310694c0 com.android.launch er/com.android.launcher2.Launcher}} mCurrentFocus=Window{310e0128 com.android.la uncher/com.android.launcher2.Launcher paused=false} E/enter ViewRoot( 315): Dispatching key KeyEvent{action=1 code=82 repeat=0 meta =0 scancode=0 mFlags=8} to com.android.internal.policy.impl.PhoneWindow$DecorVie w@30e95ce8 E/ViewRoot( 315): Sending key event to IME: seq=158 event=KeyEvent{action=1 cod e=82 repeat=0 meta=0 scancode=0 mFlags=8} E/ViewRoot( 315): rececive IME message viewRoot = Handler{30ea8148} E/exit ViewRoot( 315): Dispatching key KeyEvent{action=1 code=82 repeat=0 meta= 0 scancode=0 mFlags=8} to com.android.internal.policy.impl.PhoneWindow$DecorView @30e95ce8 E/ViewRoot( 315): IME finished event: seq=158 handled=false event=KeyEvent{acti on=1 code=82 repeat=0 meta=0 scancode=0 mFlags=8} W/WindowManager( 237): updateFocusedWindowLocked newFocus=Window{30fd4cb0 AtchD lg:com.android.launcher/com.android.launcher2.Launcher paused=false} mode=1 mCur rentFocus = Window{310e0128 com.android.launcher/com.android.launcher2.Launcher paused=false} W/WindowManager( 237): waitForLastKey: mFinished=true, mLastWin=null D/PowerManagerService( 237): UnPartial wakeLock reactivate ,flags=0x6 tag=Sta yOnWhilePluggedIn Screen Dim D/PowerManagerService( 237): setTimeoutLocked now=150030457 nextState=3 when=15 0036457 W/WindowManager( 237): updateFocusedWindowLocked newFocus=Window{30fd4cb0 AtchD lg:com.android.launcher/com.android.launcher2.Launcher paused=false} mode=3 mCur rentFocus = Window{30fd4cb0 AtchDlg:com.android.launcher/com.android.launcher2.L auncher paused=false} D/KeyguardViewMediator( 237): setHidden false D/KeyguardViewMediator( 237): setHidden false D/KeyguardViewMediator( 237): setHidden false D/KeyguardViewMediator( 237): setHidden false D/KeyguardViewMediator( 237): setHidden false D/KeyguardViewMediator( 237): setHidden false D/KeyguardViewMediator( 237): setHidden false D/KeyguardViewMediator( 237): setHidden false D/KeyguardViewMediator( 237): setHidden false D/KeyguardViewMediator( 237): setHidden false D/KeyguardViewMediator( 237): setHidden false D/KeyguardViewMediator( 237): setHidden false D/KeyguardViewMediator( 237): setHidden false D/KeyguardViewMediator( 237): setHidden false I/ActivityThread(12091): enter process activity msg = 120 I/ActivityThread(12091): exit process activity msg = 120 D/PowerManagerService( 237): setTimeoutLocked now=150036457 nextState=1 when=15 0083457 I/ActivityThread( 6895): enter process activity msg = 120 I/ActivityThread( 6895): exit process activity msg = 120 I/ActivityThread( 9071): enter process activity msg = 120 I/ActivityThread( 9071): exit process activity msg = 120 I/ActivityThread( 9058): enter process activity msg = 120 I/ActivityThread( 9058): exit process activity msg = 120 I/ActivityThread( 237): Receiving broadcast android.intent.action.TIME_TICK to com.android.server.AlarmManagerService$ClockReceiver@30f9e600 I/ActivityThread( 237): Dispatching broadcast android.intent.action.TIME_TICK t o com.android.server.AlarmManagerService$ClockReceiver@30f9e600 I/ActivityThread( 237): mRegistered=true mCurOrdered=true D/AlarmManager( 237): scheduleTimeTickEvent calendar=Wed Jun 12 14:34:00 GMT+01 :00 2013 D/AlarmManager( 237): calendar.getTimeInMillis()1371044040000 I/ActivityThread( 237): Receiving broadcast android.intent.action.TIME_TICK to com.android.internal.policy.impl.KeyguardUpdateMonitor$3@30f1abf8 I/ActivityThread( 237): finish dispatching broadcast to com.android.server.Alar mManagerService$ClockReceiver@30f9e600 I/ActivityThread( 237): Dispatching broadcast android.intent.action.TIME_TICK t o com.android.internal.policy.impl.KeyguardUpdateMonitor$3@30f1abf8 I/ActivityThread( 237): mRegistered=true mCurOrdered=true D/KeyguardUpdateMonitor( 237): received broadcast android.intent.action.TIME_TI CK D/KeyguardUpdateMonitor( 237): handleTimeUpdate I/ActivityThread( 237): Receiving broadcast android.intent.action.TIME_TICK to com.android.server.status.StatusBarPolicy$1@30edd220 I/ActivityThread( 237): finish dispatching broadcast to com.android.internal.po licy.impl.KeyguardUpdateMonitor$3@30f1abf8 I/ActivityThread( 237): Dispatching broadcast android.intent.action.TIME_TICK t o com.android.server.status.StatusBarPolicy$1@30edd220 I/ActivityThread( 237): mRegistered=true mCurOrdered=true D/StatusBarPolicy( 237): StatusBarPolicy:mIntentReceiver action=android.inten t.action.TIME_TICK D/StatusBarPolicy( 237): StatusBarPolicy:updateClock mClockData.text=14:33 System.currentTimeMillis()=1371043980102 D/StatusBarPolicy( 237): mCalendar.getTime()=Wed Jun 12 14:33:00 GMT+01:00 2013

D/StatusBarPolicy( 237): DateFormat.getTimeFormat(mContext).format(mCalendar.ge tTime()=14:33 I/ActivityThread( 237): Receiving broadcast android.intent.action.TIME_TICK to android.widget.DateTimeView$1@31248e60 I/ActivityThread( 237): finish dispatching broadcast to com.android.server.stat us.StatusBarPolicy$1@30edd220 I/ActivityThread( 237): Dispatching broadcast android.intent.action.TIME_TICK t o android.widget.DateTimeView$1@31248e60 I/ActivityThread( 237): mRegistered=true mCurOrdered=true I/ActivityThread( 237): Receiving broadcast android.intent.action.TIME_TICK to android.widget.DateTimeView$1@3117ba18 I/ActivityThread( 237): finish dispatching broadcast to android.widget.DateTime View$1@31248e60 I/ActivityThread( 237): Dispatching broadcast android.intent.action.TIME_TICK t o android.widget.DateTimeView$1@3117ba18 I/ActivityThread( 237): mRegistered=true mCurOrdered=true I/ActivityThread( 237): Receiving broadcast android.intent.action.TIME_TICK to android.widget.DateTimeView$1@310ca580 I/ActivityThread( 237): finish dispatching broadcast to android.widget.DateTime View$1@3117ba18 I/ActivityThread( 237): Dispatching broadcast android.intent.action.TIME_TICK t o android.widget.DateTimeView$1@310ca580 I/ActivityThread( 237): mRegistered=true mCurOrdered=true I/ActivityThread( 237): finish dispatching broadcast to android.widget.DateTime View$1@310ca580 I/ActivityThread( 339): enter process activity msg = 120 I/ActivityThread( 339): exit process activity msg = 120 I/ActivityThread( 311): Receiving broadcast android.intent.action.SIG_STR to co m.android.phone.BluetoothHandsfree$BluetoothPhoneState$2@30e699c8 I/ActivityThread( 311): Dispatching broadcast android.intent.action.SIG_STR to com.android.phone.BluetoothHandsfree$BluetoothPhoneState$2@30e699c8 I/ActivityThread( 311): mRegistered=true mCurOrdered=false I/ActivityThread( 311): finish dispatching broadcast to com.android.phone.Bluet oothHandsfree$BluetoothPhoneState$2@30e699c8

Doesn't look like the the server gets started. Just checking if the Port is not being used by another service.

1dson commented 11 years ago

Port 8080 is not in use by any other process

jlipps commented 11 years ago

In that case the issue is probably that Selendroid is not starting

On Jun 12, 2013, at 10:14 AM, 1dson notifications@github.com wrote:

Port 8080 is not in use by any other process

— Reply to this email directly or view it on GitHub.

1dson commented 11 years ago

Looking from the appium.exe log it does look like the selendroid server does get started but it never launches

debug: Appium request initiated at /wd/hub/session debug: Request received with params: {"desiredCapabilities":{"app-package":"com. excointouch.mobilize.ASZ10668","device":"selendroid","app":"C:\Users\Wonderson .Chideya\Documents\ASZ10668-COPD.apk","app-activity":"ASZ10668Activity","app-w ait-activity":"ASZ10668Activity"}} info: Using local app from desiredCaps: C:\Users\Wonderson.Chideya\Documents\ASZ 10668-COPD.apk info: Creating new appium session 681540c8-766d-4213-a276-162b44c95de1 info: Starting selendroid server info: Checking whether selendroid is built yet info: Selendroid server exists! info: Starting selendroid info: Preparing device for session info: Checking whether app is actually present info: Checking whether adb is present info: [ADB] Using adb from C:\Users\Wonderson.Chideya\AppData\Local\Android\andr oid-sdk\platform-tools\adb.exe info: Trying to find a connected android device info: [ADB] Getting connected devices... info: [ADB] 1 device(s) connected info: [ADB] Setting device id to CSE_P729V info: Found device, no need to retry info: [ADB] Waiting for device CSE_P729V to be ready and to respond to shell com mands (timeout = 5) info: Checking whether we need to run fast reset info: User doesn't want fast reset, doing nothing info: Rebuilt selendroid apk exists, doing nothing info: Rebuilt selendroid server already exists, no need to rebuild it with a new manifest info: Checking signed status of C:\Windows\Temp\selendroid.com.excointouch.mobil ize.ASZ10668.apk debug: Checking app cert for C:\Windows\Temp\selendroid.com.excointouch.mobilize .ASZ10668.apk: java -jar "C:\Users\Wonderson.Chideya\Documents\Appium\node_modul es\appium\app\android\verify.jar" "C:\Windows\Temp\selendroid.com.excointouch.mo bilize.ASZ10668.apk" info: Checking signed status of C:\Users\Wonderson.Chideya\Documents\ASZ10668-CO PD.apk debug: Checking app cert for C:\Users\Wonderson.Chideya\Documents\ASZ10668-COPD. apk: java -jar "C:\Users\Wonderson.Chideya\Documents\Appium\node_modules\appium\ app\android\verify.jar" "C:\Users\Wonderson.Chideya\Documents\ASZ10668-COPD.apk"

debug: App already signed. debug: App already signed. debug: Getting install/clean status for com.excointouch.mobilize.ASZ10668.selend roid info: Rebuilt selendroid is not installed, installing it info: Installing C:\Windows\Temp\selendroid.com.excointouch.mobilize.ASZ10668.ap k debug: pkg: /data/local/tmp/selendroid.com.excointouch.mobilize.ASZ10668.apk

Failure [INSTALL_FAILED_OLDER_SDK]

info: Determining app install/clean status debug: Getting install/clean status for com.excointouch.mobilize.ASZ10668 info: [ADB] Installing app apk info: Installing C:\Users\Wonderson.Chideya\Documents\ASZ10668-COPD.apk debug: pkg: /data/local/tmp/ASZ10668-COPD.apk

Success

info: [ADB] Forwarding system:8080 to device:8080 info: [ADB] Attempting to unlock screen info: Starting instrumentation process for selendroid with cmd: adb shell am ins trument -e main_activity 'com.excointouch.mobilize.ASZ10668.ASZ10668Activity' co m.excointouch.mobilize.ASZ10668.selendroid/io.selendroid.ServerInstrumentation info: Selendroid server is launching

1dson commented 11 years ago

Is there anything that I can do to start or launch the selendroid server?

Wondy On 12 Jun 2013 15:20, "Jonathan Lipps" notifications@github.com wrote:

In that case the issue is probably that Selendroid is not starting

On Jun 12, 2013, at 10:14 AM, 1dson notifications@github.com wrote:

Port 8080 is not in use by any other process

— Reply to this email directly or view it on GitHub.

— Reply to this email directly or view it on GitHubhttps://github.com/appium/appium/issues/737#issuecomment-19328632 .

jlipps commented 11 years ago

This sounds like it could be an issue with your app, android SDK, or AVD (or how they all relate). I googled INSTALL_FAILED_OLDER_SDK and found this: http://stackoverflow.com/questions/9093709/installation-error-install-failed-older-sdk, which looks like it could be helpful.

1dson commented 11 years ago

Thanks

On 13 Jun 2013 17:47, "Jonathan Lipps" notifications@github.com wrote:

This sounds like it could be an issue with your app, android SDK, or AVD (or how they all relate). I googled INSTALL_FAILED_OLDER_SDK and found this: http://stackoverflow.com/questions/9093709/installation-error-install-failed-older-sdk, which looks like it could be helpful.

— Reply to this email directly or view it on GitHubhttps://github.com/appium/appium/issues/737#issuecomment-19405067 .

1dson commented 11 years ago

Jonathan, thanks for all your help but I am still getting the INSTALL_FAILED_OLDER_SDK error and I think I've figured out what the issue might be. The original APK min SDK target is 7 and I can install it on a device running 2.2.3 to 4.2.3 and runs correctly. I've updated my android SDK and AVD but I think the issue is when Appium decompiles/rebuilds the app and creates the selendroid server e.g. selendroid.com.excointouch.mobilize.myapp.apk. For some reason I am guessing that the server gets reassigned with the min SDK version on my PC which would be 17 and not the version that was on the original app with is 7. So it will never install, as the device that I am trying to install to the SDK version is 8. I also tried to install the app selendroid app on my device (2.2.) manually an I got the following error 'There is a problem parsing the package'. but then I installed the same app on my other device (4.2.2) and it installed without any issues. Should I create a separate issue or just leave it in this chain

jlipps commented 11 years ago

Hmm, thanks for the research. @bootstraponline do you know how to make sure we respect the app target when we recompile the selendroid manifest? I bet we're just taking selendroid's target rather than the app's?

bootstraponline commented 11 years ago

@bootstraponline do you know how to make sure we respect the app target when we recompile the selendroid manifest?

We'd have to parse out the app's min sdk and then update the selendroid manifest. The min sdk on Selendroid's server is 10. If Selendroid doesn't support < 10 then changing this number won't help.

I'm not sure what you mean in reference to app target. I think the issue is related to min sdk.

I bet we're just taking selendroid's target rather than the app's?

I don't think we're changing the min sdk at all.

jlipps commented 11 years ago

I'm not sure what you mean in reference to app target. I think the issue is related to min sdk.

That's because I'm not clear on what I'm talking about or how it all works in Android-land. So maybe the issue here is just that Selendroid requires API level 10 and the device in question is API level 8?

bootstraponline commented 11 years ago

the issue here is just that Selendroid requires API level 10 and the device in question is API level 8?

Yes.

1dson commented 11 years ago

So for me to test on app that's meant to work on a API level 8 device I can just use AVD instead?

jlipps commented 11 years ago

I think the moral of the story is that Selendroid only works for API levels 10 and up. @DominikDary, is this true?

bootstraponline commented 11 years ago

Calabash is able to run on API level 4. I think it's a bug that Selendroid requires >= 10

DominikDary commented 11 years ago

I haven't tested it yet. Will do, and if it is working fine, I will change the mimimum version.

bootstraponline notifications@github.com schrieb:

Calabash is able to run on API level 4. I think it's a bug that Selendroid requires >= 10

— Reply to this email directly or view it on GitHub.

bootstraponline commented 11 years ago

It appears that Selendroid really does need API level 10. That means targeting API levels < 10 with Appium is not currently possible.

jeelansheriff commented 11 years ago

I am running into exactly the same issue with device having API level 15(Android version 4.0.4). I went through the logs posted here, and the failures seem to be exactly the same. My Appium version is v0.9.1.

Anyone who has a solution to this issue?

lock[bot] commented 5 years ago

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.