[PersistentState] not working when page is re-executed

[AndreiGorlov]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

[PersistentState] not working if page is re-executed e.g. when showing /not-found

Expected Behavior

No response

Steps To Reproduce

Repro: https://github.com/AndreiGorlov/PersistentStateReExecuteRepro

Reload home/counter/weather: Initial RendererInfo.Name:Static Current RendererInfo.Name:Server - All good

Hit "Not found test" (or try to open non existing page): Initial RendererInfo.Name:Server Current RendererInfo.Name:Server - InitialRenderMode not persist

Exceptions (if any)

No response

.NET Version

10.0.100

Anything else?

No response

[MihuBot]

I'm a bot. Here is a possible related and/or duplicate issue (I may be wrong):

• PersistentState attribute inconsistent behavior on page navigation #63129

[Stuart88]

It's probably the same as these

#64384
#63996
#63895

[javiercn]

@AndreiGorlov thanks for contacting us.

Does this happen during re-execution when you type a not found page URL from the browser URL?

[AndreiGorlov]

Does this happen during re-execution when you type a not found page URL from the browser URL?

When I directly browse /not-found page - everything works fine. If I try to browse something like /asd (non existent page) then state not persisting in re-executed /not-found

[javiercn]

@AndreiGorlov thanks for the additional details.

So just to be double sure, when you type something like /asd which causes re-execution is where persistent component state doesn't seem to work. The navigating directly vs enhanced navigation delta is the thing we want to make sure we understand.

[AndreiGorlov]

So just to be double sure, when you type something like /asd which causes re-execution is where persistent component state doesn't seem to work.

Exactly.

[javiercn]

@AndreiGorlov thanks for the additional details.

I suspect this issue is different from the other mentioned issues. We'll have a deeper look and provide an update in the future.

[javiercn]

The issue is

aspnetcore/src/Components/Endpoints/src/RazorComponentEndpointInvoker.cs

Lines 177 to 181 in 0d10296

	if (!isErrorHandlerOrReExecuted)
	{
	var componentStateHtmlContent = await _renderer.PrerenderPersistedStateAsync(context);
	componentStateHtmlContent.WriteTo(bufferWriter, HtmlEncoder.Default);
	}

The state should only be skipped for the error handler, not when we are re-executing the page. Errors are always rendered statically, but the not found page can be interactive.