The requested application under test is not configured in selendroid server.

2,562 views
Skip to first unread message

Idris Yousifie

unread,
Apr 15, 2014, 10:30:06 AM4/15/14
to selen...@googlegroups.com
have latest selendroid and latest java installed. I am able to run java code against test app provided by selendroid community. However we have an in house apk file to test, when I run the java program against it i get exception errors:

Emulator is up and running, code looks like this (just want to load the app in the emulator)
java:
SelendroidCapabilities capa = new SelendroidCapabilities("io.selendroid.androiddriver:0.9.0");
WebDriver driver = new SelendroidDriver(capa);

in dos I ran:
java -jar selendroid-standalone-0.9.0-with-dependencies.jar -aut community311.apk

http://localhost:4444/wd/hub/status shows::
{"status":0,"value":{"supportedApps":[{"appId":"io.selendroid.androiddriver:0.9.0","mainActivity":"io.selendroid.androiddriver.WebViewActivity","basePackage":"io.selendroid.androiddriver"},{"appId":"com.opendata.android:0.0.1","mainActivity":"com.opendata.android.Property311","basePackage":"com.opendata.android"}],"os":{"arch":"amd64","name":"Windows 7","version":"6.1"},"build":{"browserName":"selendroid","version":"0.9.0"},"supportedDevices":[{"screenSize":"WVGA800","emulator":true,"androidTarget":"ANDROID19","avdName":"myApp"}]}}

Error I get when I run the java code:

Exception in thread "main" org.openqa.selenium.SessionNotCreatedException: The requested application under test is not configured in selendroid server.
io.selendroid.exceptions.SessionNotCreatedException: The requested application under test is not configured in selendroid server.
at io.selendroid.server.model.SelendroidStandaloneDriver.createNewTestSession(SelendroidStandaloneDriver.java:207)
at io.selendroid.server.handler.CreateSessionHandler.handle(CreateSessionHandler.java:42)
at io.selendroid.server.SelendroidServlet.handleRequest(SelendroidServlet.java:140)
at io.selendroid.server.BaseServlet.handleHttpRequest(BaseServlet.java:70)
at org.webbitserver.netty.NettyHttpControl.nextHandler(NettyHttpControl.java:78)
at org.webbitserver.netty.NettyHttpControl.nextHandler(NettyHttpControl.java:62)
at org.webbitserver.handler.PathMatchHandler.handleHttpRequest(PathMatchHandler.java:33)
at org.webbitserver.netty.NettyHttpControl.nextHandler(NettyHttpControl.java:78)
at org.webbitserver.netty.NettyHttpControl.nextHandler(NettyHttpControl.java:62)
at org.webbitserver.handler.DateHeaderHandler.handleHttpRequest(DateHeaderHandler.java:21)
at org.webbitserver.netty.NettyHttpControl.nextHandler(NettyHttpControl.java:78)
at org.webbitserver.netty.NettyHttpControl.nextHandler(NettyHttpControl.java:62)
at org.webbitserver.handler.ServerHeaderHandler.handleHttpRequest(ServerHeaderHandler.java:25)
at org.webbitserver.netty.NettyHttpControl.nextHandler(NettyHttpControl.java:78)
at org.webbitserver.netty.NettyHttpControl.nextHandler(NettyHttpControl.java:67)
at org.webbitserver.netty.NettyHttpChannelHandler$2.run(NettyHttpChannelHandler.java:72)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)

Command duration or timeout: 163 milliseconds
Build info: version: '2.41.0', revision: '3192d8a', time: '2014-03-27 17:18:15'
System info: host: 'MSC00082', ip: '192.168.9.150', os.name: 'Windows 7', os.arch: 'amd64', os.version: '6.1', java.version: '1.6.0_21'
Driver info: io.selendroid.SelendroidDriver
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
at java.lang.reflect.Constructor.newInstance(Unknown Source)
at org.openqa.selenium.remote.ErrorHandler.createThrowable(ErrorHandler.java:193)
at org.openqa.selenium.remote.ErrorHandler.throwIfResponseFailed(ErrorHandler.java:145)
at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:595)
at org.openqa.selenium.remote.RemoteWebDriver.startSession(RemoteWebDriver.java:240)
at org.openqa.selenium.remote.RemoteWebDriver.(RemoteWebDriver.java:126)
at org.openqa.selenium.remote.RemoteWebDriver.(RemoteWebDriver.java:139)
at io.selendroid.SelendroidDriver.(SelendroidDriver.java:61)
at community311.launchPage.main(launchPage.java:29)
Caused by: io.selendroid.exceptions.SessionNotCreatedException: The requested application under test is not configured in selendroid server.
io.selendroid.exceptions.SessionNotCreatedException: The requested application under test is not configured in selendroid server.
at io.selendroid.server.model.SelendroidStandaloneDriver.createNewTestSession(SelendroidStandaloneDriver.java:207)
at io.selendroid.server.handler.CreateSessionHandler.handle(CreateSessionHandler.java:42)
at io.selendroid.server.SelendroidServlet.handleRequest(SelendroidServlet.java:140)
at io.selendroid.server.BaseServlet.handleHttpRequest(BaseServlet.java:70)
at org.webbitserver.netty.NettyHttpControl.nextHandler(NettyHttpControl.java:78)
at org.webbitserver.netty.NettyHttpControl.nextHandler(NettyHttpControl.java:62)
at org.webbitserver.handler.PathMatchHandler.handleHttpRequest(PathMatchHandler.java:33)
at org.webbitserver.netty.NettyHttpControl.nextHandler(NettyHttpControl.java:78)
at org.webbitserver.netty.NettyHttpControl.nextHandler(NettyHttpControl.java:62)
at org.webbitserver.handler.DateHeaderHandler.handleHttpRequest(DateHeaderHandler.java:21)
at org.webbitserver.netty.NettyHttpControl.nextHandler(NettyHttpControl.java:78)
at org.webbitserver.netty.NettyHttpControl.nextHandler(NettyHttpControl.java:62)
at org.webbitserver.handler.ServerHeaderHandler.handleHttpRequest(ServerHeaderHandler.java:25)
at org.webbitserver.netty.NettyHttpControl.nextHandler(NettyHttpControl.java:78)
at org.webbitserver.netty.NettyHttpControl.nextHandler(NettyHttpControl.java:67)
at org.webbitserver.netty.NettyHttpChannelHandler$2.run(NettyHttpChannelHandler.java:72)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source

mohammad nadeem

unread,
May 8, 2014, 5:15:44 AM5/8/14
to selen...@googlegroups.com
Hey is there any update for this issue?

Idris Yousifie

unread,
May 8, 2014, 10:28:10 AM5/8/14
to selen...@googlegroups.com
Yes, I am able to launch the emulator using my tests; I have lots of problems with the emulator such as data not loading or maps.

I am using a real device for now and my test is going good

naddy095

unread,
May 12, 2014, 5:06:57 AM5/12/14
to selen...@googlegroups.com
Hi Idris,

Sorry for hijacking your session.
But can you tell me the work around for this issue. Even I get the same exception "The requested application under test is not configured in selendroid server.at io.selendroid.server.model.SelendroidStandaloneDriver.createNewTestSession(SelendroidStandaloneDriver.java:207)
    at io.selendroid.server.handler.CreateSessionHandler.handle(CreateSessionHandler.java:42)"

I am trying to use selendroid inspector with android emulator 2.3.

When I start my server from the terminal it is able to create a new session with app-id and all.

Regards naddy095.

Idris Yousifie

unread,
May 12, 2014, 9:16:05 AM5/12/14
to selen...@googlegroups.com
Hi naddy,

Have you started the selendroid server?  

java -jar selendroid-standalone-0.9.0-with-dependencies.jar -aut your-test.apk

Also be sure to insert the correct SelendroidCapabilities in your code which you can get after starting the server from http://localhost:4444/wd/hub/status

naddy095

unread,
May 12, 2014, 9:20:59 AM5/12/14
to selen...@googlegroups.com
Yes, somehow it has started the app.But my real device is not able to be recognized API level 15 by the script.

Regards

Ido

unread,
May 12, 2014, 9:36:49 AM5/12/14
to selen...@googlegroups.com
When you connect your device, in dos type "adb devices"....  see if your real device shows there. if not, then go to device manager and see if there is any problems with installing drivers for your device

e.g. right click on my computer and click manage and select device manager... look under other devices if there is any error or yellow exclamation mark... 

also in your device you need to ensure usb debugging is enabled; go settings, developer tools and enable usb



---
source:  http://developer.android.com/tools/extras/oem-usb.html#InstallingDriver

To install the Android USB driver on Windows 7 for the first time:

  1. Connect your Android-powered device to your computer's USB port.
  2. Right-click on Computer from your desktop or Windows Explorer, and select Manage.
  3. Select Devices in the left pane.
  4. Locate and expand Other device in the right pane.
  5. Right-click the device name (such as Nexus S) and select Update Driver Software. This will launch the Hardware Update Wizard.
  6. Select Browse my computer for driver software and click Next.
  7. Click Browse and locate the USB driver folder. (The Google USB Driver is located in <sdk>\extras\google\usb_driver\.)
  8. Click Next to install the driver.

Or, to upgrade an existing Android USB driver on Windows 7 with the new driver:

  1. Connect your Android-powered device to your computer's USB port.
  2. Right-click on Computer from your desktop or Windows Explorer, and select Manage.
  3. Select Device Manager in the left pane of the Computer Management window.
  4. Locate and expand Android Phone in the right pane.
  5. Right-click Android Composite ADB Interface and select Update Driver. This will launch the Hardware Update Wizard.
  6. Select Install from a list or specific location and click Next.
  7. Select Search for the best driver in these locations; un-check Search removable media; and check Include this location in the search.
  8. Click Browse and locate the USB driver folder. (The Google USB Driver is located in <sdk>\extras\google\usb_driver\.)
  9. Click Next to upgrade the driv





--
You received this message because you are subscribed to a topic in the Google Groups "selendroid" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/selendroid/Qm7Txfhm5WY/unsubscribe.
To unsubscribe from this group and all its topics, send an email to selendroid+...@googlegroups.com.
Visit this group at http://groups.google.com/group/selendroid.
To view this discussion on the web, visit https://groups.google.com/d/msgid/selendroid/7d5a12ba-5343-4ff5-a22d-7fb8b93ad111%40googlegroups.com.

mohammad nadeem

unread,
May 12, 2014, 9:42:40 AM5/12/14
to
Yes adb is able to recognize the device however, log says the following -

May 12, 2014 4:31:51 PM io.selendroid.SelendroidLauncher lauchServer
INFO: Starting selendroid-server port 4444
May 12, 2014 4:31:51 PM io.selendroid.io.ShellCommand exec
INFO: executing command: /usr/local/adt/adt-bundle-linux-x86_64-20130729/sdk/build-tools/android-4.3/aapt remove /home/xyz/Downloads/selendroid-test-app-0.9.0.apk META-INF/MANIFEST.MF
May 12, 2014 4:31:51 PM io.selendroid.io.ShellCommand exec
INFO: executing command: /usr/local/adt/adt-bundle-linux-x86_64-20130729/sdk/build-tools/android-4.3/aapt remove /home/xyz/Downloads/selendroid-test-app-0.9.0.apk META-INF/CERT.RSA
May 12, 2014 4:31:51 PM io.selendroid.io.ShellCommand exec
INFO: executing command: /usr/local/adt/adt-bundle-linux-x86_64-20130729/sdk/build-tools/android-4.3/aapt remove /home/xyz/Downloads/selendroid-test-app-0.9.0.apk META-INF/CERT.SF
May 12, 2014 4:31:51 PM io.selendroid.io.ShellCommand exec
INFO: executing command: /usr/local/adt/adt-bundle-linux-x86_64-20130729/sdk/build-tools/android-4.3/aapt remove /home/xyz/Downloads/selendroid-test-app-0.9.0.apk META-INF/ANDROIDD.SF
May 12, 2014 4:31:51 PM io.selendroid.io.ShellCommand exec
INFO: executing command: /usr/local/adt/adt-bundle-linux-x86_64-20130729/sdk/build-tools/android-4.3/aapt remove /home/xyz/Downloads/selendroid-test-app-0.9.0.apk META-INF/ANDROIDD.RSA
May 12, 2014 4:31:52 PM io.selendroid.io.ShellCommand exec
INFO: executing command: /usr/lib/jvm/jdk1.7.0_10/bin/jarsigner -sigalg MD5withRSA -digestalg SHA1 -signedjar /home/xyz/Downloads/resigned-selendroid-test-app-0.9.0.apk -storepass android -keystore /home/xyz/.android/debug.keystore /home/xyz/Downloads/selendroid-test-app-0.9.0.apk androiddebugkey
May 12, 2014 4:31:53 PM io.selendroid.builder.SelendroidServerBuilder signTestServer
INFO: App signing output:
May 12, 2014 4:31:53 PM io.selendroid.builder.SelendroidServerBuilder signTestServer
INFO: The app has been signed: /home/xyz/Downloads/resigned-selendroid-test-app-0.9.0.apk
May 12, 2014 4:31:53 PM io.selendroid.io.ShellCommand exec
INFO: executing command: /usr/local/adt/adt-bundle-linux-x86_64-20130729/sdk/build-tools/android-4.3/aapt dump badging /home/xyz/Downloads/resigned-selendroid-test-app-0.9.0.apk
May 12, 2014 4:31:53 PM io.selendroid.io.ShellCommand exec
INFO: executing command: /usr/local/adt/adt-bundle-linux-x86_64-20130729/sdk/build-tools/android-4.3/aapt dump badging /home/xyz/Downloads/resigned-selendroid-test-app-0.9.0.apk
May 12, 2014 4:31:53 PM io.selendroid.server.model.SelendroidStandaloneDriver initApplicationsUnderTest
INFO: App io.selendroid.testapp:0.9.0 has been added to selendroid standalone server.
May 12, 2014 4:31:53 PM io.selendroid.io.ShellCommand exec
INFO: executing command: /usr/local/adt/adt-bundle-linux-x86_64-20130729/sdk/build-tools/android-4.3/aapt remove /tmp/android-driver8770458073547144060.apk META-INF/MANIFEST.MF
May 12, 2014 4:31:53 PM io.selendroid.io.ShellCommand exec
INFO: executing command: /usr/local/adt/adt-bundle-linux-x86_64-20130729/sdk/build-tools/android-4.3/aapt remove /tmp/android-driver8770458073547144060.apk META-INF/CERT.RSA
May 12, 2014 4:31:53 PM io.selendroid.io.ShellCommand exec
INFO: executing command: /usr/local/adt/adt-bundle-linux-x86_64-20130729/sdk/build-tools/android-4.3/aapt remove /tmp/android-driver8770458073547144060.apk META-INF/CERT.SF
May 12, 2014 4:31:53 PM io.selendroid.io.ShellCommand exec
INFO: executing command: /usr/local/adt/adt-bundle-linux-x86_64-20130729/sdk/build-tools/android-4.3/aapt remove /tmp/android-driver8770458073547144060.apk META-INF/ANDROIDD.SF
May 12, 2014 4:31:53 PM io.selendroid.io.ShellCommand exec
INFO: executing command: /usr/local/adt/adt-bundle-linux-x86_64-20130729/sdk/build-tools/android-4.3/aapt remove /tmp/android-driver8770458073547144060.apk META-INF/ANDROIDD.RSA
May 12, 2014 4:31:53 PM io.selendroid.io.ShellCommand exec
INFO: executing command: /usr/lib/jvm/jdk1.7.0_10/bin/jarsigner -sigalg MD5withRSA -digestalg SHA1 -signedjar /tmp/resigned-android-driver8770458073547144060.apk -storepass android -keystore /home/xyz/.android/debug.keystore /tmp/android-driver8770458073547144060.apk androiddebugkey
May 12, 2014 4:31:54 PM io.selendroid.builder.SelendroidServerBuilder signTestServer
INFO: App signing output:
May 12, 2014 4:31:54 PM io.selendroid.builder.SelendroidServerBuilder signTestServer
INFO: The app has been signed: /tmp/resigned-android-driver8770458073547144060.apk
May 12, 2014 4:31:55 PM io.selendroid.server.model.DeviceStore addDevice
INFO: Adding: HardwareDevice [serial=3c3f2f6d, model=null, targetVersion=null]
May 12, 2014 4:31:55 PM io.selendroid.server.model.DeviceStore addDevice
INFO: Adding: HardwareDevice [serial=3c3f2f6d, model=GT-S7562, targetVersion=ANDROID15]
May 12, 2014 4:31:55 PM io.selendroid.server.model.DeviceStore addDevice
INFO: Adding: HardwareDevice [serial=3c3f2f6d, model=GT-S7562, targetVersion=ANDROID15]
May 12, 2014 4:31:55 PM io.selendroid.android.impl.DefaultDeviceManager initializeAdbConnection
INFO: my devices: null
May 12, 2014 4:31:55 PM io.selendroid.io.ShellCommand exec
INFO: executing command: /usr/local/adt/adt-bundle-linux-x86_64-20130729/sdk/tools/android list avds
May 12, 2014 4:31:58 PM io.selendroid.io.ShellCommand exec
INFO: executing command: /usr/local/adt/adt-bundle-linux-x86_64-20130729/sdk/platform-tools/adb devices
May 12, 2014 4:31:58 PM io.selendroid.server.model.DeviceStore addEmulators
INFO: Adding: AndroidEmulator [screenSize=480x800, targetPlatform=ANDROID17, serial=null, avdName=hack]
May 12, 2014 4:31:58 PM io.selendroid.server.model.DeviceStore addEmulators
INFO: Adding: AndroidEmulator [screenSize=768x1280, targetPlatform=ANDROID18, serial=null, avdName=droid]
May 12, 2014 4:31:58 PM io.selendroid.server.SelendroidStandaloneServer start
INFO: selendroid-standalone server has been started on port: 4444
FAILED CONFIGURATION: @BeforeClass startSelendroidServer
org.openqa.selenium.SessionNotCreatedException: Error occurred while starting selendroid-server on the device
io.selendroid.exceptions.SelendroidException: Error occurred while starting selendroid-server on the device
at io.selendroid.android.impl.AbstractDevice.startSelendroid(AbstractDevice.java:228)
at io.selendroid.server.model.SelendroidStandaloneDriver.createNewTestSession(SelendroidStandaloneDriver.java:293)


at io.selendroid.server.handler.CreateSessionHandler.handle(CreateSessionHandler.java:42)
at io.selendroid.server.SelendroidServlet.handleRequest(SelendroidServlet.java:140)
at io.selendroid.server.BaseServlet.handleHttpRequest(BaseServlet.java:70)
at org.webbitserver.netty.NettyHttpControl.nextHandler(NettyHttpControl.java:78)
at org.webbitserver.netty.NettyHttpControl.nextHandler(NettyHttpControl.java:62)
at org.webbitserver.handler.PathMatchHandler.handleHttpRequest(PathMatchHandler.java:33)
at org.webbitserver.netty.NettyHttpControl.nextHandler(NettyHttpControl.java:78)
at org.webbitserver.netty.NettyHttpControl.nextHandler(NettyHttpControl.java:62)
at org.webbitserver.handler.DateHeaderHandler.handleHttpRequest(DateHeaderHandler.java:21)
at org.webbitserver.netty.NettyHttpControl.nextHandler(NettyHttpControl.java:78)
at org.webbitserver.netty.NettyHttpControl.nextHandler(NettyHttpControl.java:62)
at org.webbitserver.handler.ServerHeaderHandler.handleHttpRequest(ServerHeaderHandler.java:25)
at org.webbitserver.netty.NettyHttpControl.nextHandler(NettyHttpControl.java:78)
at org.webbitserver.netty.NettyHttpControl.nextHandler(NettyHttpControl.java:67)
at org.webbitserver.netty.NettyHttpChannelHandler$2.run(NettyHttpChannelHandler.java:72)

at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)
Caused by: java.lang.Throwable: android.util.AndroidException: INSTRUMENTATION_FAILED: io.selendroid.com.xyz.android/io.selendroid.ServerInstrumentation
at com.android.commands.am.Am.runInstrument(Am.java:586)
at com.android.commands.am.Am.run(Am.java:117)
at com.android.commands.am.Am.main(Am.java:80)
at com.android.internal.os.RuntimeInit.finishInit(Native Method)
at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:263)
at dalvik.system.NativeStart.main(Native Method)

Details:
INSTRUMENTATION_STATUS: id=ActivityManagerService
INSTRUMENTATION_STATUS: Error=Unable to find instrumentation target package: com.xyz.android
INSTRUMENTATION_STATUS_CODE: -1
android.util.AndroidException: INSTRUMENTATION_FAILED: io.selendroid.com.xyz.android/io.selendroid.ServerInstrumentation
at com.android.commands.am.Am.runInstrument(Am.java:586)
at com.android.commands.am.Am.run(Am.java:117)
at com.android.commands.am.Am.main(Am.java:80)
at com.android.internal.os.RuntimeInit.finishInit(Native Method)
at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:263)
at dalvik.system.NativeStart.main(Native Method)


Any help on this?


Regards.




To unsubscribe from this group and all its topics, send an email to selendroid+unsubscribe@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "selendroid" group.
To unsubscribe from this group and stop receiving emails from it, send an email to selendroid+unsubscribe@googlegroups.com.

Ido

unread,
May 12, 2014, 9:42:58 AM5/12/14
to selen...@googlegroups.com
you get this when you run your code?


On Mon, May 12, 2014 at 9:41 AM, mohammad nadeem <nadeemm...@gmail.com> wrote:
Yes adb is able to recognize the device however, it says the following -

at io.selendroid.server.handler.CreateSessionHandler.handle(CreateSessionHandler.java:42)
at io.selendroid.server.SelendroidServlet.handleRequest(SelendroidServlet.java:140)
at io.selendroid.server.BaseServlet.handleHttpRequest(BaseServlet.java:70)
at org.webbitserver.netty.NettyHttpControl.nextHandler(NettyHttpControl.java:78)
at org.webbitserver.netty.NettyHttpControl.nextHandler(NettyHttpControl.java:62)
at org.webbitserver.handler.PathMatchHandler.handleHttpRequest(PathMatchHandler.java:33)
at org.webbitserver.netty.NettyHttpControl.nextHandler(NettyHttpControl.java:78)
at org.webbitserver.netty.NettyHttpControl.nextHandler(NettyHttpControl.java:62)
at org.webbitserver.handler.DateHeaderHandler.handleHttpRequest(DateHeaderHandler.java:21)
at org.webbitserver.netty.NettyHttpControl.nextHandler(NettyHttpControl.java:78)
at org.webbitserver.netty.NettyHttpControl.nextHandler(NettyHttpControl.java:62)
at org.webbitserver.handler.ServerHeaderHandler.handleHttpRequest(ServerHeaderHandler.java:25)
at org.webbitserver.netty.NettyHttpControl.nextHandler(NettyHttpControl.java:78)
at org.webbitserver.netty.NettyHttpControl.nextHandler(NettyHttpControl.java:67)
at org.webbitserver.netty.NettyHttpChannelHandler$2.run(NettyHttpChannelHandler.java:72)

at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)
Caused by: java.lang.Throwable: android.util.AndroidException: INSTRUMENTATION_FAILED: io.selendroid.com.xyz.android/io.selendroid.ServerInstrumentation
at com.android.commands.am.Am.runInstrument(Am.java:586)
at com.android.commands.am.Am.run(Am.java:117)
at com.android.commands.am.Am.main(Am.java:80)
at com.android.internal.os.RuntimeInit.finishInit(Native Method)
at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:263)
at dalvik.system.NativeStart.main(Native Method)

Details:
INSTRUMENTATION_STATUS: id=ActivityManagerService
INSTRUMENTATION_STATUS: Error=Unable to find instrumentation target package: com.xyz.android
INSTRUMENTATION_STATUS_CODE: -1
android.util.AndroidException: INSTRUMENTATION_FAILED: io.selendroid.com.xyz.android/io.selendroid.ServerInstrumentation
at com.android.commands.am.Am.runInstrument(Am.java:586)
at com.android.commands.am.Am.run(Am.java:117)
at com.android.commands.am.Am.main(Am.java:80)
at com.android.internal.os.RuntimeInit.finishInit(Native Method)
at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:263)
at dalvik.system.NativeStart.main(Native Method)


Any help on this?


Regards.


On Mon, May 12, 2014 at 7:06 PM, Ido <idris....@gmail.com> wrote:

--
You received this message because you are subscribed to the Google Groups "selendroid" group.
To unsubscribe from this group and stop receiving emails from it, send an email to selendroid+...@googlegroups.com.

--
You received this message because you are subscribed to a topic in the Google Groups "selendroid" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/selendroid/Qm7Txfhm5WY/unsubscribe.
To unsubscribe from this group and all its topics, send an email to selendroid+...@googlegroups.com.
Visit this group at http://groups.google.com/group/selendroid.

mohammad nadeem

unread,
May 12, 2014, 9:47:21 AM5/12/14
to selen...@googlegroups.com
Yes for a android device on android version 4.0.4, But it works fine for another device running android version 4.2.2.

Regards


mohammad nadeem

unread,
May 12, 2014, 9:48:45 AM5/12/14
to selen...@googlegroups.com
It has offcourse listed the device also - model=GT-S7562.Sometimes the log has also said "NOt able  to start the selendroid-server on the device".

Regards

Ido

unread,
May 12, 2014, 9:54:36 AM5/12/14
to selen...@googlegroups.com
Nadeem, i am afraid I can't help in you in that area,  I am only started to use seledroid just recently.. the only andriod version i have used is venison 4.4.2

in your code are you specifying what android you using e.g.

capa.setPlatformVersion(DeviceTargetPlatform.ANDROID17)


mohammad nadeem

unread,
May 12, 2014, 9:58:46 AM5/12/14
to selen...@googlegroups.com
no issues I shall figure it out and let you know.Yes I have provided the mentioned capability.As for your situation I will advice you to use "appium" for API level 19 instead of "selendroid".

Regards.


Ido

unread,
May 12, 2014, 10:11:49 AM5/12/14
to selen...@googlegroups.com

Ido

unread,
Jun 2, 2014, 9:33:32 AM6/2/14
to selen...@googlegroups.com
Has any one upgraded to selendroid 10?  I did it and now my tests wont work.... when I run my test, the app in the tablet launches but I get the following error

Exception in thread "main" org.openqa.selenium.remote.UnreachableBrowserException: Could not start a new session. Possible causes are invalid address of the remote server or browser start-up failure.
Build info: version: '2.42.1', revision: '68b415a', time: '2014-05-29 16:17:18'

System info: host: 'MSC00082', ip: '192.168.9.150', os.name: 'Windows 7', os.arch: 'amd64', os.version: '6.1', java.version: '1.6.0_21'
Driver info: driver.version: SelendroidDriver
    at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:594)
    at org.openqa.selenium.remote.RemoteWebDriver.startSession(RemoteWebDriver.java:241)
    at org.openqa.selenium.remote.RemoteWebDriver.<init>(RemoteWebDriver.java:127)
    at org.openqa.selenium.remote.RemoteWebDriver.<init>(RemoteWebDriver.java:140)
    at io.selendroid.SelendroidDriver.<init>(SelendroidDriver.java:70)
    at community311.launchPage.testLaunchMainPage(launchPage.java:47)
    at community311.launchPage.main(launchPage.java:28)
Caused by: org.apache.http.client.ClientProtocolException
    at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:188)
    at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:72)
    at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:57)
    at org.openqa.selenium.remote.HttpCommandExecutor.fallBackExecute(HttpCommandExecutor.java:204)
    at org.openqa.selenium.remote.HttpCommandExecutor.execute(HttpCommandExecutor.java:173)
    at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:573)
    ... 6 more
Caused by: org.apache.http.HttpException: Unsupported Content-Coding: none
    at org.apache.http.client.protocol.ResponseContentEncoding.process(ResponseContentEncoding.java:98)
    at org.apache.http.protocol.ImmutableHttpProcessor.process(ImmutableHttpProcessor.java:139)
    at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:200)
    at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:85)
    at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:108)
    at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:186)
    ... 11 more

Sumit Shrivaastav

unread,
Jun 3, 2014, 7:28:13 AM6/3/14
to selen...@googlegroups.com
Hi Idrish,
             Please share your script..Let me check if i can help you in any wayws.....

Ido

unread,
Jun 3, 2014, 8:09:12 AM6/3/14
to selen...@googlegroups.com
I found the problem, I was running the server using this command

java -jar selendroid-standalone-0.09.0-with-dependencies.jar -aut c:\apk\test.apk


i Switched to command below and it works



java -jar selendroid-standalone-0.10.0-with-dependencies.jar -app c:\apk\test.apk




Shubham Saxena

unread,
Dec 16, 2014, 5:30:00 AM12/16/14
to selen...@googlegroups.com
Hi Naddy,
Did you manage to find out any solution for this Issue. I am also facing the similar issue while using my app. But in my case it is working fine for the App provided by selendroid i.e "selendroid-test-app-0.10.0.apk".
Please share your findings.

Regards:
Shubham

vishal gowda

unread,
Apr 30, 2015, 4:33:40 AM4/30/15
to selen...@googlegroups.com
I am also facing the similar problem when trying to run test on Emulator

" java -jar selendroid-standalone-0.15.0-with-dependencies.jar -app selendroid-test-app-0.10.0.apk " command Executes successfully without an error



Selenium Server starts on port 4444 , I can see the status in URL: http://localhost:4444/wd/hub/status

 --------------------
{"value":{"os":{"name":"Windows 7","arch":"x86","version":"6.1"},"build":{"browserName":"selendroid","version":"0.15.0"},
"supportedDevices":[{"emulator":true,"screenSize":"(320, 480)","avdName":"AVD","platformVersion":"19"}],
"supportedApps":[{"mainActivity":"io.selendroid.androiddriver.WebViewActivity","appId":"io.selendroid.androiddriver:0.15.0",
"basePackage":"io.selendroid.androiddriver"},{"mainActivity":"io.selendroid.testapp.HomeScreenActivity",
"appId":"io.selendroid.testapp:0.10.0","basePackage":"io.selendroid.testapp"}]},"status":0}

-----------------

After the server is started trying to execute code:
@BeforeClass
public static void startSelendroidServer() throws Exception
{
SelendroidCapabilities caps = new SelendroidCapabilities("io.selendroid.androiddriver:0.15.0");
dr = new SelendroidDriver(caps);
}

@Test
public void testShouldBeAbleToEnterText()
{
WebElement inputField = dr.findElement(By.id("my_text_field"));
inputField.sendKeys("Selendroid");
Assert.assertEquals("Selendroid", inputField.getText());
}

Shows the error/Exception message in Command prompt
SEVERE: Error occurred while starting Selendroid session
io.selendroid.server.common.exceptions.SessionNotCreatedException: The requested

application under test is not configured in selendroid server.
        at io.selendroid.standalone.server.model.SelendroidStandaloneDriver.getA
ndroidApp(SelendroidStandaloneDriver.java:396)
at io.selendroid.standalone.server.model.SelendroidStandaloneDriver.crea
teNewTestSession(SelendroidStandaloneDriver.java:221)
at io.selendroid.standalone.server.model.SelendroidStandaloneDriver.crea
teNewTestSession(SelendroidStandaloneDriver.java:210)
at io.selendroid.standalone.server.handler.CreateSessionHandler.handleRe
quest(CreateSessionHandler.java:40)
at io.selendroid.standalone.server.BaseSelendroidStandaloneHandler.handl
e(BaseSelendroidStandaloneHandler.java:45)
at io.selendroid.standalone.server.SelendroidServlet.handleRequest(Selen
droidServlet.java:131)
at io.selendroid.server.common.BaseServlet.handleHttpRequest(BaseServlet
.java:67)
at io.selendroid.server.common.http.ServerHandler.channelRead(ServerHand
ler.java:53)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(Abst
ractChannelHandlerContext.java:333)
Reply all
Reply to author
Forward
0 new messages