State Initialize called twice about blazor-state HOT 8 CLOSED

If you don't need prerendering you can change it in /Pages/_Host.cshtml

Replace ServerPrerendered with Server

from blazor-state.

The downside of replacing ServerPrerender with Server is the blank page until it's rendered -- this might only be milliseconds but enough to strike you with the thought of something's wrong .

My workaround shows the loading icon, which could be expanded to a splash page.

from blazor-state.

Hmm what version are you using?

from blazor-state.

I created a new project to test this (it has some DevExpress refrerences that are commented out) :
https://github.com/Herdubreid/TestBlazorState.git

from blazor-state.

Thanks, will take a look in a few hours at dinner.

from blazor-state.

@Herdubreid I can duplicate the issue. On your repo (server side) but not in my test app (hosted).
Looking for Root cause ;)
Thanks for reporting this. Scratching head! :)

from blazor-state.

It is because of the prerender. When loading the page it effectively loads it twice. This is by design.
see dotnet/aspnetcore#14903

Thx @mrpmorris for point this out to me.

So what problem is this causing you? Maybe we can use your problem to get that issue reconsidered by the team?

from blazor-state.

Ahh, great thanks! I thought I was missing something so this was doing my head in.

My app updates the state with Azura data on initialize, see example.

This caused the page to 'flicker', because it initialized twice (double render glitch).

My workaround is to wait for the first render on the MainLayout page.

I've noticed similar 'flickering' on a demo page from DevExpress, which I'm guessing is caused by this behavior.

I think this needs to be addressed by the team and at least documented with recommended workarounds.

from blazor-state.