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.
Using Datepicker on Android 6 (Marshmallow) I am not able to select the year, as it only displays the current year to be selected.
I look into documentation and created a datepicker from scratch. Same issue exists.
I posted this on forum but nobody seem to respond.
I am using Xamarin Studio 5.9.0(build 0)
I'm currently unable to replicate this bug.
Is this only happening in API 23 Android 6.0? Does it work find on a device running API 21/22 Lollypop?
Can you please confirm the device(s) you're testing with?
Could you attach a sample that exhibits the problem?
Hi, thank you for looking into it.
Yes it work on Lollipop running api 21/22
and i used the exact same sample given on xamarin guide here
Also used the fragment way to implement this
Both shows only 1 year available for the selection
Let me know if you need anything else.
I actually used the same sample to test this. It worked fine on my Nexus 6. What device are you testing with?
I tested it with xamarin android player Nexus 4 (marshmallow) api 23
Also, i have heard from Samsung Galaxy 6 users that they are having this issue. that's why i am looking into it.
is there any chance that my xamarin studio configuration/ project configuration may induce this behavior?
I am still stuck with this bug. Any help?
Unfortunately, we’re unable to reproduce this report. If this issue is still occurring for you, please reopen this issue and attach a reproduction to the bug by starting with a clean Xamarin.Android project adding just the code necessary to demonstrate the issue.