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
GitHub or Developer Community 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 20327 [details]
Goood day Xamarin team support
In IOS only, using the latest Xamarin Forms stable version, most of culture combinations working fine but "es-US" culture info is wrongly applying formatting over the NumberGroupSeparator, after the first group, next groups is no applied the separator.
value = 123456789
this.NumberUSA = value.ToString("N0", new CultureInfo("es-US")); // 123456,789
this.NumberUSA = value.ToString("N0", new CultureInfo("en-US")); // 123,456,789
this.NumberEspana = value.ToString("N0", new CultureInfo("es-ES")); // 123.456.789
this.NumberColombia = value.ToString("N0", new CultureInfo("es-CO")); // 123.456.789
this.NumberArgentina = value.ToString("N0", new CultureInfo("es-AR")); // 123.456.789
As we can see, the first "es-US" culture formatting is wrong.
All others are fine.
The attached test app project is used to verify the reported case.
I can confirm I'm getting the same error, but this looks like it's actually a bug with Mono as opposed to XI itself. I get the same output if I use the given code sample in a .net console project on mac.
Fixed in master
After one bug is fixed in master, how long it will take to be released in the next stable version. If this fix is in a pre-release version, which one I have to use, or how could I use it?
Thanks in advance.