[BUG] auth provider's check method triggering unwanted refresh with XHR call

[sqwxl]

Describe the bug

Hello Refine dev team,

I have a basic registration form that uses the useRegister hook's mutate function to submit form values.

The problem I'm facing is that when the registration is unsuccessful, the page gets refreshed and the browser is interpreting this as a sign to prompt the user to store/update the new password. This is not the expected behavior when the registration failed because of existing username, for example.

More details. I've tracked down the issue to the invalidateAuthStore function in the useRegister implementation, which is invalidating the "check" query. The refresh only happens if the check implementation includes an awaited XHR (fetch).

I understand the browser behavior is out of your control, but I wonder if the refresh mechanism is intentional? It certainly seems like a bug to me.

Steps To Reproduce

1. Create a basic refine app with a generic auth provider, including the "example" pages.
2. In the auth provider create a register method which returns { success: false, redirectTo: undefined }
3. In the auth provider's check method, add any plain fetch to a server. (The simplest is to start a simple HTTP server locally so that you don't run into CORS issues)
4. Go to the registration page and try to sign up
5. The page should refresh, and you will be prompted to save credentials even though the registration failed

Expected behavior

Ideally, the cache invalidation should happen silently and only trigger a refresh if needed. In the case described above, there's no reason to refresh/re-render anything.

Packages

Basic packages included by the npm create refine-app@latest command. v1.12.9 at time of writing.

Additional Context

No response

[BatuhanW]

Hello @sqwxl thanks for the issue. We believe you are right, invalidate should only happen if registration is successful. We are open to contributions for this one.