undefined is not an object (evaluating 'e.config')

[nicmosc]

Issue Summary

It looks like sometimes the useOAuthFlow hook fails and does not provide more data because the error returned is undefined. Because of the type cast the whole block fails.

Specifically this line:

cal.com/packages/platform/atoms/hooks/useOAuthFlow.ts

Line 28 in ed3579c

const originalRequest = err.config as AxiosRequestConfig;

See example from a stacktrace from our own app deployments:

Those traces point to this minified code line:

let e = u && iR.getAuthorizationHeader() ? iR.responseInterceptor.use(void 0, async e => {
                    var n;
                    let u = e.config;
                    if (t && (null == (n = e.response) ? void 0 : n.status) === 498 && !s) {
                        l(!0);
                        let e = await eSe(t);
                        if (e)
                            return c(e),
                            null == a || a(),
                            iR.instance({
                                ...u,
                                headers: {
                                    ...u.headers,
                                    Authorization: `Bearer ${e}`
                                }
                            });
                        null == i || i("Invalid Refresh Token."),
                        l(!1)
                    }
                    return Promise.reject(e.response)
                }
                ) : "";
                return () => {
                    e && iR.responseInterceptor.eject(e)
                }

Which is the code for useOAuthFlow. So clearly, here:

http.responseInterceptor.use(undefined, async (err: AxiosError) => {
            const originalRequest = err.config as AxiosRequestConfig;

The err object is undefined.

Steps to Reproduce

See above

Any other relevant information. For example, why do you consider this a bug and what did you expect to happen instead?

Actual Results

The refresh token is not properly refreshed as the code fails early, and our error reporting has very little information on the reason.

Expected Results

The refresh token should be refreshed, or at least a Invalid Refresh Token error should throw.

Technical details

• @calcom/atoms version 1.0.78 but the problematic code is still present on the latest version

Evidence

• See code snippets above