Unhandled exception: Auth requires a cascading parameter of type Task<AuthenticationState>

[xunmeng2002]

[EDIT by guardrex to add the error text to the comment]

Microsoft.AspNetCore.Components.Server.Circuits.RemoteRenderer: Warning: Unhandled exception rendering component: Authorization requires a cascading parameter of type Task. Consider using CascadingAuthenticationState to supply this.

Description

I wrote the test project in accordance with the documentation, and I always encountered exceptions. I created a BlazorApp Server type project with.NET 8.0.

I have already add the CascadingAuthenticationState Routes.
Routes.razor
<CascadingAuthenticationState> <Router AppAssembly="@typeof(Program).Assembly"> <Found Context="routeData"> <AuthorizeRouteView RouteData="@routeData" DefaultLayout="@typeof(Layout.MainLayout)" /> <FocusOnNavigate RouteData="@routeData" Selector="h1" /> </Found> </Router> </CascadingAuthenticationState>
BlazorApp12.zip

Page URL

https://learn.microsoft.com/zh-cn/aspnet/core/blazor/security/server/?view=aspnetcore-8.0&tabs=visual-studio

Content source URL

https://github.com/dotnet/AspNetCore.Docs/blob/main/aspnetcore/blazor/security/server/index.md

Document ID

8da62490-e36f-8f38-8f06-d5d6bceaafde

Article author

guardrex

[guardrex]

Hello @xunmeng2002 ... I'll take a look as soon as I can, but Friday is the soonest that I can look. I'm swamped with work. If you can't wait, you can contact devs on a public support forum, such as Stack Overflow.

[xunmeng2002]

Thanks for your reply. I'll be waiting for your message. Thanks for your reply. I'll be waiting for your message 紫云 ***@***.*** &nbsp;

…

------------------&nbsp;原始邮件&nbsp;------------------ 发件人: "dotnet/AspNetCore.Docs" ***@***.***&gt;; 发送时间:&nbsp;2023年11月16日(星期四) 晚上6:42 ***@***.***&gt;; ***@***.******@***.***&gt;; 主题:&nbsp;Re: [dotnet/AspNetCore.Docs] Microsoft.AspNetCore.Components.Server.Circuits.RemoteRenderer: Warning: Unhandled exception rendering component: Authorization requires a cascading parameter of type Task<AuthenticationState&gt;. Consider using CascadingAuthenticationState to supply this. (Issue #31056) Hello @xunmeng2002 ... I'll take a look as soon as I can, but Friday is the soonest that I can look. I'm swamped with work. If you can't wait, you can contact devs on a public support forum, such as Stack Overflow. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: ***@***.***&gt;

[guardrex]

Ok ... I made it. Except for getting one PR over the finish line and merged today, this is the last task of the week ... and I'm exhausted 😩.

I'll take a look at your app now and see if I can figure out the problem. If I can't figure it out, then I'll advise you to open an issue for the product unit. Stand-by ................................

[guardrex]

@xunmeng2002 ... Add ...

builder.Services.AddCascadingAuthenticationState();

... to the Program file.

Next, remove the CascadingAuthenticationState component from your Routes component ...

- <CascadingAuthenticationState>
      <Router AppAssembly="@typeof(Program).Assembly">
          <Found Context="routeData">
              <AuthorizeRouteView RouteData="@routeData" DefaultLayout="@typeof(Layout.MainLayout)" />
              <FocusOnNavigate RouteData="@routeData" Selector="h1" />
          </Found>
      </Router>
- </CascadingAuthenticationState>

We're missing the coverage on this updated approach for 8.0 BWA apps. It slipped through the cracks. Sorry about that.

I'll put in a PR to fix it. Leave this issue open. This issue will close automatically when the PR merges.

Thanks for letting me know about this.