Skip to content
This repository has been archived by the owner on Dec 31, 2022. It is now read-only.

GetDevices fails if device name contains a white space #42

Closed
ghost opened this issue Jun 2, 2016 · 8 comments
Closed

GetDevices fails if device name contains a white space #42

ghost opened this issue Jun 2, 2016 · 8 comments

Comments

@ghost
Copy link

ghost commented Jun 2, 2016

Hi,

this is bug:

camalot/madb#27

Is also a bug here. It results in an empty list with an "Invalid device list data"-Exception.

Greetings

@qmfrederik
Copy link
Contributor

Hi @Viper2k4 ,

Thanks for the feedback! I may need your help to further troubleshoot this -- the bug you reference was reported by me on Codeplex and I've carried over the unit test for that case, it's in DeviceDataTests

That makes me guess you're having slightly different device data which SharpAdbClient fails to process. Could you let me know which device data you are seeing? Do you have a stack trace?

Thanks!

@ghost
Copy link
Author

ghost commented Jun 3, 2016

Hi,

i would, but i can not :/

i got this error with a device of on colleague. But i see him next time in one or two weeks. But i try to get the devicename if possible.

Greetings

@ghost
Copy link
Author

ghost commented Jun 8, 2016

Hi,

now i got access to the devies. Its an Nexus 5X with Android N (prev 3). Here the Error with DeviceData:

Invalid device list data '0100a9ee51a18f2b device product:bullhead model:Nexus_5X device:bullhead features:shell_v2,cmd'

@qmfrederik
Copy link
Contributor

Cool, I'll check it & get back to you. Thanks!

@ghost
Copy link
Author

ghost commented Jun 8, 2016

It looks like the "features:shell_v2,cmd" at the end brakes the regex. It seems "features" is expected a bit earlyer in the string. If i remove it the regex work just fine.

bartsaintgermain added a commit that referenced this issue Jun 9, 2016
Add support for emulator devices
@qmfrederik
Copy link
Contributor

Thanks, I've just pushed a commit to master that should fix this issue, see this unit test.

Let me know if this fixes the issue for you (when you have access to the device :))

@ghost
Copy link
Author

ghost commented Jun 10, 2016

It should fix the issue. But i cant validate it :(. But it think it should be fine, because the test based 1:1 on "my problem device" :)

I think we can close the issue. If i got an other Error i will report it ^^

@ghost ghost closed this as completed Jun 10, 2016
@ghost
Copy link
Author

ghost commented Jun 13, 2016

So i got my hands on the device and i can 100% proof that the fix work :)

This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant