-
Notifications
You must be signed in to change notification settings - Fork 26.9k
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
[CLIENT_FETCH_ERROR] with next-auth and v12.2.5-canary.4 #39495
Comments
Update I can confirm that this is the PR that is causing the issues #38483 (although weirdly enough, it seems to work for most envs) To confirm this I:
|
This fixes the case where we were incorrectly ignoring the next-auth API endpoint since it matched the `.next` watch ignore and also adds a test case to ensure we match this route correctly. ## Bug - [x] Related issues linked using `fixes #number` - [x] Integration tests added - [ ] Errors have helpful link attached, see `contributing.md` Fixes: #39495
Hi, thanks for the detailed info, this should be fixed in |
This closed issue has been automatically locked because it had no new activity for a month. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you. |
Verify canary release
Provide environment information
What browser are you using? (if relevant)
No response
How are you deploying your application? (if relevant)
No response
Describe the Bug
When trying to login, an error appears. Not happening in earlier canary versions. (can only repro in v12.2.5-canary.4)
ref: nextauthjs/next-auth#5008 (comment)
Expected Behavior
To be able to login
Link to reproduction
https://github.com/awareness481/next-auth-v12.2.5-canary.4
To Reproduce
(Edit: If you dont have at least one provider setup, you ll get a different error message but it is irrelevant)
The text was updated successfully, but these errors were encountered: