Skip to content

[Sample App] Non-WASM supported components showing up in WASM Sample App #5

@michael-hawker

Description

@michael-hawker

Describe the bug

Components like Shimmer which use composition and aren't supported in WASM, have a Multi-target that defines as such. However, it's still appearing in the WASM sample app when generating the all solution.

This is tangentially related to the local component head for WASM being copied as well when it's not supported (not sure if we have another issue for that, maybe want a separate one?).

Steps to reproduce

1. GenerateAllSolution
2. Run WASM head
3. Open controls, see Shimmer
4. Click on Shimmer
5. See error in output as Shimmer page doesn't exist for WASM, shouldn't be listed in app.

Expected behavior

Shimmer not shown in WASM app head.

Screenshots

No response

Code Platform

  • UWP
  • WinAppSDK / WinUI 3
  • Web Assembly (WASM)
  • Android
  • iOS
  • MacOS
  • Linux / GTK

Windows Build Number

  • Windows 10 1809 (Build 17763)
  • Windows 10 1903 (Build 18362)
  • Windows 10 1909 (Build 18363)
  • Windows 10 2004 (Build 19041)
  • Windows 10 20H2 (Build 19042)
  • Windows 10 21H1 (Build 19043)
  • Windows 11 21H2 (Build 22000)
  • Other (specify)

Other Windows Build number

No response

App minimum and target SDK version

  • Windows 10, version 1809 (Build 17763)
  • Windows 10, version 1903 (Build 18362)
  • Windows 10, version 1909 (Build 18363)
  • Windows 10, version 2004 (Build 19041)
  • Other (specify)

Other SDK version

No response

Visual Studio Version

No response

Visual Studio Build Number

No response

Device form factor

No response

Additional context

No response

Help us help you

Yes, but only if others can assist.

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

Status

✅ Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions