using authClient.organization.setActive() corrupts session_token in cookie

When ever I attempt to call setActive on the client:
await client.organization.setActive({ organizationId })
await client.organization.setActive({ organizationId })
I will have an un-authenticated user due to the cookie values changing from this: better-auth.session_token: isFHeVVfHfyLKGUbhthDBhyaMrvliJxC.eaSNvBFuGJGVfoUt2VFAQfeOFzIP82SDhipYEH7wbO0:"" to this: better-auth.session_token: undefined.JTi+O22FDM7EM3bIo4l8aKoK2Q1qJx0cj0hVw6mLUR0:"" Happens with 1.2.4 and with v1.2.5-beta.10 (using the mongo adapter).
0 Replies
No replies yetBe the first to reply to this messageJoin

Did you find this page helpful?