Following this page resulted in missing 200% scale images from packaged app installation.

[istvan-pal-shapr3d]

I needed to "force include" all language resources in my package. Following the description in Option 2 I deleted the Language qualifier name and added <AppxDefaultResourceQualifiers>Language=en;es;fr</AppxDefaultResourceQualifiers> as instructed. However this resulted in having no images for 200% scale when the app is installed from package. In a related document I found that <AppxDefaultResourceQualifiers> can also have default value for Scale and many other things (and 200% scale was the default before these changes in my project). Once I explicitly added Scale=200 to <AppxDefaultResourceQualifiers> the issue seemed to be resolved. Based on this to mee it seems that by adding <AppxDefaultResourceQualifiers> to the configuration I lost the built-in defaults.
So I was wondering that either I didn't use the content of this page as it was intended or this information is missing? And that brings up the question what are the other defaults and should those be specified too?

---

Document Details

⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

• ID: 836865ec-ea89-1baf-141b-c415940b6e5c
• Version Independent ID: 6c610dcb-0f1c-c58e-b42c-4aa06687c9d6
• Content: Build resources into your app package - UWP applications
• Content Source: uwp/app-resources/build-resources-into-app-package.md
• Product: uwp
• Technology: data-and-files
• GitHub Login: @alvinashcraft
• Microsoft Alias: aashcraft

[alvinashcraft]

Thanks for submitting this issue @istvan-pal-shapr3d. Did you have the same problem if you followed the steps in Option 1 without specifying a value for Scale?

[istvan-pal-shapr3d]

Hi @alvinashcraft!
It was some time ago, I may not remember correctly, but I think I was working with Option 2 from the start as it seemed to be a better fit for our build environment. So I can't tell if Option 1 had the same effect or not. We only realized the issue a bit late in the process as local builds or non 200% scale builds didn't produce any visible issue so when I tried to fix it I didn't go back to try Option 1.