Identify and handle any HTTP errors that occur outside of the typical promise resolution or

Question

Identify and handle any HTTP errors that occur outside of the typical promise resolution or

Hi there,

I am currently working on calling an API from the back end using promises in Angular 8 with TypeScript. I am facing an issue where I am unable to receive the error response properly. Whenever I reject the error to get the response/error, I only receive "OK" as a message (msg = "OK"). However, in the console, I can see that there is actually a 500 error along with the response data. You can take a look at the code snippet and the response details in the network tab below:

getAllItem(id: number) {
let promise = new Promise((resolve, reject) => {
  this.http.post<any>(environment.apiEndPoint,
    { "Method": "myMethod"},
    Helper.getHeader()).toPromise().then((res: any) => {
      resolve(res);
    },
      msg => { reject(msg); });
});
return promise;

}

This is the actual response captured in the network tab:

{"Success": false, "ErrorCode": "SYSTEM909", "Data": {}}

In the network tab, you will see the following information: Status Code: 500

Thank you for your help!

javascript angular typescript error-handling promise

Answer 1

Answer №1

Perhaps the issue lies with an interceptor that could be altering the error message. I suggest reviewing whether or not you have set up an interceptor.

Answer 2

Perhaps the issue lies with an interceptor that could be altering the error message. I suggest reviewing whether or not you have set up an interceptor.

Answer 3

Answer №2

Instead of using RxJS catchError, you can try handling errors differently

fetchItems(id: number) {
  return this.http.post(environment.apiEndPoint).pipe(
    onErrorResumeNext(error => { ... }) // alternative way to handle errors
  )
}

Answer 4

Instead of using RxJS catchError, you can try handling errors differently

fetchItems(id: number) {
  return this.http.post(environment.apiEndPoint).pipe(
    onErrorResumeNext(error => { ... }) // alternative way to handle errors
  )
}

Identify and handle any HTTP errors that occur outside of the typical promise resolution or

Answer №1

Answer №2

Similar questions

What is the correct way to fetch JSON data from a remote server using pure JavaScript?

Dropdown menu does not appear upon hovering over an item

Is your Typescript compilation running into a problem with jwt tokens?

When a d3 event is triggered by clicking, the value should be saved in a textbox

Error message: The 'event' variable is not defined in the Firebase function

Is it possible to access XMLHTTPRequest.responseText using a standardized method in JSON.parse?

Tips for displaying JSON data in HTML without the use of placeholder DIV elements

How can a command in a test be executed that is located within a specific "section" in Nightwatch?

Unexpected behavior detected in three.js and raycaster where conditional else statements fail to execute

Collaborative Artistry: Using HTML5, JavaScript, and Node.js for Multiplayer

Monitoring a folder using webpack

Navigating with React Router version 6 while implementing protected routes through the Context API

Loading JavaScript variable with pre-processed JavaScript information

An error occurred stating 'TypeError: jsdom.jsdom is not a function' while using the paper-node.js in the npm paper module

Create a dynamic menu dropdown with absolute positioning using React

What could be causing Angular to not show the outcome? Why is it that only the complete-handler is being triggered?

Guide to executing a JS file using Selenium

Accessing JSON file content from Firebase storage

Expected an occurrence of '...' in expected.ts(1005), but there is no overload that matches this call

Unable to host static content with express