Since 2022.7.0 Insomnia cannot get schema from graphql api

[Exifs]

Expected Behavior

Insomnia should be able to get schema from introspection url and help with autocompletion.

Actual Behavior

Since the upate, my working query are now getting a 403 error while getting the schema.
But creating a GET HTTP request to the same url with /schema.json is working

Reproduction Steps

try to use a graphql query and use the auto schema fetching

Is there an existing issue for this?

• I have searched the issue tracker for this problem.

Additional Information

Version: Insomnia 2022.7.0
Build date: 15/12/2022
OS: Windows_NT x64 10.0.22000
Electron: 22.0.0
Node: 16.17.1
V8: 10.8.168.20-electron.0
Architecture: x64

Insomnia Version

2022.7.0

What operating system are you using?

Windows

Operating System Version

windows 11

Installation method

downloaded from the websit and automagically updated

Last Known Working Insomnia version

2022.6.0

[filfreire]

@Exifs do you notice the same 403 errors if you try with another server (e.g. https://rickandmortyapi.com/graphql)

Can you also share error logs you see from Dev Console of Insomnia?

[Exifs]

No, with this URL I get a 401 error.
The 403 error is probably due to authentication for my API, but the token used for that was correctly sent before.

[Exifs]

After relading Insomnia with devtools activated, i got the following error message :

The only error i got in the logs is :
\AppData\Local\insomnia\app-2022.7.0\resources\app.asar\node_modules@sentry\browser\dist\helpers.js:76 15:09:41.393 › [graphql] Failed to fetch schema Error: Request failed with status code 401

The call to the character query of the API is OK with the following logs :
15:09:31.021 › [network] Sending req=req_7ba138e07cee49578ea74738887d3d4d env=env_a32c895d747346d988325d013250a032
\AppData\Local\insomnia\app-2022.7.0\resources\app.asar\node_modules@sentry\browser\dist\helpers.js:76 15:09:31.446 › [header] Set default header Authorization: Bearer XXXXXXXXXXXXXXXXTHISISMYAUTHTOKEN
\AppData\Local\insomnia\app-2022.7.0\resources\app.asar\node_modules@sentry\browser\dist\helpers.js:76 15:09:31.540 › [network] Response failed req=req_7ba138e07cee49578ea74738887d3d4d err=Error: Failure when receiving data from the peer
\AppData\Local\insomnia\app-2022.7.0\resources\app.asar\node_modules@sentry\browser\dist\helpers.js:76 15:09:34.345 › [network] Sending req=req_7ba138e07cee49578ea74738887d3d4d env=env_a32c895d747346d988325d013250a032
\AppData\Local\insomnia\app-2022.7.0\resources\app.asar\node_modules@sentry\browser\dist\helpers.js:76 15:09:34.764 › [header] Set default header Authorization: Bearer XXXXXXXXXXXXXXXXTHISISMYAUTHTOKEN
\AppData\Local\insomnia\app-2022.7.0\resources\app.asar\node_modules@sentry\browser\dist\helpers.js:76 15:09:35.254 › [network] Response succeeded req=req_7ba138e07cee49578ea74738887d3d4d status=200
\AppData\Local\insomnia\app-2022.7.0\resources\app.asar\node_modules@sentry\browser\dist\helpers.js:76 15:09:37.183 › [network] Sending req=req_7ba138e07cee49578ea74738887d3d4d env=env_a32c895d747346d988325d013250a032
\AppData\Local\insomnia\app-2022.7.0\resources\app.asar\node_modules@sentry\browser\dist\helpers.js:76 15:09:37.600 › [header] Set default header Authorization: Bearer XXXXXXXXXXXXXXXXTHISISMYAUTHTOKEN
\AppData\Local\insomnia\app-2022.7.0\resources\app.asar\node_modules@sentry\browser\dist\helpers.js:76 15:09:37.721 › [network] Response succeeded req=req_7ba138e07cee49578ea74738887d3d4d status=200

[phyllisstein]

I see the same thing. For example, I authenticate to a GraphQL API using an OAuth 2.0 client credentials grant. Insomnia correctly acquires and submits a token when I request the endpoint itself. However, from what I can see in the render log, it looks like schema requests, in particular, may drop the token on the floor.

[2022-12-16 11:32:42.802] [error] [graphql] Failed to fetch schema {
  message: 'Request failed with status code 401',
  name: 'Error',
  stack: 'Error: Request failed with status code 401\n' +
    '    at createError (/Applications/Insomnia.app/Contents/Resources/app.asar/node_modules/axios/lib/core/createError.js:16:15)\n' +
    '    at settle (/Applications/Insomnia.app/Contents/Resources/app.asar/node_modules/axios/lib/core/settle.js:17:12)\n' +
    '    at IncomingMessage.handleStreamEnd (/Applications/Insomnia.app/Contents/Resources/app.asar/node_modules/axios/lib/adapters/http.js:269:11)\n' +
    '    at IncomingMessage.emit (node:events:525:35)\n' +
    '    at endReadableNT (node:internal/streams/readable:1358:12)\n' +
    '    at process.processTicksAndRejections (node:internal/process/task_queues:83:21)',
  config: {
    url: 'https://tower.voxmedia.com/graphql',
    method: 'post',
    data: '{"query":"\\n    query IntrospectionQuery {}\\n  "}',
    headers: {
      Accept: 'application/json, text/plain, */*',
      'Content-Type': 'application/json',
      'User-Agent': 'axios/0.21.2',
      'Content-Length': 1774
    },

[colinshum]

+1, also seeing a 401 error after updating to 22.7.0. I've tested this using GitHub's GraphQL API, and confirmed that requests using the same token are making it through. Looks like this only affects schema introspection.

In the meantime, I've downgraded to release 22.6.0 and disabled automatic updates.

Logs:

helpers.ts:98 12:11:26.114 › [graphql] Failed to fetch schema Error: Request failed with status code 401
    at createError (/private/var/folders/32/hkfp424n2lj35x19733qclv80000gn/T/AppTranslocation/372FC57A-B846-4237-922B-4068E59DF5E1/d/Insomnia.app/Contents/Resources/app.asar/node_modules/axios/lib/core/createError.js:16:15)
    at settle (/private/var/folders/32/hkfp424n2lj35x19733qclv80000gn/T/AppTranslocation/372FC57A-B846-4237-922B-4068E59DF5E1/d/Insomnia.app/Contents/Resources/app.asar/node_modules/axios/lib/core/settle.js:17:12)
    at IncomingMessage.handleStreamEnd (/private/var/folders/32/hkfp424n2lj35x19733qclv80000gn/T/AppTranslocation/372FC57A-B846-4237-922B-4068E59DF5E1/d/Insomnia.app/Contents/Resources/app.asar/node_modules/axios/lib/adapters/http.js:269:11)
    at IncomingMessage.emit (node:events:525:35)
    at endReadableNT (node:internal/streams/readable:1358:12)
    at process.processTicksAndRejections (node:internal/process/task_queues:83:21)
sentryWrapped @ helpers.ts:98

[dlic-ddlucas]

+1 on 401 error, we use OAuth2, and this used to work with schema, but after upgrade it is like it ignored the authentication plugin and values and just fails. Even if I try manually it still fails. Just upgraded to 2022.7.0 this morning.

[cdn-schaars]

I can confirm that 2022.7.0 is not able to fetch the schema! A 401 error was displayed.
After finding this thread I downgraded to 2022.6.0
With this version the schema is fetched properly.
Kind regards,
Stefan

[viliam-jobko]

I used mitmproxy to sniff the Introspection query and found out that the HTTP Request header Authorization is missing. As mitigation, I disabled the Authentication option of Insomnia and specified the Authorization header manually.

[penngrove]

Yep, same problem here, our endpoint requires authentication and the introspection query does not use the authentication provided with the query (in our case HTTP Request Signature)

[dikuropiatnyk]

The same mistake for me, if I try to fetch Schema (and I'm using Bearer auth token) - 401.
But if send a "real" request to the /graphql endpoint, everything works great

[agm1981]

Same here. We can no longer refresh the schema. We are using a fixed bearer token.
It was working fine before the latest version. Other queries still work.

[etooley]

I'm seeing the same behavior with MacOS on M1. I am using OAuth 2.0 and the schema query fails with 401 while the actual graphql query succeeds.

[DawTaylor]

The Graphql introspection query is not being run with the current request authentication. Downgrading to 22.6.0 was the only way to get it working.

[kbumsik]

I noticed the same thing. Since the latest update Insomnia starts dropping Authorization header for schema request. It works great for other requests like "Send" button.

[kofiasare]

Downloaded 22.7.0 today and I am experiencing same. Downgrading to 22.6.0

[nikolayandr]

The same issue, schemas are not fetched at all, all my colleagues have similar issue

[nikolayandr]

Wow, I enabled automatic schema fetch, and it works now

UPD.
Sorry guys, my mistake @DawTaylor @skylersidner

[DawTaylor]

Wow, I enabled auth schema fetch, and it works now

I couldn't find that option.

[skylersidner]

+1
Just downloaded 22.7.0 and lost my graphQL schema introspection.

I also can't figure out what @nikolayandr is referring to with, "enabling auth schema fetch"

[DawTaylor]

Wow, I enabled automatic schema fetch, and it works now

UPD. Sorry guys, my mistake @DawTaylor @skylersidner

That didn't seem to help in my case. The introspection query still fails as the Authorization header is never sent.

[nikolayandr]

DawTaylor

In my case no Authorization is necessary so looks like it is enough to get schema fetching working after enabling automatic fetching

[DawTaylor]

So, it looks like there was a huge refactor on the packages/insomnia/src/ui/components/editors/body/graph-ql-editor.tsx file. On 2022.6.0 it used the packages/insomnia/src/network/network.ts to send the introspection query request, this network method injects the Authorization header based on the current request config, now it's using Axios instead without any of the "enhancements" that the network method does.

I'd love to try and push a fix for it, but I really don't have the bandwidth to do that at the moment.

core@2022.6.0...core@2022.7.0

[jackkav]

We have a fix up at #5611 and it'll be in the next dot release, thanks for your patience.