Suttisak Denduangchai

I've exactly same problem. My hosted Blazor WASM doesn't use any prerendering and authenticate with IdentityServer4. .NET Version 7.0.100-rc.1.22431.12 ``` crit: Microsoft.AspNetCore.Components.WebAssembly.Rendering.WebAssemblyRenderer[100] Unhandled exception rendering component: ConstructorContainsNullParameterNames, Microsoft.AspNetCore.Components.WebAssembly.Authentication.RemoteAuthenticationService`3+JavaScriptLoggingOptions[Microsoft.AspNetCore.Components.WebAssembly.Authentication.RemoteAuthenticationState,Microsoft.AspNetCore.Components.WebAssembly.Authentication.RemoteUserAccount,Microsoft.AspNetCore.Components.WebAssembly.Authentication.ApiAuthorizationProviderOptions] SerializationNotSupportedParentType, System.Object...

@MackinnonBuck There is no space in my solution and project paths (`C:\Users\Sutti\source\repos\OccMedCheckUpBlazor\OccMedCheckUpBlazor.sln`,`C:\Users\Sutti\source\repos\OccMedCheckUpBlazor\OccMedCheckUpBlazor\Client\OccMedCheckUpBlazor.Client.csproj`, `C:\Users\Sutti\source\repos\OccMedCheckUpBlazor\OccMedCheckUpBlazor\Server\OccMedCheckUpBlazor.Server.csproj`) But there is a space in dotnet component which are installed to `Program Files` folder such as...

@MackinnonBuck It occurs on both Visual Studio and `dotnet publish`. This issue only occurs when I try to publish (add `false` in Blazor WASM csproj) using Windows. If I publish...

@MackinnonBuck Here a minimal repo [https://github.com/Lukespacewalker/BlankBlazorWASM](https://github.com/Lukespacewalker/BlankBlazorWASM). But I think this problem occurs only in Windows because .NET SDK is installed in `Program Files` folder, containing space in path, that break...

@MackinnonBuck Sorry for late reply. I've install 7.0 SDK daily build and it fixs the problem