Using Custom ILogger with ErrorBoundary produces exception = null

[musamalou]

I have a blazor webassembly project with a custom ILogger that worked fine. However, after I used the new ErrorBoundary, the public void Log method of the ILogger is called with logLever = Error and a null exception.

 <ErrorBoundary @ref ="errorBoundary">
        <ChildContent>
            @Body
        </ChildContent>
        <ErrorContent Context="ex">  
             <div class="alert alert-danger alert-dismissible fade show m-3" role="alert" style="display:flex; z-index:99999;">
                 <div style="justify-content:flex-start;flex:10;"> <strong>Error:</strong>@ex.Message  </div>
                 <div style="justify-content:flex-end;flex:1"><a href="@CurrentPath" class="reload"  style="float:right;cursor:pointer;" >Reload <span class="material-icons" title="refresh"> refresh </span> </a> </div>                        
            </div>           
        </ErrorContent>
    </ErrorBoundary>

[mkArtakMSFT]

Thank you for filing this issue. In order for us to investigate this issue, please provide a minimalistic repro project (ideally a GitHub repo) that illustrates the problem.

Hi @musamalou. We have added the "Needs: Author Feedback" label to this issue, which indicates that we have an open question for you before we can take further action. This issue will be closed automatically in 7 days if we do not hear back from you by then - please feel free to re-open it if you come back to this issue after that time.

[musamalou]

To reproduce the issue follow these steps:

1. Place a break point in the log method of the CustomLogger.cs.
2. Run the project
3. Click on Counter/Error menu
4. Clikc on the 'Click Me' button to throw an exception
5. Check the value of the exception.
6. Run the project without enclosing @Body in ErrorBoundary

The Result is: Without an error boundary, you should get the exception in log method of CustomLogger.cs that was thrown from the counter.razor

8. Now enclose the @Body in ErrorBoundary and build and run the project again

The Result is: With the body enclose in the ErrorBoundary tag, the error is thrown, but the exception in the log method of CustomLogger.cs is null
BlazorAppWithILoggerErrorBoundary.zip

[pranavkm]

Looks like a bug: #39202