hoppscotch: Cannot "Get schema" on GraphQL page

Describe the bug “Get schema” on GraphQL page has been broken since today.

To Reproduce Steps to reproduce the behavior:

Go to https://postwoman.io/graphql
Click on ‘Get schema’
Scroll down to ‘Schema’
See error

Expected behavior “Get schema” should produce actual value.

Screenshots

Error: Invalid or incomplete introspection result. Ensure that you are passing "data" property of introspection response and no "errors" was returned alongside: undefined.. Check console for details.

Desktop (please complete the following information):

OS: windows 10
Browser: Chrome
Version: latest

Additional context @AndrewBastin I don’t think it’s because of the recent improvements with browser extension or proxy. This seems to be an updated syntax from the GraphQL client.

Site	Extension OFF & Poxy OFF	Extension ON & Proxy OFF	Extension OFF & Proxy ON	Extension ON & Poxy ON
Live	[x] working	[ ] failed `SyntaxError: Unexpected token in JSON at position 27692. Check console for details.`	[ ] failed `SyntaxError: Unexpected end of JSON input. Check console for details.`	[ ] failed `SyntaxError: Unexpected end of JSON input. Check console for details.`

About this issue

Original URL
State: closed
Created 4 years ago
Comments: 18 (17 by maintainers)

Most upvoted comments

Well, it is not you, the proxy is down. But I think #1027 is a more suitable issue to be open right now ? As the extension based issues are fixed.

AndrewBastin on Jul 31, 2020

@liyasthomas, that error is what I described earlier and is associated with the proxy not with the app code. Use the URL in the quote below and you can see it is the issue with the proxy. It works sometimes, but sometimes the proxy sends a failure with this message.

@NBTX the proxy is giving errors on both binary and non-binary requests.

I tried debugging this with Postwoman (turn off proxy of course): https://postwoman.io/?method=POST&url=https://postwoman.apollosoftware.xyz&path=/&contentType=application/json&rawParams={ "method": "GET", "url": "https://reqres.in/api/users", "auth": null, "headers": {}, "data": null, "credentials": true, "wantsBinary": true }

Disabling wantsBinary (or removing it) still returns a failed request.

@NBTX

AndrewBastin on Jul 20, 2020

@liyasthomas can you check if the issue persists with the code in my fork https://github.com/AndrewBastin/postwoman/tree/bug/994

AndrewBastin on Jul 19, 2020

@liyasthomas Just want to add that this issue is present for a few weeks already now.

levrik on Jul 16, 2020

Nevermind, it is the binary responses 😅

Mannn, we need a better test suite 😅

AndrewBastin on Jul 15, 2020