NetworkError on Axios request which was working before update to 2.x

[kiocosta]

Hello! I have this test which was working fine before upgrading to 2.x but now throws an error on a Axios request.

  it('should login the user and return isAuthenticated = true', async () => {
    const { result } = renderHook(() => useAuth(), { wrapper });

    result.current.login({
      username,
      password,
    });

    await waitFor(() => {
      expect(result.current.isAuthenticated).toEqual(true);
    });
  });

useAuth is a hook which does a bunch of stuff, but I'm particularly concerned with this part of it:

  const {
    isLoading: isLoginLoading,
    mutate: loginUser,
    error: loginError,
  } = useMutation({
    mutationKey: ['login'],
    mutationFn: authenticateUserRequest,
    onSuccess: (data) => {
      // ...
    },
    onError: (error) => {
       console.error(error=
      } else {
        showSnackbar();
      }
    },
  });

authenticateUserRequest:

/**
 * Authenticates user with given credentials
 *
 * @async
 * @function authenticateUser
 * @param {Object} data - An object containing user credentials
 * @param {string} data.username - User's username
 * @param {string} data.password - User's password
 */
export const authenticateUserRequest = async ({ username, password }) => {
  const response = await axiosInstance.post('/authentication/login', {
    username,
    password,
  });

  return loginResponseSchema.parse(response.data);
};

This request was mocked as follows:

  http.post('/authentication/login', () => HttpResponse.json(
    {
      token: validToken,
      temporaryCredentials: false,
      twoFactorEnabled: false,
      twoFactorEmail: null,
    },
  )),

Instead of returning the response I mocked in my handlers, it throws this error:

 AxiosError {
        message: 'Network Error',
        name: 'AxiosError',
        code: 'ERR_NETWORK',
        config: {
          transitional: {
            silentJSONParsing: true,
            forcedJSONParsing: true,
            clarifyTimeoutError: false
          },
          adapter: [ 'xhr', 'http' ],
          transformRequest: [ [Function: transformRequest] ],
          transformResponse: [ [Function: transformResponse] ],
          timeout: 0,
          xsrfCookieName: 'XSRF-TOKEN',
          xsrfHeaderName: 'X-XSRF-TOKEN',
          maxContentLength: -1,
          maxBodyLength: -1,
          env: { FormData: [Function], Blob: [class Blob] },
          validateStatus: [Function: validateStatus],
          headers: AxiosHeaders {
            Accept: 'application/json, text/plain, */*',
            'Content-Type': 'application/json',
            'Access-Control-Allow-Origin': '*'
          },
          baseURL: null,
          method: 'post',
          url: '/authentication/login',
          data: '{"username":"username","password":"password"}'
        },
        request: XMLHttpRequest {
          open: [Function: open],
          setRequestHeader: [Function: setRequestHeader],
          send: [Function: send],
          abort: [Function: abort],
          getResponseHeader: [Function: getResponseHeader],
          getAllResponseHeaders: [Function: getAllResponseHeaders],
          overrideMimeType: [Function: overrideMimeType],
          onreadystatechange: [Getter/Setter],
          readyState: 4,
          timeout: [Getter/Setter],
          withCredentials: [Getter/Setter],
          upload: [Getter],
          responseURL: [Getter],
          status: [Getter],
          statusText: [Getter],
          responseType: [Getter/Setter],
          response: [Getter],
          responseText: [Getter],
          responseXML: [Getter],
          UNSENT: 0,
          OPENED: 1,
          HEADERS_RECEIVED: 2,
          LOADING: 3,
          DONE: 4
        }
      }

Does anyone have any idea why this might be happening?
One thing I've noticed was that baseUrl is null, but even after I manage to add a value for it, the problem still occurred.

Any help is appreciated, thanks in advanced.

[Ladrillo]

Could it be related to this issue?

[Ladrillo]

I believe this is fixed with release 2.0.2! Thanks guys

[mattcosta7]

awesome, thanks for verifying that!