-
Notifications
You must be signed in to change notification settings - Fork 2.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
Expected signal to be an instanceof AbortSignal #6765
Comments
Full dump of the error stack trace:
|
I am also getting this error, please help! |
@icco There seems to be an issue with using ApolloClient in tandem with @auth0/auth0-react. I got the error to go away by using @auth0/nextjs-auth0 instead. |
I'm only seeing this error when using apollo in nextjs's get static functions. But unclear if it's due to auth0 or apollo or nextjs. I thought it was a big with the fetch included with nextjs but removed that and didn't solve the issue. |
Yeah, I was only seeing it in getServerSideProps and played around with fetch but using @auth0/nextjs-auth0 was the only thing that made the error go away 😅. Don't really understand why though to be completely honest. |
can confirm I'm seeing this exact issue, not a huge fan of this issue because the next's specific auth0 doesn't support the hooks from the react version |
So I removed auth0 and I'm pretty sure this is coming from inside apollo. node-fetch/node-fetch#784 could be the root issue... |
In nextjs page
|
Might be that the root cause is vercel/next.js#18044. Lots of versions of node-fetch and cross-fetch in my yarn.lock |
Hey guys, I had the same issue trying to use auth0-react with next.js and apollo client. This is not an apollo client issue. As I understand it next.js will prefetch apollo queries using node-fetch (e.g. if you fetch data in From abortcontroller-polyfill package it seems you need to patch node-fetch with Patching the global.fetch in the next app seems to get rid of this error (for example in
|
that fixed the issue for me. thanks 👍 |
@mihaildu where would that snippit go? in
|
add that in pages/_document.tsx - see my example below
|
I got the same error and any advise here worked for me, I had to movedto another graphql client :( |
I found this solution and it works for me on Vercel |
* Disable prerending for now due to graphql rate limiting * Debug vercel build errors * Disable telemetry * New main icon * Add passhref per next docs * Try apollographql/apollo-client#6765 to fix build error on vercel
@icco , Is your problem solved with removal of |
So FWIW, updating from node v14 to v16 fixed this error for me. |
Thanks all, I'm going to close this issue as it seems there are workarounds and some upstream dependencies that may make this not actionable for the team here. We really appreciate all the idea-sharing! |
Intended outcome:
I expect to see no error.
Actual outcome:
I'm upgrading my blog to apollo 3.0 on Next w/ auth from Auth0. I'm getting the following error, which from reading code seems to be related to Apollo raising a networking error.
Nothing seems to be in the console, but here's a dump of it.
localhost-1596418187932.log
How to reproduce the issue:
I haven't figured out what the root cause is to reproduce. https://github.com/icco/writing/pull/237/files is my code where I'm migrating to the updated API.
Versions
The text was updated successfully, but these errors were encountered: