NavigationError on NavigateTo

Question

I'm trying out Blazor ServerSide and created a Component to Redirect To the Login Page when a user is not logged in.

@inject Microsoft.AspNetCore.Components.NavigationManager NavigationManager;

@code {
/// <inheritdoc />
protected override Task OnInitializedAsync()
{
    NavigationManager.NavigateTo("Login");
    return Task.CompletedTask;
}

}

But always when "NavigateTo" is called the following exception is thrown:

"Microsoft.AspNetCore.Components.NavigationException: Exception of type 'Microsoft.AspNetCore.Components.NavigationException' was thrown.
   at Microsoft.AspNetCore.Components.Server.Circuits.RemoteNavigationManager.NavigateToCore(String uri, Boolean forceLoad)
   at Microsoft.AspNetCore.Components.NavigationManager.NavigateTo(String uri, Boolean forceLoad)
   at ApplySupportTool.Blazor.Pages.RedirectToLogin.OnInitializedAsync() in C:\\Users\\padruttn\\Documents\\git\\ApplySupportTool\\src\\ApplySupportTool.Blazor\\Pages\\RedirectToLogin.razor:line 8"

Interesstingly the navigation is made despite the exception. I also tried to call it with the path "/login" but the same behaviour here.

That's got to be one of the worst (least descriptive) exceptions I've ever seen. GG Microsoft. — ataraxia
– ataraxia, Commented Aug 14, 2020 at 1:16
If someone is looking for a complete answer, take a look at this: stackoverflow.com/a/74721678/8644294 — Ash K
– Ash K, Commented Dec 7, 2022 at 19:01

Pascal R. · Accepted Answer · 2019-09-24 09:30:54Z

61

There is an open issue on github for this problem. See also the preceeding issue where a possible workaround is mentioned: putting the NavigateTo method into OnAfterRender instead of OnInitialized.

answered Sep 24, 2019 at 9:30

Pascal R.

2,3532 gold badges23 silver badges36 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

Carl Over a year ago

The issue is no longer open and still remains unfixed, but moving the call to OnAfterRender works a charm!

SmRiley · Accepted Answer · 2022-01-06 14:17:01Z

18

use OnInitializedAsync replace OnInitialized

protected override async Task OnInitializedAsync()
{
    nav.NavigateTo("/login", true);
    await base.OnInitializedAsync();
}

answered Jan 6, 2022 at 14:17

SmRiley

3424 silver badges10 bronze badges

2 Comments

twaldron Over a year ago

This is the correct solution

Toine Seiter Over a year ago

This doesn't solve the issue for me. The exception is triggered, but the NavigateTo works for the user.

ataraxia · Accepted Answer · 2020-08-14 09:23:46Z

17

I needed to put this into OnInitialized rather than OnAfterRender, so had to go with the render-mode="Server" method, though apparently this isn't recommended.

It also states in the GitHub issue that this only happens in debug, not release, so a middle ground option is to change _Host.cshtml to contain:

<environment include="Staging,Production">
    <component render-mode="ServerPrerendered" type="typeof(App)" />
</environment>
<environment include="Development">
    <component render-mode="Server" type="typeof(App)" />
</environment>

answered Aug 14, 2020 at 9:23

ataraxia

1,2001 gold badge21 silver badges34 bronze badges

2 Comments

Calciol Over a year ago

I think this is the preferred solution until it is fixed!

Jesse Over a year ago

I think that a better solution to this is to set a flag in your code behind, and then perform the navigation where you are expected to, after the rendering is complete. You can use that same flag to optimize the rendering in the scenario.

Hyque · Accepted Answer · 2022-03-22 17:49:11Z

16

Note that the following may be considered a workaround:

You may also change your method to the following including the "async" keyword to its signature, there is going to be a complaint about not using await, but in exchange you are not going to need a return value. Since it doesn't have an 'await' the effect is kinda the same as the synchronous version, but without the exception being thrown.

protected override async Task OnInitializedAsync()
{
    NavigationManager.NavigateTo("Login");
}

Here is an example where i am using a RedirectToLogin.razor component in my routing

@inject NavigationManager NavigationManager

@code{

    protected override async Task OnInitializedAsync()
    {
        var returnUrl = "~/" + NavigationManager.ToBaseRelativePath(NavigationManager.Uri);
        NavigationManager.NavigateTo($"Identity/Account/Login?returnUrl={returnUrl}", forceLoad:false);
    }

}

And in my App.razor

 <Found Context="routeData">
            <AuthorizeRouteView RouteData="@routeData" DefaultLayout="@typeof(MainLayout)">
                <NotAuthorized>
                    <RedirectToLogin />
                </NotAuthorized>
            </AuthorizeRouteView>
 </Found>

edited Mar 22, 2022 at 17:49

answered Feb 15, 2021 at 16:44

Hyque

1691 silver badge4 bronze badges

1 Comment

Victorio Berra Over a year ago

Can you explain "~/"? This does not work for me locally and I end up with localhost:1234/~ which is not found.

user2088457 · Accepted Answer · 2020-01-21 00:11:10Z

10

Old post, but - if you are running a Blazor Server app, this behavior only happens if render-mode is "ServerPrerendered". Disabling Pre-rendering by changing the mode to "Server" makes the exception not be thrown in the first place:

<app>
    <component type="typeof(App)" render-mode="Server" />
</app>

I've searched current Blazor Documentation and change notes, and haven't found any mention of this, so just in case it helps somebody else...

answered Jan 21, 2020 at 0:11

user2088457

4634 silver badges7 bronze badges

1 Comment

Robert Perry Over a year ago

It works, but its a "sledge-hammer for a nail" fix :-s

Qrt · Accepted Answer · 2020-12-04 09:29:59Z

10

I ran into the same problem and filed issue #28355. The official answer is, that it is save to ignore the exception when NaviagteTo is placed in OnInitialized. Here is the answer from javiercn:

Yes, it is completely safe to ignore it. The debugger stops because it is configured to do so, but in this case the exception is always handled. You can turn-off breaking on this exception if it's caught on the debugger settings.

Issue #13582 deals with how to prevent the debugger from stopping at this exception.

answered Dec 4, 2020 at 9:29

Qrt

6297 silver badges23 bronze badges

Comments

Shervin Ivari · Accepted Answer · 2025-01-28 06:28:35Z

10

This issue persists on .Net 9,

In my case, I only encounter it whenever my debugger is on. The current solution is to put your NavigationManager code in try-catch or simply ignore it.

.Net team planned to fix it in .Net 10. You can track the issue on Github.

edited Jan 28 at 6:28

answered Feb 18, 2024 at 17:48

Shervin Ivari

3,0915 gold badges29 silver badges43 bronze badges

1 Comment

agileDev Apr 24 at 14:59

Yes it happens only in 'Debug' mode not in 'Release' mode. Also, in my case only first time in my Login, if logout and login again then login redirection not creating problem for me.

xapymam6ypoji · Accepted Answer · 2020-08-08 14:03:59Z

3

I had this when I tried to call the navigateto from another thread. render-mode = "Server" - solved the problem

answered Aug 8, 2020 at 14:03

xapymam6ypoji

311 bronze badge

Comments

Mathias · Accepted Answer · 2025-03-15 17:42:23Z

1

For me, it was called on the wrong thread. This will help:

            await InvokeAsync(() => NavigationManager.NavigateTo("/chat"));

answered Mar 15 at 17:42

Mathias

111 bronze badge

Comments

Nicola Biada · Accepted Answer · 2024-05-21 05:36:20Z

In a Blazor 8 web app the OnInitialized/Async doesn't work when you need to redirect before the layout rendering.

The routing code (Routes.razor) is something like:

<CascadingAuthenticationState>
    <Router AppAssembly="typeof(Program).Assembly">
        <Found Context="routeData">
            <AuthorizeRouteView RouteData="routeData" DefaultLayout="typeof(Layout.MainLayout)">
                <NotAuthorized>
                    <RedirectToLogin />
                </NotAuthorized>
            </AuthorizeRouteView>
            <FocusOnNavigate RouteData="routeData" Selector="#page-container" />
        </Found>
        <NotFound>
            <PageTitle>Not found</PageTitle>
            <LayoutView Layout="@typeof(Layout.MainLayout)">
                <p role="alert">Sorry, there's nothing at this address.</p>
            </LayoutView>
        </NotFound>
    </Router>
</CascadingAuthenticationState>

In this case the redirect is triggered immediately and the OnInitializedAsync triggers the same error. The only solution is to use an OnAfterRender method, the following is my RedirectToLogin.razor:

@inject NavigationManager NavigationManager

@code {
    protected override Task OnAfterRenderAsync(bool firstRender)
    {
        NavigationManager.NavigateTo($"Account/Login?returnUrl={Uri.EscapeDataString(NavigationManager.Uri)}", forceLoad: true);
        return base.OnAfterRenderAsync(firstRender);
    }
    
    // https://github.com/dotnet/aspnetcore/issues/53996
    // We need to use the OnInitializedAsync method instead of the OnInitialized method
    // {
    //     NavigationManager.NavigateTo($"Account/Login?returnUrl={Uri.EscapeDataString(NavigationManager.Uri)}", forceLoad: true);
    // }
}

Alex Soloh · Accepted Answer · 2025-07-16 10:14:03Z

0

I moved the redirect to OnParameterSet from OnInitialized. It helped me.

    protected override void OnParametersSet()
    {
        Navigation.NavigateTo("/", forceLoad: true);
    }

answered Jul 16 at 10:14

Alex Soloh

713 bronze badges

Comments

Akram Al-Qaifi · Accepted Answer · 2025-11-21 10:27:08Z

0

In .NET 10 add this line:

<BlazorDisableThrowNavigationException>true</BlazorDisableThrowNavigationException>

in ... .csproj file like:

<PropertyGroup>
    <TargetFramework>net10.0</TargetFramework>
    ...

    <BlazorDisableThrowNavigationException>true</BlazorDisableThrowNavigationException>
  </PropertyGroup>

answered 23 hours ago

Akram Al-Qaifi

6505 silver badges18 bronze badges

Comments

George M · Accepted Answer · 2021-06-13 22:53:45Z

-1

In .NET 5.0, in the _host.cshtml file. Past the following @(await Html.RenderComponentAsync(RenderMode.Server)) in the line after the "blazor_error_ui" section.

answered Jun 13, 2021 at 22:53

George M

812 silver badges5 bronze badges

1 Comment

nh43de Over a year ago

On Net5.0 I get an error: "Error CS0411 The type arguments for method 'HtmlHelperComponentExtensions.RenderComponentAsync<TComponent>(IHtmlHelper, RenderMode)' cannot be inferred from the usage. Try specifying the type arguments explicitly."

Yassine · Accepted Answer · 2023-07-09 19:45:43Z

-1

A simple workaround that i used is to encapsulate the navigation code in a try catch block

                @try
                {
                    if (context != null)
                    {
                        if (!context.User.Identity.IsAuthenticated)
                        {
                            var returnUrl = _navigation.ToBaseRelativePath(_navigation.Uri);
                            returnUrl = "~/" + returnUrl;
                            _navigation.NavigateTo($"Identity/Account/Login?returnUrl={returnUrl}", forceLoad: true);
                        }
                    }
                }
                catch
                {
                }

answered Jul 9, 2023 at 19:45

Yassine

192 bronze badges

Collectives™ on Stack Overflow

NavigationError on NavigateTo

14 Answers 14

1 Comment

2 Comments

2 Comments

1 Comment

1 Comment

Comments

1 Comment

Comments

Comments

Comments

Comments

Comments

1 Comment

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

14 Answers 14

1 Comment

2 Comments

2 Comments

1 Comment

1 Comment

Comments

1 Comment

Comments

Comments

Comments

Comments

Comments

1 Comment

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related