question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

GraphQL support broken (once again)

See original GitHub issue

Describe the bug

GraphQL requests work in general but I can’t see the response from server. Neither if the request was successful or not (means contains errors or not). Instead I’m just getting SyntaxError: Unexpected token in JSON at position 85. Check console for details.. With a different position depending on the actual JSON returned by server. I think the unexpected token seems to be a space? Sadly I can’t check the response since this is routed through the extension. Some debug mode for the extension would be great, that it logs request/response pairs or similar. I can file another issue for this if it sounds good to you.

To Reproduce Steps to reproduce the behavior:

  1. Go to GraphQL section
  2. Get the schema (works fine)
  3. Enter some query or mutation
  4. Send it and see this error described above.

Expected behavior Returned JSON to be shown

Screenshots If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

  • OS: macOS
  • Browser Chrome
  • Version 85

Additional context

It’s starting to get kinda “funny”. Every time I’m using this application, something else is broken. Most of the time around GraphQL support, sometimes also just in general. I really like the look and feel of this application and it really makes me sad that every time I want to use some fundamental functionality is broken.

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:6 (6 by maintainers)

github_iconTop GitHub Comments

1reaction
levrikcommented, Oct 2, 2020

@liyasthomas Yep. This is working fine so the problem is probably the extension.

0reactions
AndrewBastincommented, Oct 2, 2020

Yup, this is known 😅 . I just couldn’t get to the bottom of the issue yet, because it is a bit random.

Trying to work on a fix for that soon. I am busy working on the Teams system. Closing this issue as it is basically same underlying issue as #11

Read more comments on GitHub >

github_iconTop Results From Across the Web

Five Common Problems in GraphQL Apps (And How to Fix ...
Schema duplication; Server/client data mismatch; Superfluous database calls; Poor performance; Boilerplate overdose. I'm willing to bet your app ...
Read more >
Top GraphQL Errors and How to fix them
Top GraphQL Errors and How to Fix them. Error handling in GraphQL is different on both server and client side tooling.
Read more >
GraphQL playground broken: "Issues processing last ...
Got the following message: Issues processing last GraphQL query If you ... broken all day, but 25m after posting this, it's working again....
Read more >
Introducing: GraphQL Inspector. Prevent breaking changes ...
CLI Tool and Github Application. Prevent breaking changes. Find broken operations. Get Schema Coverage. Check deprecated usage and type duplicates.
Read more >
SliceMachine broken GraphQL tree - Developing with Prismic
Hello there, I got a message from Adam who has a problem with GraphQL on one of his next.js app. Could you help...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found