authState is always null even though I have a token

[snaplesec]

I have been trying to use the authExchange, but I get a jwt back from server, and it never is in localStorage, and authState is never anything but null. I have gone through the docs on this, but nothing works for me. I am using Vue3 in vite, and apollo server with express-jwt, and jsonwebtoken. I checked the headers and there is never an auth header, I thought that this was working before. Ok, changed a few things, authState contains the token, but fetch fails with error:
Uncaught (in promise) TypeError: Cannot read property '__key' of undefined
at y (fetchSource.ts:25)
at createRequest (request.ts:81)
at useQuery (useQuery.ts:113)
at setup (ViewPolicyIP.vue:30)
at callWithErrorHandling (runtime-core.esm-bundler.js:154)
at setupStatefulComponent (runtime-core.esm-bundler.js:6484)
at setupComponent (runtime-core.esm-bundler.js:6445)
at mountComponent (runtime-core.esm-bundler.js:4151)
at processComponent (runtime-core.esm-bundler.js:4127)
at patch (runtime-core.esm-bundler.js:3745)

[JoviDeCroock]

That error would imply that you're not using a query-string which means you're just sending an empty graphql operation 😅 could you reproduce this?

[snaplesec]

Ok, so I stripped it down to minimum, and still gives same error.
app.use(urql, {
url: url,
fetchOptions: () => {
const token = localStorage.getItem('token')
return {
headers: { "Authorization": token ? Bearer ${token} : ''}
}
}
})

[kitten]

Your addAuthToOperation function is returning a context object, hence the error you're seeing due to a type mismatch

[snaplesec]

How do I fix that? I'm not sure how, I just sort of copied the examples in the docs.

[kitten]

I think you're not following the explanations in the docs closely enough, frankly speaking 😅 that being said, if you copy addAuthToOperation one-to-one then it will work: https://formidable.com/open-source/urql/docs/advanced/authentication/#configuring-addauthtooperation

Note that it doesn't return a context object, i.e. operation.context but a new cloned operation with new context. It must return a full operation, which is something that TypeScript would usually catch for you to be fair.

Also willAuthError cannot always return true, since there you're telling the exchange that it will never succeed. If you don't quite know yet what it does it's better to leave it out entirely, See: https://formidable.com/open-source/urql/docs/advanced/authentication/#configuring-willautherror

[snaplesec]

Thank you, I will try that, and I will leave out the willAuthError for now. I do not have a refresh setup, so probably not going to work for me at this time.