on fail I'm not getting error response's data

[NishantDesai1306]

on fail I'm not getting error response's data

[pathikmehta]

I am facing the same problem.
In case of error it is just giving "error": [Error: Request failed with status code 401] in action.error but it is not providing the actual response object from which I can fetch some data, parameter which is set by the server.

I also tried to get that in the promise's catch block. But it looks like it is not executing catch block even if the request is getting 401 or similar error response back. Even in such failure cases, it is executing the then block of promise considering the request is succeeded.

So currently, I don't see any way to get the actual response in case of failures.

[NishantDesai1306]

I ended up using onError callback and then dispatching REQ_FAIL manually from there, and this callback function can access the actual axios's response so you can add whatever you like in the payload of the dispatched action.

It's not a solution but a workaround to make my project workable till I get a proper solution.

// example action
export const login = (email, password) => {
  return {
    type: LOGIN,
    payload: {
      request: {
        method: 'POST',
        url: '/login',
        data: {
          email,
          password,
        },
        options: {
          onError({ getState, dispatch, error }) {
            dispatch({
              type: LOGIN_FAIL,
              payload: error.response
            });
          },
        }
      },
    }
  }
}

[Overdozed]

General solution:
axiosMiddleware(client, { onError: ({ action, dispatch, error: { message } }) => { dispatch({ type: action.type + '_FAIL', payload: { error: message } }); } })

[matviishyn]

Check my answer on #87

[adrielFab]

u can grab it in the component by doing

try {
   await login()
} catch(e) {
 log( e.error.response )
}

the value returned gives

{
 data: {},
 status: ###,
}

im also on version 4.0.1

[acrosson]

Has anyone figured this out? The data property is null for me. I tried @Overdozed approach, but i'm only getting a generic message, not the string thats in the body response.