-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Server request fails with undefined reasons #375
Comments
Looks like the issue was that Relay was setting the Should |
@aweary express-graphql supports both.
{"query": "{viewer{id}}", "variables": {}}
{viewer{id}} The default network layer in Relay always uses |
@fson beat me to it - Relay sends JSON, hence |
👍 |
This was referenced May 11, 2021
This was referenced Apr 7, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have a really simple Relay app at the moment which fails with the error:
The query that is supposed to be submitted to my API is, according to the
_printedQuery
property:"query RootQueryType{property{...__RelayQueryFragment0nrk9vk}} fragment __RelayQueryFragment0nrk9vk on Property{propertyName,id}"
Which I've verified returns the expected results if I run the query directly against the server using
curl
. My API is running on a different port so I'm usingRelay.injectNetworkLayer
to point Relay to the proper endpoint. I've noticed that, whenever I start my Relay application, my GraphQL API logs therequest.body
as an empty object, which says to me that its making the request but not with the right information.Here are my files, as they pertain to the Relay app:
app.js
components/Property.js
routes/AppHomeRoute.js
I'm hoping its just user error, but in any case it shouldn't be returning
undefined
as a reason.The text was updated successfully, but these errors were encountered: