RangeError: Maximum call stack size exceeded

[ryangittings]

Using 3.2.0-canary.10, and just getting the folllowing error:

Describe the bug
RangeError: Maximum call stack size exceeded

Do not report bugs with your own project here, ask from help by raising a question instead - this helps us a lot with administration overhead.

Steps to reproduce
Run npm run dev, and load page with auth provider.

Expected behavior
No callstack error!

Screenshots or error logs
API resolved without sending a response for /api/auth/session, this may result in stalled requests.
/node_modules/next-auth/dist/server/index.js:71
resolve();
^

RangeError: Maximum call stack size exceeded
at
at ServerResponse.res.end (/node_modules/next-auth/dist/server/index.js:71:11)
at ServerResponse.res.end (/node_modules/next-auth/dist/server/index.js:72:15)
at ServerResponse.res.end (/node_modules/next-auth/dist/server/index.js:72:15)
at ServerResponse.res.end (/node_modules/next-auth/dist/server/index.js:72:15)
at ServerResponse.res.end (/node_modules/next-auth/dist/server/index.js:72:15)
at ServerResponse.res.end (/node_modules/next-auth/dist/server/index.js:72:15)
at ServerResponse.res.end (/node_modules/next-auth/dist/server/index.js:72:15)
at ServerResponse.res.end (/node_modules/next-auth/dist/server/index.js:72:15)
at ServerResponse.res.end (/node_modules/next-auth/dist/server/index.js:72:15)
at ServerResponse.res.end (/node_modules/next-auth/dist/server/index.js:72:15)
at ServerResponse.res.end (/node_modules/next-auth/dist/server/index.js:72:15)
at ServerResponse.res.end (/node_modules/next-auth/dist/server/index.js:72:15)
at ServerResponse.res.end (/node_modules/next-auth/dist/server/index.js:72:15)
at ServerResponse.res.end (/node_modules/next-auth/dist/server/index.js:72:15)
at ServerResponse.res.end (/node_modules/next-auth/dist/server/index.js:72:15)

[balazsorban44]

Thanks for reporting! I quickly managed to find the cause and fixed some other bugs along the way. canary is a bit brittle at the moment, so feedback is extremely helpful!

[github-actions]

🎉 This issue has been resolved in version 3.2.0-canary.11 🎉

The release is available on:

• GitHub release
• npm package (@canary dist-tag)

Your semantic-release bot 📦🚀

[ryangittings]

Just tried this! Getting another error, did you want me to create a new issue?

/node_modules/next-auth/dist/server/routes/session.js:48
return res.setHeader('Content-Type', 'application/json').json({}).end();
^

TypeError: Cannot read property 'end' of undefined

[balazsorban44]

Sorry for the inconvenience! Try next-auth@3.2.0-canary.12

I overlooked some stuff and was too eager to merge. It should be ok now, I tested 12, and I can manage to log in correctly.

We need to improve our tests to avoid things like this.

[ryangittings]

No problem - I'm here to help! Great stuff, thanks for sorting so quickly.

[ryangittings]

Working locally, though deploying with Next on Netlify and just getting console error. Not sure if this is environment related though... /api/auth/session is just a blank page with no source, but is JSON locally. Hm...

["/api/auth/session", SyntaxError: Unexpected end of JSON input
at /_next/static/chunks/0…]0: "/api/auth/session"1: SyntaxError: Unexpected end of JSON input
at /_next/static/chunks/0557186d9f439fb0430cdc93057e1a56c86d23a1.c7cc4ffd86991a5c6ff0.js:1:8356
at Generator.next ()
at l (/next/static/chunks/0557186d9f439fb0430cdc93057e1a56c86d23a1.c7cc4ffd86991a5c6ff0.js:1:3628)
at c (/next/static/chunks/0557186d9f439fb0430cdc93057e1a56c86d23a1.c7cc4ffd86991a5c6ff0.js:1:3831)length: 2__proto: Array(0)

Update: works on Vercel, so it must be something specific with netlify!

[ryangittings]

I'm testing Sign in with Apple, and just getting a task timeout on Vercel. Not sure why that is, though!

[POST] /api/auth/callback/apple - Task timed out after 10.01 second

[balazsorban44]

Can you check if it works on canary version 8?

[ryangittings]

Yep, works perfectly!

[balazsorban44]

Will have to look at it again, later. Might have to revert some of the refactorings.

[github-actions]

🎉 This issue has been resolved in version 3.3.0-canary.1 🎉

The release is available on:

• GitHub release
• npm package (@canary dist-tag)

Your semantic-release bot 📦🚀