Anonymous users cannot sign in again anonymously... but you can?

When you authClient.signIn.anonymous() while already having an anonymous session, you get a bad request error. This is intentional of course.

However, a new anonymous user is still created, with a session, and the better-auth.session_token cookie is also updated.

So either, the 400 error is nonsense because everything works properly. Or, the error is correct but all the logic is still executed.

I just thought it was a bit odd...
Was this page helpful?