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.
Created attachment 18433 [details]
Screen capture from the first and second read.
I'm developing an app for tablet windows 10 in xamarin.forms for upw.
I need a searchbar to use barcodes scanned via an usb barcode scanner.
The scanner is configured to add an enter key after the code that's read.
The first read show's on the searchBar, triggers the command but the text property is empty.
if read again, without clearing the searchbar text, it reads the same string (now showing twice) and triggers the command. But showing in the text property only the text from the 2 read.
Both other events TextChanged and SearchButtonPressed behave the same way.
You can test this behavior using the example in https://developer.xamarin.com/api/type/Xamarin.Forms.SearchBar/.
Are you still experiencing this issue on the latest stable/prerelease, and does it function correctly on the other platforms, to your knowledge? I'll have to see if I can find someone with a barcode scanner to verify.
Updating to NEEDINFO for upkeep purposes until further information is received.
For now, because we have not received a reproduction and the response was asked for roughly three months ago and have not received any in the last few days, we are closing this issue. If you are still experiencing the problem on the latest prerelease or nightly build, please reopen this with a reproduction project.