NavigationManager.NavigateTo has no effect if called after a aynchronous method in OnIntializedAsync, in SSR mode

[SebastianToet]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

Since .NET 10 Preview 4, where NavigationManager.NavigateTo no longer throws a NavigationException, NavigateTo no longer has any effect in SSR mode, if called after an aynchronous method call in OnInitializedAsync.

Expected Behavior

NavigationManager.NavigateTo navigates to the specified route.

Steps To Reproduce

Doesn't work:

@inject NavigationManager NavigationManager
@code {
    protected override async Task OnInitializedAsync()  
    {
           await Task.Delay(1000);
           NavigationManager.NavigateTo("any-route"); //Does nothing
    }  
}

Works correctly:

@inject NavigationManager NavigationManager
@code {
    protected override async Task OnInitializedAsync()  
    {
           NavigationManager.NavigateTo("any-route"); //Works correctly
           await Tasl.Delay(1000);
    }  

Exceptions (if any)

No response

.NET Version

10.0.100-preview.5.25277.114

Anything else?

No response

[javiercn]

@SebastianToet thanks for contacting us.

I believe this was potentially addressed in preview6. @ilonatommy can you confirm?

[ilonatommy]

I tested p5, from default blazor SSR template and it does work - it navigates to "any-route" and because it's not found, re-execution gets activated and the not found page is rendered. New and old way of working behave same (in p5: Microsoft.AspNetCore.Components.Endpoints.NavigationManager.EnableThrowNavigationException with true and false).
I think I will need the full repro, could you please post it?

[ilonatommy]

My bad: in p5 template there's no re-execution, so for the not-found page rendering behavior you would have to add in Program.cs:

app.UseStatusCodePagesWithReExecute("/not-found", createScopeForErrors: true);

However, it does not have any impact on navigation.

[dotnet-policy-service]

Thank you for filing this issue. In order for us to investigate this issue, please provide a minimal repro project that illustrates the problem without unnecessary code. Please share with us in a public GitHub repo because we cannot open ZIP attachments, and don't include any confidential content.

[tharlab]

hi thanks this fix my problem, InvalidOperationException: 'RemoteNavigationManager' already initialized.
now i can using NavigationManager.NotFound(); on my component
also global handler app.UseStatusCodePagesWithReExecute() enabled on Program.cs

My bad: in p5 template there's no re-execution, so for the not-found page rendering behavior you would have to add in Program.cs:

app.UseStatusCodePagesWithReExecute("/not-found", createScopeForErrors: true);

However, it does not have any impact on navigation.

[dotnet-policy-service]

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment. If it is closed, feel free to comment when you are able to provide the additional information and we will re-investigate.

See our Issue Management Policies for more information.