signoutData might be undefined

[LLCampos]

Environment

- Node Version:     v18.17.0
- Nuxt Version:     3.11.2
- CLI Version:      3.11.1
- Nitro Version:    2.9.6
- Package Manager:  [email protected]
- User Config:      experimental, extends, modules, sourcemap, app, css, postcss, auth, vite, runtimeConfig
- Runtime Modules:  @sidebase/nuxt-auth@^0.7.2, @pinia/[email protected], @formkit/[email protected], @nuxt/[email protected], @nuxtjs/tailwindcss@^6.8.0, floating-vue/nuxt
- Build Modules:    -

Reproduction

This is a non-deterministic problem. Not able to reproduce it consistently.

Describe the bug

We've been non-deterministically been getting the error

TypeError: undefined is not an object (evaluating 'o.url') / TypeError: o is undefined

The source maps tell me that the error is happening here.

So it seems that somehow signoutData might be undefined at this point?

Additional context

• This leads to an error page in Netlify.
• This error is paired sometimes (but not always) with TypeError: NetworkError when attempting to fetch resource.

I'll add more context here if I find anything new.

Logs

No response

[phoenix-ru]

Hi @LLCampos . I checked and it's probably caused by redirects

Here's what next-auth v4 does:

POST:
https://github.com/nextauthjs/next-auth/blob/8fd11333c5f5d426a741674b0a02def723e4aa31/packages/next-auth/src/core/index.ts#L254-L261

And here's how we handle it in 0.8:

nuxt-auth/src/runtime/server/services/authjs/nuxtAuthHandler.ts

Lines 171 to 176 in 9295d1f

	if (nextRequest.body?.json) {
	return { url: nextResult.redirect }
	}
	// 3.3 via a redirect:
	return await sendRedirect(event, nextResult.redirect)

So, the body with url is only returned when next-auth returns a body with JSON, thus probably making the problem inconsistent for you.

Since we are working on a revamp of authjs in #818, it might be the case that this problem is solved there. Please keep an eye out on a new release to see if it helps.