Bug 59725 - CultureInfo.CurrentCulture always returns 'en-US' in iOS 11
Summary: CultureInfo.CurrentCulture always returns 'en-US' in iOS 11
Status: RESOLVED DUPLICATE of bug 59604
Alias: None
Product: Forms
Classification: Xamarin
Component: iOS ()
Version: 2.3.4
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2017-09-25 15:13 UTC by Kelley Ricker
Modified: 2017-09-25 17:20 UTC (History)
3 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and 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 Links.

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.

Related Links:

Description Kelley Ricker 2017-09-25 15:13:27 UTC
I've noticed that in iOS 11 the value of System.Globalization.CultureInfo.CurrentCulture always seems to return 'en-US' regardless of the language actually set on device. I never saw this issue with iOS 10 (that is it always returned the language of the device) so it seems like it is a bug.
Comment 1 Paul DiPietro [MSFT] 2017-09-25 15:17:37 UTC
Very likely related to 59604

*** This bug has been marked as a duplicate of bug 59604 ***
Comment 2 NMackay 2017-09-25 17:05:49 UTC
Any chance that bug could be made public so we can track it?
Comment 3 Paul DiPietro [MSFT] 2017-09-25 17:20:41 UTC
Should be fixed now