Blazor WASM Standalone is always in Finished State in Aspire Dashboard. This is giving error and URL for app is empty in dashboard.

[Abdul Rahman (fingers10)]

I have an identity server project - IDP.csproj, api project - PublicAPI.csproj and a blazor wasm standlone app - Web.csproj. All running in .net10. Here is my aspire setup

var builder = DistributedApplication.CreateBuilder(args);

var IdpDb = builder.AddPostgres("IDP-Postgres")
        .AddDatabase("IdentityConnectionString", "Identity");

var ApiDb = builder.AddPostgres("API-Postgres")
        .AddDatabase("CommandsConnectionString", "Data");

var Idp = builder.AddProject<Projects.IDP>("IDP")
        .WithReference(IdpDb)
        .WithReference(ApiDb);

var IdpUrl = Idp.GetEndpoint("https");

var Api = builder.AddProject<Projects.PublicAPI>("API")
        .WithReference(ApiDb);

var ApiUrl = Api.GetEndpoint("https");

var Web = builder.AddProject<Projects.Web>("Web")
        .WithEnvironment("ApiBaseAddress", ApiUrl)
        .WithEnvironment("OidcConfiguration__Authority", IdpUrl);

var WebUrl = Web.GetEndpoint("https");

Web
        .WithEnvironment("OidcConfiguration__RedirectUri", $"{WebUrl}/authentication/login-callback")
        .WithEnvironment("OidcConfiguration__PostLogoutRedirectUri", $"{WebUrl}/authentication/logout-callback");

Api
        .WithEnvironment("IDPUrl", IdpUrl)
        .WithEnvironment("WebClient", WebUrl);

Idp
        .WithEnvironment("APIClient", ApiUrl)
        .WithEnvironment("WebClient", WebUrl);
        
await builder.Build().RunAsync();

When I look at the dashboard, I see Web is always Finished state. When I look at the logs for Web, I see

Executing command 'resource-start'.
Successfully executed command 'resource-start'.
A fatal error was encountered. The library 'libhostpolicy.dylib' required to execute the application was not found in '/Users/xxxx/Projects/Personal/xxxx/Web/bin/Debug/net10.0/'.
Failed to run as a self-contained app.
  - The application was run as a self-contained app because '/Users/xxxx/Projects/Personal/xxxx/Web/bin/Debug/net10.0/Web.runtimeconfig.json' did not specify a framework.
  - If this should be a framework-dependent app, specify the appropriate framework in '/Users/xxxx/Projects/Personal/xxxx/Web/bin/Debug/net10.0/Web.runtimeconfig.json'.

Please assist me on what I'm missing in my blazor wasm standalone app - Web.csproj

[Abdul Rahman (fingers10)]

Benjamin (@BenjaminCharlton) I even tried Aspire4Wasm but still seeing the same issue. Any hints?

[Benjamin (BenjaminCharlton)]

Hi! I have seen this too, but I just accepted it: it never bothered me. I thought to myself: it's a WebAssembly app running in the browser, so once the server has served it to the client machine, it is literally "Finished" with it. The app is disconnected from Aspire, disconnected from the server and running in the browser just like Angular or anything JavaScript would be. Do you disagree? Should it not say "Finished"?

[Abdul Rahman (fingers10)]

Benjamin (@BenjaminCharlton) But when you do dotnet run on your apphost it shows the status as Running for blazor wasm project. Aspire shows the status as Finished only when you run apphost in debug mode.

[Benjamin (BenjaminCharlton)]

I wouldn't be able to comment on that exact behaviour, as I don't know much about Aspire and that behaviour isn't a blocker for me.

I really like Aspire but I had to code Aspire4Wasm to resolve what I viewed as a blinspot in Aspire to Blazor WebAassembly. It got me unblocked and I hope it got other people unblocked too.

I invested a lot of effort making a Pull Request to bring that functionality into Aspire, but it hasn't been looked at. Maybe Blazor WebAassembly is a low priority for Microsoft nowadays...