-
Notifications
You must be signed in to change notification settings - Fork 337
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Clicking "Edit HTTP Headers" produces Invariant Violation #162
Comments
I just ran |
I have the same issue and the solution you proposed did not solve it for me. :| |
Re-installing also solved the issue for me, as pointed by @zachtylr21! |
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. |
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
|
Having the same issue and was wondering if it was because I am on an M1 Mac. |
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. |
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?The text was updated successfully, but these errors were encountered: