[WebToolsE2E] After adding Blazor Identity to a Blazor Web App (non-auth, .NET 10.0 project), the User Register failed with an exception:"IdentityRedirectManager can only be used during static rendering."

[v-reinawang]

REGRESSION INFO: Not repro on VS 17.14.21

INSTALL STEP

1. Clean machine: Win11 x64 23H2 ENU
2. Install VS 18.3 Insiders 1.2 from https://aka.ms/vs/18/insiders/vs_Enterprise.exe
   • Web workload
   • Check 8.0/9.0 runtime
   • Includes SDK 10.0.100

REPRO STEPS

1. File > New > Project > Blazor Web App > .NET 10.0 > Server ~ Per page/component > create.

2. Right click the project > Add > New Scaffolded Item > Identity > Blazor Identity

   • DbContext class: Click + for Data context class and keep the context name by default
   • Database provider: Select "SQL Server/SQLite"
   • Click Add

3. After scaffolding completed

   • You may encounter BUG 2611149, which requires updating the Microsoft.Build.* package version.
   • Update "BlazorApp1ContextConnection" to "BlazorApp1Context"

4. Open Tools > NuGet Package Manager > Package Manager Console and run the following code.

Add-Migration CreateIdentitySchema -context <Contextname>
Update-Database -context <Contextname>

5. Run the project and register a new user

NOTE:

1. There have been similar bugs before: #3609 and #3657
2. This issue does not reproduce in 9.0/8.0 project

ACTUAL:
The user register failed with an exception

fail: Microsoft.AspNetCore.Diagnostics.DeveloperExceptionPageMiddleware[1]
      An unhandled exception has occurred while executing the request.
      System.InvalidOperationException: IdentityRedirectManager can only be used during static rendering.
         at BlazorApp8.Components.Account.IdentityRedirectManager.RedirectTo(String uri) in C:\Users\v-reinawang\source\repos\BlazorApp8\BlazorApp8\Components\Account\IdentityRedirectManager.cs:line 32
         at BlazorApp8.Components.Account.IdentityRedirectManager.RedirectTo(String uri, Dictionary`2 queryParameters) in C:\Users\v-reinawang\source\repos\BlazorApp8\BlazorApp8\Components\Account\IdentityRedirectManager.cs:line 40
         at BlazorApp8.Components.Account.Pages.Register.RegisterUser(EditContext editContext) in C:\Users\v-reinawang\source\repos\BlazorApp8\BlazorApp8\Components\Account\Pages\Register.razor:line 96
         at Microsoft.AspNetCore.Components.ComponentBase.CallStateHasChangedOnAsyncCompletion(Task task)
         at Microsoft.AspNetCore.Components.Forms.EditForm.HandleSubmitAsync()
         at Microsoft.AspNetCore.Components.ComponentBase.CallStateHasChangedOnAsyncCompletion(Task task)
         at Microsoft.AspNetCore.Components.RenderTree.Renderer.GetErrorHandledTask(Task taskToHandle, ComponentState owningComponentState)
         at Microsoft.AspNetCore.Components.RenderTree.Renderer.GetErrorHandledTask(Task taskToHandle, ComponentState owningComponentState)
         at Microsoft.AspNetCore.Components.Endpoints.EndpointHtmlRenderer.<WaitForNonStreamingPendingTasks>g__Execute|58_0()
         at Microsoft.AspNetCore.Components.Endpoints.RazorComponentEndpointInvoker.RenderComponentCore(HttpContext context)
         at Microsoft.AspNetCore.Components.Endpoints.RazorComponentEndpointInvoker.RenderComponentCore(HttpContext context)
         at Microsoft.AspNetCore.Components.Rendering.RendererSynchronizationContext.<>c.<<InvokeAsync>b__10_0>d.MoveNext()
      --- End of stack trace from previous location ---
         at Microsoft.AspNetCore.Builder.ServerRazorComponentsEndpointConventionBuilderExtensions.<>c__DisplayClass1_1.<<AddInteractiveServerRenderMode>b__1>d.MoveNext()
      --- End of stack trace from previous location ---
         at Microsoft.AspNetCore.Antiforgery.Internal.AntiforgeryMiddleware.InvokeAwaited(HttpContext context)
         at Microsoft.AspNetCore.Diagnostics.StatusCodePagesMiddleware.Invoke(HttpContext context)
         at Microsoft.AspNetCore.Authorization.AuthorizationMiddleware.Invoke(HttpContext context)
         at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware.Invoke(HttpContext context)
         at Microsoft.AspNetCore.Diagnostics.DeveloperExceptionPageMiddlewareImpl.Invoke(HttpContext context)

EXPECTED

[oroztocil]

@MackinnonBuck Can you please take a look?

[MackinnonBuck]

This should be fixed now with the recent scaffolder changes. I'll check on when those are planning to ship.

[v-elenafeng]

I checked that this issue has been fixed in the 10.0.0 feed and configuration files.

[one1lion]

This should be fixed now with the recent scaffolder changes. I'll check on when those are planning to ship.

BLUF: Is it possible to have a workaround in the meantime?

"Brief" description: I am upgrading a .NET 8 project to .NET 10 (Interactive Auto) and adding the Passkey support as well. The original Blazor WebApp project was created using the .NET 8 template with Individual Accounts auth type and I used the migrations from that to create the Identity DB, modifying the ApplicationUser to add a few more fields. During the upgrade, I found the line needed to get the DB context to add the AspNetUserPasskeys table (adding options.Stores.SchemaVersion = IdentitySchemaVersions.Version3; to the builder.Services.AddIdentityCore<ApplicationUser> line) so the migration worked fine. However, when I try to login now using the same account that worked in the .NET 8 version, I experience the same error as the OP.

I tried updating App.razor to match a new .NET 10 Blazor WebApp with Individual Accounts templated version, as well as made sure that Program.cs matched. I also tried merging the PageRenderMode logic to read:

private IComponentRenderMode? PageRenderMode =>
    HttpContext.AcceptsInteractiveRouting() 
        && !HttpContext.Request.Path.StartsWithSegments("/Account")
    ? InteractiveAuto 
    : null;

But I am still seeing the "System.InvalidOperationException: IdentityRedirectManager can only be used during static rendering." line.

So, in short, as I mentioned in the BLUF, is there a change we could make currently to apply the fix ourselves (even if it is just to the current version of the scaffolded code)?

As an aside, I created a new .NET 10 Blazor WebApp (Individual Accounts and Interactive Auto) and pointed it to my current Identity DB connection with the additions to the ApplicationUser and I am getting auth failures (no exceptions in the console). I'm using the same credentials that work in the .NET 8 version of the original app.