-
-
Notifications
You must be signed in to change notification settings - Fork 3.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Beta 6 upgrade breaking callback error definition #3106
Comments
I'm having this issue too And it's only happened when you have a custom error page |
#3141 should fix this. I tested locally, but could anyone test out this release to make sure: |
Just tested this release locally and seems to work / fix the issue just fine 👍🏻 |
Thanks! Once reviewed, it will make it into the next release. |
https://github.com/nextauthjs/next-auth/releases/tag/v4.0.0-beta.7 is now released. |
Description 🐜
Currently running a Next.js project using
next-auth
version4.0.0-beta.4
&@next-auth/prisma-adapter
version0.5.2-next.19
(Though I don't feel this dependency is relevant here I am just making it aware I am using it).I have my
[...nextauth].ts
file set up with a custompages
object that points error pages to the same page as my sign in page (So I can instead use a toast to prompt the error).I upgraded my project to v6 & so far the only bug I have noticed is that any callback failures of any kind (Callback failure, OAuth account not linked, etc) get returned as
undefined
.Since I am using Vercel I checked my functions logs and saw the following (As an example):
So somewhere, either by an issue on my end or a bug that slipped through in the new release errors are not getting passed back correctly.
Is this a bug in your own project?
No
How to reproduce ☕️
Attempt to login in via Discord and click "Cancel" & you should be re-directed back to:
You should be navigated to:
Screenshots / Logs 📽
No response
Environment 🖥
Note: I am running Windows 11, not Windows 10 (Bug with Node.js)
Contributing 🙌🏽
Yes, I am willing to help solve this bug in a PR
The text was updated successfully, but these errors were encountered: