Taras Matsyk

I am facing the same error after `v3.8.8` with any unhandled graphql error: ``` ApolloError: xxx at new ApolloError2 (chunk-7EYSJOP3.js?v=a8c04c3c:154:28) at toApolloError (@apollo_client.js?v=a8c04c3c:1497:43) at @apollo_client.js?v=a8c04c3c:1465:14 at mountMemo (chunk-QYYA6GZJ.js?v=a8c04c3c:12817:27) at Object.useMemo...

@jerelmiller not yet, just went through 3.8.9 and 3.8.10 and they seem to be working fine, but not `3.9.0`

@jerelmiller yeah, my bad I get the same error as topic starter if I use apollo v3.9.0 and above, everything before works fine. The main difference from my tests is...

unfortunately, this is all I have so far, I don't understand why one suspense throws an error to handle by upper components in case of gql failure and another returns...

@jerelmiller That was my guess from the very beginning, but I use defaults (`none` if I read sources/docs correctly)

[this link says](https://www.apollographql.com/docs/react/data/suspense/#error-handling) ``` By default, both network errors and GraphQL errors are thrown by useSuspenseQuery. These errors are caught and displayed by the closest [error boundary](https://react.dev/reference/react/Component#static-getderivedstatefromerror). ``` this is...

I am pretty sure it's the same issue, this is the error I get if I unpack `useSuspenseQuery` response ``` const {data, error, networkStatus} = useSuspenseQuery(Query, { variables: myVariables}, errorPolicy:...

@jerelmiller you are right, I was confused by the error, but those 2 look different I've filed an issue here: https://github.com/apollographql/apollo-client/issues/11800 feel free to delete the thread if it helps

@jerelmiller thanks for a follow-up, but I still don't understand how to catch the difference. I can confirm the issue is still present at 3.10.4, react 18.3, react-dom 18.3. Could...

@jerelmiller I get it, I barely can get any reproduction steps, your suggestions def help. I was referring to this `skipResult`, but it might be more misleading than helping, perhaps...