Shouldn't we keep the oauthResponse?.error logic here? If not should we just remove the loading and depend on whether it is defined in the prev?

The idea in this code was to use oauthResponse?.error being defined as a way to check that the operation is complete and set the loading state to false (but create an escape hatch. for the docs since no oauthResponse is created inside the docs).

prev.loading will be true in all cases, and letting loading stay that way was done so that even if a response is received, the button would remain in a "loading" state till the OAuth redirect occurs, to visually indicate to the user that something is still "pending". This behaviour is present only in the oauth case, since none of the other auth methods involve an intermediate redirect.

On second thought, I feel it's a nice detail to let the user know that the redirect is pending, so what I feel we can do is to simply remove the additional docs check here, and change the oauth docs demos to return a mock error with "this is a fake error message", so that the button goes back into the default state.

Yeah, that makes sense 👌