Spring GraphQL 1.4.1 - GraphiQL Schema Load error

[djett41]

I just upgraded to Spring GraphQL 1.4.1 and GraphQL Java 24.1 to upgrade to GraphiQL 5.0.0 and fix the issue with GraphiQL not loading. The GraphiQL URL now loads however It still fails to load the schema and shows the following error.

{ "errors": [ { "message": "Failed to execute 'json' on 'Response': Unexpected end of JSON input", "stack": "SyntaxError: Unexpected end of JSON input\n at https://esm.sh/@graphiql/toolkit@0.11.3/X-ZWdyYXBocWw/es2022/toolkit.bundle.mjs:7:2407\n at Generator.next (<anonymous>)\n at n (https://esm.sh/@graphiql/toolkit@0.11.3/X-ZWdyYXBocWw/es2022/toolkit.bundle.mjs:2:554)\n at https://esm.sh/@graphiql/toolkit@0.11.3/X-ZWdyYXBocWw/es2022/toolkit.bundle.mjs:2:629" } ] }

Is there anything else required for GraphiQL 5.0.0 to work with the new Spring GraphQL 1.4.1? Thanks

[bclozel]

I have tested this in several browsers, successfully, including Firefox and Safari.
Nothing else is required to run GraphiQL as far as I know. Maybe an extension or company network rule affecting the CDN being used?

[djett41]

Ive narrowed it down to the introspection query that Spring GraphQL makes under the hood. Im not super familiar with the internals, but the libraries are loading, and if I go to /graphql/schema the full schema shows, however the introspection query below fails, which worked prior ro the upgrade.

Two things to note:

1. I am creating the GraphQLSchema and GraphQlSource dynamically from configuration
2. I am currently locked into these Spring versions for required company libs. Does the upgrade to 1.4.1 also require a Spring upgrade? I'm not sure what effects overriding to newer versions will have on other libs

• Spring 6.1.16,
• Spring Security 6.3.6
• Spring Boot 3.3.8

{"query":"
    query IntrospectionQuery {
      __schema {
        
        queryType { name kind }
        mutationType { name kind }
        subscriptionType { name kind }
        types {
          ...FullType
        }
        directives {
          name
          description
          
          locations
          args {
            ...InputValue
          }
        }
      }
    }

    fragment FullType on __Type {
      kind
      name
      description
      
      
      fields(includeDeprecated: true) {
        name
        description
        args {
          ...InputValue
        }
        type {
          ...TypeRef
        }
        isDeprecated
        deprecationReason
      }
      inputFields {
        ...InputValue
      }
      interfaces {
        ...TypeRef
      }
      enumValues(includeDeprecated: true) {
        name
        description
        isDeprecated
        deprecationReason
      }
      possibleTypes {
        ...TypeRef
      }
    }

    fragment InputValue on __InputValue {
      name
      description
      type { ...TypeRef }
      defaultValue
      
      
    }

    fragment TypeRef on __Type {
      kind
      name
      ofType {
        kind
        name
        ofType {
          kind
          name
          ofType {
            kind
            name
            ofType {
              kind
              name
              ofType {
                kind
                name
                ofType {
                  kind
                  name
                  ofType {
                    kind
                    name
                    ofType {
                      kind
                      name
                      ofType {
                        kind
                        name
                      }
                    }
                  }
                }
              }
            }
          }
        }
      }
    }
  ","operationName":"IntrospectionQuery"}

[bclozel]

That introspection Query is sent by your browser by GraphiQL (you can check that in your networking tab), not spring-graphql. And on the server side, graphql-java replies with the defined schema.
At this stage, I'm not sure where the problem is:

1. maybe the graphiql explorer fails with this schema?
2. maybe the schema is somehow invalid now?
3. maybe the new spring+graphql libraries combination fails with your schema somehow

As a first step, you could roll back to 1.4.0 and copy paste this file in your src/main/resources/graphiql folder. If this fails, this points to 1) and you should probably open an issue in graphiql and share your generated schema there.

If this attempt works, this means that the problem could be 2) or 3) and I'm going to need a minimal sample application to dig into this.

Thanks!

[djett41]

I appreciate the quick reply, good to know on the introspection query. ill try the index.html override and see if that resolves the issue for now.

Im assuming the schema is good since the graphql/schema endpoint displays the raw schema as I expect it and since my IT tests all pass, but ill try to narrow down the scope of the issue