Some of our users are seeing the exception “ApolloError: value.toString is not a function” from a useQuery hook on one of our GraphQL queries. We haven’t been able to reproduce the error. Do you have any idea what might cause this or how we can prevent it? We are on Apollo 3.9.10

One common feature is that so far all the affected users seem to be on Windows >= 10

Is there any stack trace attached? I’ve looked at the AC sources and I don’t believe that this originates in our codebase - the only method call this could occur is here: apollographql/apollo-client/blob/d42d9e09f6e887d2e862784eb601a8bda5802f11/src/utilities/common/makeUniqueId.ts#L8 …

[Screenshot 2024-12-06 at 9.50.24 am]

There is a second set with the same error from a different source in our app. Both go through QueryManager.js: [Screenshot 2024-12-06 at 9.53.11 am]

Unfortunately that’s only the stacktrace of ApolloError, which wraps around the original error which is thrown waaaay sooner to bring it into a predictable format. Is there any chance you can access error.cause and look at the stack trace of that?

Scratch that, in your version error.cause probably doesn’t exist yet. You’d have to look at error.networkError, error.graphQLErrors, error.protocolErrors and error.clientErrors to find the possible original error.

We are experiencing the same problem and found that it is related to some code coming from kaspersky anti-virus. The stack trace lead us to some function called copyHeaders() on Kaspersky side that proxies the native fetch() function. It happens only with requests using apollo client. Stacktrace: …

Yes, I discovered that this morning. There’s a conversation happening over in the Kaspersky forums. Thanks for your help Lenz and Nitzan. [image] Kaspersky is breaking ApolloClient requests(GraphQL) Not sure this is the right forum, please redirect to the relevant one if there is one. W…

We encountered something similar with a Safari extension before, and made changes on our side that should make this less likely to happen - if you can, please try to update to Release v3.11.8 · apollographql/apollo-client · GitHub

@NitzanSirota as you reported in the other thread that you are updating, please keep me posted if the update really resolves the issue. I’m still trying to reproduce the problem on my end.

ApolloError: value.toString is not a function

Client SDKs

jerelmiller December 10, 2024, 11:03pm 17

FYI, we have opened a new community thread where we will post updates as we have them. Thanks!

Topic		Replies	Views
`value.toString` is not a function issue General client , web	2	639	February 4, 2025
Apollo Client ignores errors in the server response Client SDKs client , web	1	1336	May 17, 2023
"setter is not a function" error in apollo client Client SDKs client	2	63	September 4, 2024
ApolloClient gets HTML when querying graphql-yoga endpoint in NextJS 13 RCS/app dir Client SDKs client , web	1	609	April 3, 2023
Problems with query using apollo client and react Client SDKs client , web	8	3659	November 29, 2023

ApolloError: value.toString is not a function

Related topics