Skip to content

Fix WASM gallery startup stall/blank by forcing UnoRuntimeIdentifier #314

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
MartinZikmund wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Fix WASM gallery startup stall/blank by forcing UnoRuntimeIdentifier #314

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions ProjectHeads/App.Head.Wasm.props
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,6 +4,17 @@
<TargetFramework>$(WasmHeadTargetFramework.Split(';')[0])</TargetFramework>
</PropertyGroup>

<!--
TargetFramework is set late (above), so NuGet's net9.0-conditional import of
Uno.*.Runtime.WebAssembly.props is skipped and UnoRuntimeIdentifier never gets set. Without it
Uno deploys the reference Uno.UI.dll (no embedded JS) instead of the WebAssembly runtime build,
so the app stalls on the splash. Set it explicitly so the runtime-assembly swap runs.
-->
<PropertyGroup>
<UnoRuntimeIdentifier>WebAssembly</UnoRuntimeIdentifier>
<UnoIsWebAssemblyBrowserHead>true</UnoIsWebAssemblyBrowserHead>
</PropertyGroup>

<Import Project="$(MSBuildThisFileDirectory)\App.Head.Uno.props" />

<PropertyGroup Condition="'$(Configuration)'=='Release'">
Expand Down
Loading