aspnetcore: Blazor doesn't render ErrorBoundary's ErrorContent when there are two different exceptions inside it's ChildContent

Is there an existing issue for this?

I have searched the existing issues

Describe the bug

ErrorBoundary renders nothing when there are two different errors inside it’s ChildContent.

Expected Behavior

ErrorBoundary renders exception information.

Steps To Reproduce

App.razor

<ErrorBoundary>
    <ChildContent>
        <ComponentWithError />
    </ChildContent>
    <ErrorContent>
        <div style="background: red">@context</div>
    </ErrorContent>
</ErrorBoundary>

ComponentWithError.razor

@{
    throw new Exception("error2");
}

@code
{
    protected override async Task OnInitializedAsync()
    {
        throw new Exception("error");
    }
}

Exceptions (if any)

No response

.NET Version

6.0.101

Anything else?

I originally ran into this problem when I misspelled the parameter name in the inner component of ComponentWithError: <ComponentWithoutProp BadProp=1 /> Which throws an exception by itself.

Also with exception inside void OnInitialized() everything works fine.

About this issue

Original URL
State: open
Created 2 years ago
Reactions: 6
Comments: 16 (9 by maintainers)

Links to this issue

Is there a way to globally catch all unhandled errors in a Blazor single page application? - Stack Overflow

Most upvoted comments

I’d like this to get some more attention than just pushing it back from one year to the next. This has been around since .NET 6, and now you have three releases with this same issue.

I can confirm that this is an issue for me as well. The ErrorBoundary should be catching and rendering its ErrorContent if some async work in OnInitializedAsync throws shouldn’t it? Instead it bubbles up to the whole application, whereas I want it to do what it claims to do. Keep it within the component’s ErrorBoundary and handle it there.

stephajn on Dec 11, 2023

I tried to make a minimal reproducible example. Of course there is much more code to await in real use case.

xiety on Oct 26, 2022

Hi @TanayParikh. You removed async from my method and the problem is gone.

I reproduced it by adding async back: https://blazorrepl.telerik.com/cQPuQTml54XlfWdS53

xiety on Oct 25, 2022

And the following does not work:

    protected override async Task OnInitializedAsync()
    {
        await File.ReadAllTextAsync("NOT EXISTS");
    }

https://blazorrepl.telerik.com/mcbucUvh06LNyOkj40

xiety on Oct 26, 2022

So the async isn’t the issue per-say, it’s the missing await if you have async. The following works as expected:

https://blazorrepl.telerik.com/GQFuGAFq46B8euzE23

TanayParikh on Oct 26, 2022