LocalizationService does not set a culture in Windows (Unpackaged) Head

[Seekuhnetz]

Current behavior

I created a new App with the UnoApp Template and Localization and Configuration enabled.
I added the ToggleLocalizationAsync() of this page.

The Current Culture gets updated in the (Packaged) but not in the (Unpackaged) Windows Head.

I also had to add .Section<LocalizationConfiguration>() under configBuilder in my App.cs else the SupportedCultures would be empty.
I guess the problem could be fixed if i was able to also add .Section<LocalizationSettings>(). But i can not because it is internal.

Expected behavior

The Current Culture should be updated in the (Unpackaged) Windows Head like in the (Packaged) Head.

How to reproduce it (as minimally and precisely as possible)

• Create a new Uno App with the UnoApp Template and Localization and Configuration enabled.
• Add the ToggleLocalizationAsync() of this page.
• Run the Windows (Unpackaged) Head

Workaround

No response

Works on UWP/WinUI

None

Environment

No response

NuGet package version(s)

No response

Affected platforms

Windows

IDE

Visual Studio 2022

IDE version

No response

Relevant plugins

No response

Anything else we need to know?

No response

[Seekuhnetz]

@nickrandolph
I just tested this and it looks like that changing the language with ILocalizationService still does not work in the Unpackaged Head of WinUI.
Packaged Head works fine.
SetLanguageTest.zip

[nickrandolph]

@nickrandolph I just tested this and it looks like that changing the language with ILocalizationService still does not work in the Unpackaged Head of WinUI. Packaged Head works fine. SetLanguageTest.zip

Thanks for following up on this. I've confirmed that:

• ILocalizationService does appear to be saving the change to the current culture
• For some reason the saved culture isn't being applied correctly when run as unpackaged.
  This is evident both in a new application created with latest template but also in the Playground application in this repository

[nickrandolph]

Looks like we might be stalled on this microsoft/WindowsAppSDK#4181

[Seekuhnetz]

I also noticed that DateTimes are in the wrong format for the Unpackaged Head.
The culture does not get set to the system one and is instead set to "en".
Again this is not an issue in the Packaged Head.

I fixed the issue with following workaround:

App.Dispatcher.TryEnqueue(() =>
{
    CultureInfo ci = new CultureInfo("de-DE");
    Thread.CurrentThread.CurrentCulture = ci;
    Thread.CurrentThread.CurrentUICulture = ci;
});

[Seekuhnetz]

@nickrandolph it looks like microsoft/WindowsAppSDK#4181 has been closed.