[arquillian-issues] [JBoss JIRA] (ARQ-1581) Droidium does not work with remote emulators

[Karel Piwko (JIRA)]

    [ https://issues.jboss.org/browse/ARQ-1581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12927314#comment-12927314 ] 

Karel Piwko commented on ARQ-1581:
----------------------------------

This would need to fix DDMLIB or provide alternative way how Droidium works with Android SDK.
                
> Droidium does not work with remote emulators
> --------------------------------------------
>
>                 Key: ARQ-1581
>                 URL: https://issues.jboss.org/browse/ARQ-1581
>             Project: Arquillian
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Extension - Droidium
>    Affects Versions: droidium_1.0.0.Alpha2
>            Reporter: Karel Piwko
>            Assignee: Stefan Miklosovic
>
> *When*:
> I use Android Jenkins Plugin to start the device
> *Then*:
> It starts the emulator using remote syntax, that is including --port port1,port2
> *Expect*:
> Drodium will connect to already running emulator.
> *Actual problem*:
> AndroidDevice and IDevice isEmulator() call is not able to parse the data retrieved from adb devices. This results into Droidium trying to start emulator with the same name, however this emulator is already started so event marking correct startup is never send and test fails.
> Output:
> {code}
> export ANDROID_ADB_SERVER_PORT=52892
> [tester at fedora19 ~]$ ANDROID_SDK_HOME=`pwd`/workspace/mobile-eap-test ./tools/android-sdk/platform-tools/adb devices
> List of devices attached 
> localhost:46689	device
> {code}
> However, emulators are expected to be in format of emulator-XYZ. 
> Drodium should be able to modify the behavior to handle this correctly.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira