V5 signin() throws error when using redirect: false

[herkulano]

Provider type

Email

Environment

System:
OS: macOS 14.1.1
CPU: (8) arm64 Apple M1 Pro
Memory: 872.53 MB / 16.00 GB
Shell: 5.9 - /bin/zsh
Binaries:
Node: 18.18.2 - ~/.nvm/versions/node/v18.18.2/bin/node
npm: 10.2.4 - ~/.nvm/versions/node/v18.18.2/bin/npm
bun: 1.0.14 - ~/.bun/bin/bun
Watchman: 2023.11.20.00 - /opt/homebrew/bin/watchman
Browsers:
Chrome: 119.0.6045.199
Safari: 17.1

Reproduction URL

https://github.com/nextauthjs/next-auth-example

Describe the issue

In "next-auth": "5.0.0-beta.4" the signIn() with redirect: false throws the following error on the client side:

Uncaught (in promise) TypeError: Failed to construct 'URL': Invalid base URL
    at signIn (webpack-internal:///(:3000/en/auth/app-pages-browser)/../../node_modules/next-auth/react.js:172:19)

How to reproduce

Install:

"next-auth": "5.0.0-beta.4"

Run:

const authResponse = await signIn("email", {
      email: data.email,
      redirect: false
})

Expected behavior

Should not throw error

[datagutt]

This PR seems to have tried to fix an issue with constructing the error URL:
#9056

But baseUrl seems to return the basePath instead of an base url (since we are on the client):

next-auth/packages/next-auth/src/lib/client.ts

Lines 160 to 167 in 656c0cd

	export function apiBaseUrl(__NEXTAUTH: AuthClientConfig) {
	if (typeof window === "undefined") {
	// Return absolute path when called server side
	return `${__NEXTAUTH.baseUrlServer}${__NEXTAUTH.basePathServer}`
	}
	// Return relative path when called client side
	return __NEXTAUTH.basePath
	}

[tills13]

PR ^ contains fix for this issue.

[pulgueta]

I am getting this same issue but with credentials provider instead of email. Already have latest beta update and still not working. Note that I am using signIn from "next-auth/react" instead of exporting it from my auth.config.ts file since it throws an error from webpack.

[Meierschlumpf]

When the next beta release is planed?

[henriques4nti4go]

same issue

[eliza921]

Same issue here with credentials provider...

[aliceclv]

Same issue 👍

[RoyBkker]

Having same issue :-(

[cassioseffrin]

Same issue for me too!

[kitchenbeats]

Same.

[lucasdale99]

Same issue! When will this make it to the next version?

[glenntws]

Would also like to get a new beta release ASAP for next-auth. Currently waiting for this one, since patching it out locally is quite tedious....

[pulgueta]

I managed to solve the issue. Simply export the signIn method from the NextAuth class and use it in a server action. Something like this:

[RicSala]

I managed to solve the issue. Simply export the signIn method from the NextAuth class and use it in a server action. Something like this:

That's not solving the issue but changing the environment (client --> server)...

[RicSala]

Same issue

[tills13]

I'll unsubscribe myself from this thread but can we please just thumbs-up the issue or PR instead of commenting "same"

[beaniebag]

I managed to solve the issue. Simply export the signIn method from the NextAuth class and use it in a server action. Something like this:

That's not solving the issue but changing the environment (client --> server)...

From authjs.dev's docs. It seems handling the formdata server side is the given solution:
https://authjs.dev/reference/nextjs#signin

Hopefully a fix for client side to properly handle errors will come later

[primostasis123]

i have encounter same issue.. any update on this?

[emimaricic]

same issue... did you guys manage to find a solution?

[glenntws]

beta5 includes the patch

[netrolite]

I fixed this by upgrading to 5.0.0-beta.5

[alexdsgmoura]

Same issue here with credentials provider.