Calling authClient.signIn.social() causes unnecessary session refetch before redirect
I'm displaying a "Sign In" button in the Navbar based on whether useSession() returns a session and isPending === false. (My project is in Next.js v15.4.2 and better-auth v1.3.3
When I call authClient.signIn.social(), it immediately sends a request to the /session endpoint and flips isPending to true and then back to false even before the redirect to the provider happens. And then once again when we are redirected back to our own app.
The key here is that this whole process happens before the redirect to the provider even happens.
...
npx @better-auth/cli generate logs weird stuff on the console when run and fails
I just upgrade to
1.3.3 and for good measure I wanted to execute the cli comman generate and noticed that is logging some code in the terminal (added a screenshot, because it's too much text) and throws a prisma error at me.
The error makes no sense to me. It says the URL must start with "file:", but the url actually does start with file: and the error logs are even showing the line where file: is set 🤨 Has anyone else encountered this issue?
``
PrismaClientInitializationError: error: Error validating datasource db: the URL must start with the protocol file:`....Solution:
AH! Found the issue! I had to add
dotenvx run -f .env -- in front of the generate command. 🤦♂️