Blazor ErrorContent not catching an error

Question

Hi all;

Blazor Interactive Server - in my MainLayout.razor I have:


    
        
    
    
        
            
                @{
                    var guid = Guid.NewGuid().ToString();
                    Logger.LogError(error, $"{error.GetType().Name}: {guid}");
                }
                Unexpected Error (sorry)
                
                    The program has encountered an unexpected error (yes there are expected errors). This error has been
                    logged and we will look at it.

When it throws an exception handling an event in one of my components, it never gets to the . Why not?

And what do I need to do to log the exception? I want to avoid having to try/catch everywhere just to log the exception.

In addition this occurs silently. No error is displayed to the user. I want to put up a message that says something happened, provide them an error number (guid) and ask them to contact support. I can then use that guid to find the issue in the logs to see what happened.

The code throwing the exception is fired off by OnSelectResources:

Which is:

[Parameter]
public EventCallback?> Click { get; set; }

Which is declared as:

And calls:

private void OnSelect()
{
    Visible = false;
    _receivedClick = true;
    if (Click.HasDelegate)
        Click.InvokeAsync(Values);
}

Update: As stated above, this is InteractiveServer mode. In App.razor I have:

??? - thanks - dave

Accepted Answer

I would guess that the async code throwing the error is not running in the correct context, so the caller is not seeing the error and it is ignored. see this thread:

https://github.com/dotnet/aspnetcore/issues/27716

until the await syntax, getting errors from threads was difficult. your code is not using await to call Click.InvokeAsync(...) so the error is lost. you might try:

private async Task OnSelect()
{
    Visible = false;
    _receivedClick = true;
    if (Click.HasDelegate)
        await Click.InvokeAsync(Values);
}

Share via

Blazor ErrorContent not catching an error

0 additional answers

Your answer