I'm working on a Blazor app configured to use Interactive Auto render mode. My goal is to improve initial page load times while avoiding the flicker that occurs when using prerendering with Blazor WebAssembly.
Everything seems to work fine initially — the page loads quickly, and interactivity is enabled. However, after some time (even without refreshing), if the user navigates to a different page or route, they sometimes encounter a "Connection lost" message.
My understanding is that Interactive Auto render mode starts in server mode and seamlessly switches to WebAssembly once it's loaded on the client. If that’s the case, I would expect the app to stop relying on the SignalR connection after WASM takes over, which should prevent the connection lost message.
To summarize:
I'm using Interactive Auto render mode.
I want to avoid the long load time of WASM with prerendering
disabled.I also want to prevent the flicker that happens during hydration whenprerender is enabled for WASM.
But after some time, the app behaves as if it’s still dependent on
the server, showing "Connection lost" when navigating.
Questions:
Is it expected for the app to show a connection lost message evenafter WASM is supposed to have taken over?
How can I confirm that the WASM handoff has completed successfully?
Is there any recommended approach to fully offload to WebAssembly
after initial prerendering, without relying on the server connection?