1.8 has disrupted my localization

[BigHeadDev]

Describe the bug

My program supports multilingual localization and has 7 languages.
When I was debugging, it could correctly recognize the language zh-Hans on my computer and display it in Chinese.
When I packaged it into MSIX and installed it, it could only be displayed in English.

---

Through debugging, I found that after packaging and installation, there is only one programming language left, 'en'. Here is my debugging information

Debug：
ApplicationLanguages.ManifestLanguages ：en,pt,fr,ja,zh-hans,zh-hant,es
ApplicationLanguages.Languages：zh-hans

install msix：
ApplicationLanguages.ManifestLanguages ：en
ApplicationLanguages.Languages：en

Steps to reproduce the bug

1. Add multilingual resources resw
2. Package and run
3. The program cannot use computer UI language as the program UI language

Expected behavior

Check the upgrade process of 1.7-1.8 for any damage mainfest that may have caused localization failure

Screenshots

No response

NuGet package version

Windows App SDK 1.8.0: 1.8.250907003

Packaging type

Packaged (MSIX)

Windows version

Windows 11 version 23H2 (22631, June 2025 Update)

IDE

Visual Studio 2022

Additional context

No response

[BigHeadDev]

Generating an msixbundle will 100% cause this issue, but not generating a bundle will not

[DarranRowe]

Can you check the bundle? Check if it has split the resources, and if it has, check to see if the split resources were included in the bundle. The Visual Studio build log will show if the resources has been split.

Also, just for clarification, since this wasn't mentioned, was the project generated as a single project, or does it have the external packaging project.

[BigHeadDev]

Can you check the bundle? Check if it has split the resources, and if it has, check to see if the split resources were included in the bundle. The Visual Studio build log will show if the resources has been split.

Also, just for clarification, since this wasn't mentioned, was the project generated as a single project, or does it have the external packaging project.

• The bundle package does not include split resource packages, such as MyApp.x64.de.de.msix, MyApp.x64.zh-cn.msix, and so on
• When packaging, only some. scalexxx.msix logs appear in the VS console.
• My project is a single project

[JulienTheron]

We came across the same issue after upgrading to WinAppSDK 1.8. The created bundle contains only one language, and Dependencies are missing as well.
Setting AppxBundle to Never fixes the issue, but we were hoping to stop using MakeAppx to create the bundle ourselves.

[BigHeadDev]

We came across the same issue after upgrading to WinAppSDK 1.8. The created bundle contains only one language, and Dependencies are missing as well. Setting AppxBundle to Never fixes the issue, but we were hoping to stop using MakeAppx to create the bundle ourselves.

Unfortunately, the Microsoft Store has a requirement: once you have submitted a bundle and it has been approved for listing. So you will never be able to submit a single architecture package

[JulienTheron]

We're not using the Microsoft Store but you should be able to go around it by creating the bundle manually. You can have a look here: https://platform.uno/docs/articles/uno-publishing-windows-packaged-signed.html.

[torum]

I've also encountered this issue with my WinUI3 app. While testing locally, my app correctly displays localized language in both unpaclaged and packaged, but after I packaged it using Visual Studio tool and submitted to the store and download via app store, there is no more localization.

PS. may not be related, but I keep getting
1>WINAPPSDKGENERATEPROJECTPRIFILE : warning : PRI249: 0xdef00520 - Invalid qualifier: DESKTOP-EVENTLOG-INSTRUMENTATION
warning since I upgraded to 1.8 when I create app packages.