-
When using const response = await client
.query(query, variables, {
requestPolicy: "network-only",
fetchOptions: { credentials: 'include' },
})
.toPromise() It works fine most of the time, but every so often it happens that the second request using the same query with different variables that's called immediately after the first one, gets cancelled, and we're getting this logged out: We're using the following exchanges: devtoolsExchange,
requestPolicyExchange({ ttl: Infinity }),
cacheExchange(...),
authExchange(...),
fetchExchange What could be the reason for this cancellation? How can we avoid that? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
This doesn't really seem to entirely be an issue in the core library? I can spot a reference to |
Beta Was this translation helpful? Give feedback.
This doesn't really seem to entirely be an issue in the core library? I can spot a reference to
fetchWithAbort
in the logs that seems to not handle the abort error correctly. The question then obviously also becomes why the request is being aborted, but that wrapper seems to be a bit suspicious potentially?