27 replies

Catching net::ERR_CONNECTION_REFUSED, with authClient?

Using authClient fort signIn:

const { data, error } = await authClient.signIn.email({
  email: f.data.email,
  password: f.data.password,
  rememberMe: f.data.rememberMe,
});

const { data, error } = await authClient.signIn.email({
  email: f.data.email,
  password: f.data.password,
  rememberMe: f.data.rememberMe,
});

I am hypothetically testing if my api is down.

Why doesn't

better-auth

better-auth

return better errors for this?

I wrapped in

try

try

catch

catch

and no error seems to be thrown. Only see

net::ERR_CONNECTION_REFUSED

net::ERR_CONNECTION_REFUSED

in console

How can I reliably check for extraneous errors like network?
1. data returns

null

null

2. error returns

{
    "status": 0,
    "statusText": ""
}

{
    "status": 0,
    "statusText": ""
}

Reliable way to check if

data

data

null then or when

error.status === 0

error.status === 0

? Something is wrong error?

I think authClient should at least throw an error so a catch block can take it.

Better Auth•7mo ago•