Wp-graphql-woocommerce: Getting NO SCHEMA AVAILABLE after activating this plugin in GraphiQL Ide

Created on 2 Nov 2020  路  10Comments  路  Source: wp-graphql/wp-graphql-woocommerce

UPDATE: This is no longer an issue on v0.6.0, I'll keep it open because it might still be relevant for you, feel free to close in case.
I installed version from master v 0.6.1 downgrading to v 0.6.0 seemed to fix the issue for me

Describe the bug
Getting NO SCHEMA AVAILABLE after activating this plugin in GraphiQL Ide.
Everything was working fine until I activated Gql WooCommerce plugin.
Deactivating it shows the schema back

To Reproduce
Activate both plugins (wp-graphql and wp-graphql-woocommerce) and lookup for the schema or documentation in graphiql, both are empty

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
image

Desktop (please complete the following information):

  • OS: MacOs
  • Browser Chrome
  • Version:
    WP GraphQL: 0.14.0
    WooGraphQL: 0.6.1

Additional context
Add any other context about the problem here.

Just in case I tried to do run a query on products getting it from the documentation:

query MyQuery {
  products(first: 1) {
    edges {
      cursor
      node {
        id
        name
      }
    }
  }
}

And it responds 500

{
  "code": "internal_server_error",
  "message": "<p>There has been a critical error on your website.</p><p><a href=\"https://wordpress.org/support/article/debugging-in-wordpress/\">Learn more about debugging in WordPress.</a></p>",
  "data": {
    "status": 500
  },
  "additional_errors": []
}
bug

Most helpful comment

@dbertella This is due to a breaking change in WPGraphQL v0.14.0. I'll get a hotfix out as soon as I can.

All 10 comments

Most of the time when this happened to me (maybe doesn't apply to you), logging out/back on seemed to fix this issue. Maybe some important config is stored in the session/cookies and forcing it to refresh it resolves the issue.

I see thanks for the response, I "fixed" it downgrading actually so maybe latest version is not super stable?
Also I noticed that in graphiql I get 500 oftens while calling the endpoint from my app works. Mystery. The problem is I don't know how to debug the wp part unfortunately.
I will try to logout login again thanks maybe it will help, thanks

@dbertella This is due to a breaking change in WPGraphQL v0.14.0. I'll get a hotfix out as soon as I can.

@dbertella This was resolved with the release of WPGraphQL v0.15.0 and this PR in WPGraphQL.

Hi @kidunot89,

I'm facing the same problem in graphiql as well as getting 500 errors when querying to graphql endpoint.

WpGraphql version 1.1.8
Wp-graphql-woocommerce version 0.7.0

Once I deactivate Wp-graphql-woocommerce everything works fine. I was also able to get it working by reverting wpgraphql to version 0.14.0

On the console, I get the following errors:

VM182:1 POST https://my-website.com/index.php?graphql 500
(anonymous) @ VM182:1
u @ App.js:63
value @ App.js:178
_r @ react-dom.production.min.js:238
t.unstable_runWithPriority @ scheduler.production.min.js:20
_t @ react-dom.production.min.js:113
Tr @ react-dom.production.min.js:230
sr @ react-dom.production.min.js:204
Hr @ react-dom.production.min.js:263
Kr @ react-dom.production.min.js:263
(anonymous) @ react-dom.production.min.js:272
gr @ react-dom.production.min.js:208
ei @ react-dom.production.min.js:272
render @ react-dom.production.min.js:273
(anonymous) @ index.js:5
t @ bootstrap b6398cb23a41b9b84656:19
(anonymous) @ main.b7d08b5b.js:33710
t @ bootstrap b6398cb23a41b9b84656:19
(anonymous) @ bootstrap b6398cb23a41b9b84656:62
(anonymous) @ bootstrap b6398cb23a41b9b84656:62

Uncaught (in promise) Error: Invalid or incomplete introspection result. Ensure that you are passing "data" property of introspection response and no "errors" was returned alongside: { status: 500 }
    at r (invariant.mjs:6)
    at r (buildClientSchema.mjs:27)
    at App.js:181
r @ invariant.mjs:6
r @ buildClientSchema.mjs:27
(anonymous) @ App.js:181
Promise.then (async)
value @ App.js:180
_r @ react-dom.production.min.js:238
t.unstable_runWithPriority @ scheduler.production.min.js:20
_t @ react-dom.production.min.js:113
Tr @ react-dom.production.min.js:230
sr @ react-dom.production.min.js:204
Hr @ react-dom.production.min.js:263
Kr @ react-dom.production.min.js:263
(anonymous) @ react-dom.production.min.js:272
gr @ react-dom.production.min.js:208
ei @ react-dom.production.min.js:272
render @ react-dom.production.min.js:273
(anonymous) @ index.js:5
t @ bootstrap b6398cb23a41b9b84656:19
(anonymous) @ main.b7d08b5b.js:33710
t @ bootstrap b6398cb23a41b9b84656:19
(anonymous) @ bootstrap b6398cb23a41b9b84656:62
(anonymous) @ bootstrap b6398cb23a41b9b84656:62

This is still happening on WP GraphQL 1.2.6 and WooGraphQL (0.8.1) on Wordpress (5.7). Please advise @kidunot89

Hi @kidunot89,

I am also having the same problem after activate the WooGraphQL, I cannot find any schema in GraphQL IDE and when I execute the query, it results wit "Internal Server Error". No other information presented ( GRAPHQL_DEBUG is set to true).

Once I deactivate, everything's back to normal. I am currently using Wordpress 5.7, WP-GraphQL 1.3.5 and WooGraphQL 0.8.1.

Thank you

I am currently seeing this issue with WPGraphQL 1.3.5 if Custom Post Type UI 1.9.1 plugin is enabled.
Latest version of both.

I am also currently seeing this issue with WooGraphQL 0.8.1, WP GraphQL 1.3.8, and WordPress 5.7.1.

I see this error on the console:

invariant.mjs:6
Uncaught (in promise) Error: Invalid or incomplete introspection result. Ensure that you are passing "data" property of introspection response and no "errors" was returned alongside: { status: 500 }
at r (invariant.mjs:6)
at r (buildClientSchema.mjs:27)
at App.js:181

I am also not seeing any schema when i activate WooGraphQL, no problem when it's desactivated (WooGraphQL 0.8.1, WP GraphQL 1.3.8, and WordPress 5.7.2).

Should I downgrade ?

Was this page helpful?
0 / 5 - 0 ratings

Related issues

jake-101 picture jake-101  路  7Comments

ardiewen picture ardiewen  路  3Comments

huniqcast picture huniqcast  路  4Comments

zamson picture zamson  路  4Comments

mohaimenmahi picture mohaimenmahi  路  5Comments