NavigationException raised when using NavigationManager.NavigateTo upon form post in SSR

[blissvalley]

Is there an existing issue for this?

• [X] I have searched the existing issues

Describe the bug

NavigationException raised when using NavigationManager.NavigateTo upon form post in server-side rendering

Expected Behavior

redirect page to destination

Steps To Reproduce

@page "/admin_login"
@attribute [StreamRendering(true)]

@using Models
@inject NavigationManager Navigation

<h3>AdminLogin</h3>

<EditForm Model="loginRequest" OnValidSubmit="ProcessLogin" FormName="AdminLoginForm">
    <div class="form-group">
        <label for="password" class="form-label">Password:</label>
        <InputText id="password" class="form-control" @bind-Value="@loginRequest.Password" type="password" />
    </div>
    <div class="mb-2">
        <button type="submit" class="btn btn-primary">Login</button>
    </div>

</EditForm>

@if (errorMessage != null)
{
    <div class="alert alert-danger" role="alert">
        @errorMessage
    </div>
}

@code {

    [SupplyParameterFromForm]
    private LoginRequest loginRequest { get; set; } = new();

    private string? errorMessage { get; set; } = null;

    private void ProcessLogin()
    {

        if (loginRequest.Password == "123")
        {
            Navigation.NavigateTo("/admin"); //Exception Raised
        }
        else
        {
            errorMessage = "Invalid password";
        }
    }

}

Exceptions (if any)

No response

.NET Version

8.0.100-preview.7.23376.3

Anything else?

No response

[marinasundstrom]

This seems like an issue that I have encountered.

The NavigationManager not being for SSR.

From what I heard it should be fixed. Perhaps not released yet.

[marinasundstrom]

Duplicate? https://github.com/dotnet/aspnetcore/issues/49670

Although, I can't reproduce it with the specified SDK version.

Not with my own code, or with the code provided.

[marinasundstrom]

This one seems more likely: https://github.com/dotnet/aspnetcore/issues/50260

[mkArtakMSFT]

Thanks for contacting us. Does this exception result in an error in application or does it simply go away after you Continue debugging (F5) ?

[ghost]

Hi @blissvalley. 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.

[danroth27]

I'm unable to reproduce this exception with .NET 8 RC1.

[ghost]

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.

[blissvalley]

Thanks for contacting us. Does this exception result in an error in application or does it simply go away after you Continue debugging (F5) ?

When continue using F5, the program continue and go to destination page successfully.

[javiercn]

@blissvalley thanks for the additional details.

That exception is launched and caught internally by the framework, the behavior is by design. You can avoid pausing on it if you turn off first chance exceptions