Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report on
Developer Community or GitHub with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
I have an Android tablet that will report its serial number/qualifier (using "adb devices") with a space (in my case "ZTB X").
This causes the deploy to device to fail when getting the device API version using this command:
1>C:\Users\<user>\AppData\Local\Android\android-sdk\platform-tools\adb.exe -s ZTB X shell getprop ro.build.version.sdk
1>"adb.exe" exited with code 1.
1>A numeric comparison was attempted on "$(_DeviceSdkVersion)" that evaluates to "" instead of a number, in condition "$(_DeviceSdkVersion) >= 21".
The failure is due to the '-s ZTB X' part. Since there is a space, the proper command should be adb.exe -s "ZTB X" shell getprop ro.build.version.sdk
Just to add to my description, here is the output of the ADB command:
List of devices attached
ZTB X device
Thank you for the report. Unfortunately, at this time, we're unable to reproduce this issue. I don't currently have access to any devices with a space in the qualifier. Alex - could you let us know what device you were using? I haven't been able to locate a device based on "ZTB X". I'll try to source something to test moving forward.
Setting to NEEDINFO for the time being.
Because we have not received a reply to our request for more information we are closing this issue. If you are still encountering this issue, please reopen the ticket with the requested information. Thanks!