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.
Since updating to Mono3 and Xcode 5, Ive noticed this value defaults to what appears to be US settings. I noticed this because FirstDayOfWeek is Sunday. In the UK it should be Monday and before updating it was correct. I wouldn't know if this is a bug with Mono3, or Xamarin.iOS. But at least you guys can take a look and figure it out.
I need some way to reproduce the issue reliably.
var ci = new CultureInfo ("en-GB");
works as expected
Try setting the device to be based in the UK. Then:
Returns Sunday. Should by Monday.
Happy to demonstrate over Skype with 2 separate devices (iPhone 5s and iPad Mini 2)
Just tried with a new single view app, has the same issue.
This works as expected with master version of Xamarin.iOS and International Region Format set to United Kingdom
Closed without even taking a look over Skype? I can replicate this 100% using current stable.
Poor showing guys. Not good enough. Contact me tmw to login over Skype or I'll escalate this.
A user posted the link to the above bug, which looks like you fixed in master, you couldn't have mentioned that??
Can you at least tell me when this will be in stable?
This should be available next release after 7.1 (read as nothing imminent)
*** This bug has been marked as a duplicate of bug 17151 ***