-1

Since sometime recently, possibly from upgrading to apollo 3.9.9 or from switching to mocking with graphql-codegen (not sure which if either), the console of my developer tools now fills up with thousands of instances of this error:

An error occurred! For more details, see the full error text at https://go.apollo.dev/c/err#%7B%22version%22%3A%223.

I've looked in my client/apollo files in my repo and I don't see any console.log that matches this that I can quiet.

These errors make debugging very difficult and also causes some delays in my tests when running manually and locally.

How can I silence this error? I have tried failOnConsoleError in the cypress configs and fiddled with the window object in the before of the test with no luck.

asked Jun 27, 2025 at 19:53

1 Answer 1

0

This is likely not just one error - these are potentially a lot of different errors/warnings as probably the urls slightly differ. You get the full text of the error by clicking on the link.
(Along with more explanations on how to include the full error messages instead of a link in development builds - but be aware that all the error "text" will increase your bundle size.)

Each of these is important, highlighting potential bugs in your application and you should click on the link, read the message and fix the cause, not silence them.

Once you fix the problem they warn about, you also won't see the warning anymore.

answered Jun 30, 2025 at 7:06
Sign up to request clarification or add additional context in comments.

Comments

Your Answer

Draft saved
Draft discarded

Sign up or log in

Sign up using Google
Sign up using Email and Password

Post as a guest

Required, but never shown

Post as a guest

Required, but never shown

By clicking "Post Your Answer", you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.