Skip to content
Discussion options

You must be logged in to vote

This was not the issue. The issue was in my code and remained undetected by graphql-java. I had two instances of these types (with the same name) because I built them twice (using the same GraphQLObjectType.Builder instance. Only one of these was registered with the schema builder but another was used instead of type references in some cases. After ensuring that a single instance is built and used (or type references are), the issue disappeared.

Replies: 5 comments

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Answer selected by aleksandarsusnjar
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
1 participant