Console.error when API fails

[ninobc]

Describe the bug
In both useQuery and useMutation, whenever the API that has been passed to them fails, it results in a console.error which would then appear on screen. Also, when the mutation API fails, it crashes the app entirely and the error can't be caught, even if calling the mutation within a try/catch block as mentioned in the docs.

Additional context
using it in a react native app.

[tannerlinsley]

When using in React Native, you'll need to override the Logger, otherwise, it will cause redboxing all over the place.

import { setConsole } from 'react-query'

setConsole({
  log: console.log,
  warn: console.log,
  error: console.log,
})

[kopax]

This doesn't exist in react query anymore, what's the solution now ?

[TkDodo]

setConsole has been replaced with setLogger. Have you seen the v3 migration guide? https://react-query.tanstack.com/guides/migrating-to-react-query-3#setconsole-has-been-replaced-by-the-new-setlogger-function

[kopax]

Yes, sorry I posted that a minute before, all good and thanks !

[rshettyawaken]

Since, passing the custom logger is deprecated, how can I avoid yellow box for error responses in React Native?

[TkDodo]

we won't log error responses to the console anymore, so you should only see a log statement from react-query when there is really something that needs action from you as a developer.

[ninobc]

Just what I needed. Thanks a ton 🙌

[neilakoh]

I've been scratching my head for hours thinking what went wrong... adding it in the documentation would be a lot better or just add it by default