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.
": _ / " keys dont work from Mac keyboard to the device. Letters and numbers work fine but special keys have issues.
This is fixed in master, will be in the next update- it will also require updated devices to be downloaded.
Fixed with new image updates available now
Updated play.... same issue ": /" do not work in player
Just installed Xamarin Android Player 0.3.7 on Mac and can confirm that ':' and '/' characters do not work.
Do you have the latest devices images installed as well? I've just been testing 0.3.7 on Mac, with fresh downloads of the Nexus 4 (KitKat), (Lollipop) and (Jelly Bean) images. I cannot replicate this issue.
Can you ensure you are using the updated device images and confirm the system language and keyboard layout you are using.
removed the app and reinstalled the player and downloaded a fresh Nexus 4(Lollipop) issue persists.
Can you please retest in the latest version (0.4.4.0), if it still does not work - can you let me know what language and regional settings your system is set to.
just updated to 4.4. Also deleted and downloaded the image for the nexus 4 lollipop. Issue still persists.
Region: United States
Mac OS-X 10.10.3
*** Bug 29407 has been marked as a duplicate of this bug. ***
Just downloaded the latest and everything seems to work as expected
Marking as resolved, as per comment 10.