Handle exceptions in Blazor Server App

Question

Handle exceptions in Blazor Server App

Ameet 1

We use Blazor Server app for our UI which calls APIs for almost all functions. When an API responds with an error code, what is the best way to show this response and not make the app break the circuit and become unresponsive.

AgaveJoe 30,126 Reputation points

2022-06-07T11:59:02.127+00:00

A try...catch with response.EnsureSuccessStatusCode(); is the standard pattern for catching a Web API response other than 200 (Ok). See the HttpClient reference documentation for sample code.

HttpClient Class

what is the best way to show this response and not make the app break the circuit and become unresponsive.

If you follow the standard HttpClient pattern then your code should not become unresponsive.

The community cannot see how your code is designed and you have not explained what you expect to happen when status other than 200 (ok) is returned. With that being said, a standard service pattern is typical. Then you get to write a custom implementation for Web API calls. The actual approach depends on your use case which is to vague at this point.
Ameet 1 Reputation point

2022-06-07T13:03:57.32+00:00

We use Service pattern to wrap all Web API calls. We also ensure that these are trapped in the try...catch block. However, when an endpoint responds with an Error status code, should we have State properties that are updated based on the response and follow the standard "BroadcastStateChange()" which we can then show in the UI somehow?

I wondered if there is another elegant way for this.
AgaveJoe 30,126 Reputation points

2022-06-07T15:44:48.33+00:00

Maybe the following reference documentation is what you are looking for?

https://learn.microsoft.com/en-us/aspnet/core/blazor/fundamentals/handle-errors?view=aspnetcore-6.0#error-boundaries

Your answer

AgaveJoe 30,126 Reputation points

2022-06-07T11:59:02.127+00:00

A try...catch with response.EnsureSuccessStatusCode(); is the standard pattern for catching a Web API response other than 200 (Ok). See the HttpClient reference documentation for sample code.

HttpClient Class

what is the best way to show this response and not make the app break the circuit and become unresponsive.

If you follow the standard HttpClient pattern then your code should not become unresponsive.

The community cannot see how your code is designed and you have not explained what you expect to happen when status other than 200 (ok) is returned. With that being said, a standard service pattern is typical. Then you get to write a custom implementation for Web API calls. The actual approach depends on your use case which is to vague at this point.
Ameet 1 Reputation point

2022-06-07T13:03:57.32+00:00

We use Service pattern to wrap all Web API calls. We also ensure that these are trapped in the try...catch block. However, when an endpoint responds with an Error status code, should we have State properties that are updated based on the response and follow the standard "BroadcastStateChange()" which we can then show in the UI somehow?

I wondered if there is another elegant way for this.
AgaveJoe 30,126 Reputation points

2022-06-07T15:44:48.33+00:00

Maybe the following reference documentation is what you are looking for?

https://learn.microsoft.com/en-us/aspnet/core/blazor/fundamentals/handle-errors?view=aspnetcore-6.0#error-boundaries

Share via

Handle exceptions in Blazor Server App

Your answer