Error from server obfuscated

[c0rdeiro]

I have a login that when it returns a 401 I need to do some specific logic. The code I show here works fine in development but in production the error that reaches the client side is obfuscated Error: An error occurred in the Server Components render. The specific message is omitted in production builds to avoid leaking sensitive details. A digest property is included on this error instance which may provide additional details about the nature of the error., making it impossible to do the client side error handling after the mutation call

I've stuck here for some days and haven't been able to find a workable solution, if anyone has been through a similar problem please share your knowledge with me

const {
    mutate,
    isSuccess,
    isPending,
  } = useMutation({
    mutationKey: ['login', address],
    mutationFn: (signature: string) => {
      return login(address, signature, currentMessageToSign!)
    },
    onError(error) {
      console.log('MUTATION ERROR', error)
      if (error.message.includes('Unauthorized')) {
        setIsModalOpen(false)
        setIsRegisterModalOpen(true)
      } else {
        toast.error('Something went wrong logging in. Please try again.')
      }
    },
  })

export async function login(address: Address, signature: string, message: string) {
 ...
   if (!response.ok) {
    if (response.status === 401) {
      return Promise.reject('Unauthorized')
    }
    if (response.status === 400) {
      return Promise.reject('Bad Request')
    }
  }

[TkDodo]

that message doesn’t come from react-query, so I guess it’s coming from nextJs.

[c0rdeiro]

yeah, I think so, but next always returns a 500 with that error message.
I searched everywhere and the only solution is to make login pass a Promise.resolve and inside of it have the flag with success and error data, but it seems quite bad. I was wondering if someone in this specific react query use case would know if it was possible to still have those errors so that I can properly use the useMutation hook callbacks

[TkDodo]

It's not react query specific, sorry