Mackinnon Buck

Thanks for reaching out. Could you please provide us with a repro project so we can investigate this further? Note: If this turns out to be a product bug, it...

@sbwalker Do any of these problems go away after updating to the latest .NET 8 patch release? There were some servicing fixes related to stream rendering that may have resolved...

@sbwalker, the fix I was referring to was introduced in 8.0.2, so it seems like that bug isn't the cause of what you're seeing. I briefly looked into the repro...

@sbwalker, I did a fresh clean of the repo, pulled the latest commit, confirmed that stream rendering was disabled in `Routes.razor`, and ran it, and got this:  Not sure...

Thanks for the additional details, @sbwalker. I cloned the latest version of your repro and ran it, and it still worked fine for me. Is the repro set up in...

I'm glad you were able to find the cause of the issue, @sbwalker! > the only remaining question which has not been addressed is if there is any official guidance...

Glad to hear that the upgrade fixed it! > "The renderer does not have a component with ID ##" in some scenarios where you are dynamically creating components. A new...

Updated the title so that others experiencing a similar issue can find this one more easily.

Are you using [`UsePathBase`](https://learn.microsoft.com/en-us/dotnet/api/microsoft.aspnetcore.builder.usepathbaseextensions.usepathbase?view=aspnetcore-8.0)? Can you show us your full `Program.cs`?

The reason this happens is due to the following combination: 1. SignalR requires streaming to be initiated from the client, so the server sends a message to the client with...