-
Notifications
You must be signed in to change notification settings - Fork 10.3k
Blazor linking/trimming issue in RemoteAuthenticationService: "System.NotSupportedException: ConstructorContainsNullParameterNames" #44811
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.
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
Comments
Tagging @javiercn, although I'm not sure a fix can be in place until RTM. |
I was able to reproduce the bug on RC2, so it looks like the fix missed the cutoff. However, I tried the latest RTM build from https://github.com/dotnet/installer and everything worked as expected, so the fix should be available in GA. @yugabe, would you be able to confirm if the latest RTM build resolves your issue? |
Hi @yugabe. We have added the "Needs: Author Feedback" label to this issue, which indicates that we have an open question for you before we can take further action. This issue will be closed automatically in 7 days if we do not hear back from you by then - please feel free to re-open it if you come back to this issue after that time. |
Thanks @MackinnonBuck for the answer, I tried the daily build, and it seems fine as you say -- in a new project. 👍 I wanted to try my main project too, but I'm in a mini version hell there and I'd only be able to check that if I built the SDK locally, as the RTM packages are looking for versions ">=7.0.0" of packages (of which |
Understood, thanks for trying it out on a new project, @yugabe! I'm going to close this issue, but we can reopen it if we get more reports that this is still a problem. |
RTM bits resolved the issue for me. |
RTM bits resolved this particular issue for me as well, but @MackinnonBuck FYI I don't think the trimming saga is fully solved yet. I posted a comment on a similar issue that is likely related to these fixes: #43293 (comment) |
Is there an existing issue for this?
Describe the bug
Creating a Blazor WASM (or hosted) application with any kind of authentication enabled breaks on startup when published.
Related: #44322 (closed possibly by mistake, as it seems it wasn't fixed in .NET 7 RC2), also dotnet/runtime#74141
Authentication currently does not work in fully trimmed .NET 7 RC Blazor WASM apps because of this.
Expected Behavior
Published client app should not die on startup.
Steps To Reproduce
Then run the client application from a server of your choice.
Exceptions (if any)
(There are 3 errors logged to the console: the first and third exceptions are the same, the second is also the same but the stack is one call deeper.)
.NET Version
7.0.100-rc.2.22477.23
Anything else?
I found the workaround is to pin the
Microsoft.AspNetCore.Components.WebAssembly.Authentication
assembly via:<TrimmerRootAssembly Include="Microsoft.AspNetCore.Components.WebAssembly.Authentication" />
.The text was updated successfully, but these errors were encountered: