search

skevy / graphiql-app

Light, Electron-based Wrapper around GraphiQL
MIT License
2.95k stars 336 forks source link

Clicking "Edit HTTP Headers" produces Invariant Violation #162

Open zachdtaylor opened 4 years ago

zachdtaylor commented 4 years ago

I used to be able to edit the http headers, but now when I click it I get an error in the console:

bundle.js:6 Uncaught Invariant Violation: Minified React error #37; visit http://facebook.github.io/react/docs/error-decoder.html?invariant=37 for the full message or use the non-minified dev environment for full errors and additional helpful warnings.

This error message isn't helpful at all, because according to the React docs:

"In the minified production build of React, we avoid sending down full error messages in order to reduce the number of bytes sent over the wire."

So I'm not sure how to go about solving this problem. I tried running brew cask reinstall graphiql but that didn't help. Has anyone else run into this before?

zachdtaylor commented 4 years ago

I just ran brew cask uninstall graphiql followed by brew cask install graphiql and that solved it. I'm leaving this open because I have no idea why this error occurred and would like to know if anyone has an explanation.

pazaricha commented 4 years ago

I have the same issue and the solution you proposed did not solve it for me. :|

hugomn commented 4 years ago

Re-installing also solved the issue for me, as pointed by @zachtylr21!

captaincole commented 3 years ago

I have the same issue, and reinstalling it helped but as soon as I re-inputted headers it happened again. I'm sure I have some issue with the headers I'm setting, but if I can't edit them, I can't figure it out.

3pns commented 2 years ago

For me re installing on OSX with brew cask did not solve the problem because the app cache was not cleared by uninstalling it making GraphiQL totally unusable as it becomes impossible to edit the headers in the UI.

I found out it is possible to edit the headers by

jeremyzilar commented 2 years ago

Having the same issue and was wondering if it was because I am on an M1 Mac.

rpylipow commented 1 year ago

I was able to fix this issue by opening the developer tools (View -> Toggle Developer Tools), then navigating to Application, going to the "clear storage" tab and clearing everything.