Postman 7.26.0 has encountered an error... - GraphQL

Since this version of Postman, I’m running in an error, when clicking Body -> GraphQL
(I think it could be linked to Gitlab GraphQL Schema?)

Hey @zisco67

Could you give a screenshot of the state you are seeing? Are you seeing any errors in DevTools?

It would be great if you could give us a set of steps to reproduce this issue.

I have the same problem

os:windows 7


devtool console error log
vendor-shared.js:242869 Error: Unknown type “Long”.

Unknown type “Long”.

Unknown type “Long”.

Unknown type “Long”.

Unknown type “Long”.

Unknown type “Long”.

Unknown type “Long”.

Unknown type “Long”.

Unknown type “Long”.

Unknown type “Long”.

Unknown type “Long”.

Unknown type “Long”.

Unknown type “Long”.

Unknown type “Long”.

Unknown type “Long”.

Unknown type “Long”.

Unknown type “Long”.

Unknown type “Long”.

Unknown type “Long”.

Unknown type “Long”.

Unknown type “Long”.

Unknown type “Long”.

Unknown type “Long”.

Unknown type “Long”.

Unknown type “Long”.

Unknown type “Long”.

Unknown type “Long”.

Field “FlatObjectField.isCreationRequired” can only be defined once.

Field “FlatObjectField.defaultValue” can only be defined once.

Unknown type “Long”.

Unknown type “Long”.

Unknown type “Long”.

Unknown type “Long”.

Unknown type “Long”.

Unknown type “Long”.

Unknown type “Long”.

Unknown type “Long”.

Unknown type “Long”.

Unknown type “Long”.

Unknown type “Long”.

Unknown type “Long”.

Unknown type “Long”.

Unknown type “Long”.

Unknown type “Long”.

Unknown type “Long”.

Unknown type “Long”.

Unknown type “Long”.

Unknown type “Long”.

Unknown type “Long”.

Field “ObjectSchema.description” can only be defined once.

Unknown type “Long”.

Field “ObjectSchemaCreate.description” can only be defined once.

Field “ObjectSchemaUpdate.description” can only be defined once.

Unknown type “Long”.

Unknown type “Long”.

Unknown type “Long”.

Unknown type “Long”.

Unknown type “Long”.

Unknown type “Long”.

Unknown type “Long”.

Unknown type “Long”.

Unknown type “Long”.

Unknown type “Long”.

Unknown type “Long”.

Unknown type “Long”.

Unknown type “Long”.

Unknown type “Long”.

Unknown type “Long”.

Unknown type “Long”.

Unknown type “Long”.

Unknown type “Long”.

Unknown type “Long”.

Unknown type “Long”.

Unknown type “Long”.

Unknown type “Long”.

Unknown type “Long”.

Unknown type “Long”.

Unknown type “Long”.
at assertValidSDL (vendor-shared.js:178156)
at buildASTSchema (vendor-shared.js:312661)
at buildSchema (vendor-shared.js:313088)
at RequestBodyGraphQLEditor.handleSchemaChange (vendor-shared.js:617531)
at RequestBodyGraphQLEditor.componentDidMount (vendor-shared.js:617503)
at commitLifeCycles (vendor-shared.js:356959)
at b (vendor-shared.js:356968)
at m (vendor-shared.js:356979)
at w (vendor-shared.js:356978)
at batchedUpdates (vendor-shared.js:356981)
at tc (vendor-shared.js:356864)
at vd (vendor-shared.js:356881)
at HTMLDocument.sentryWrapped (vendor-shared.js:242356)
(anonymous) @ vendor-shared.js:242869
h @ vendor-shared.js:356974
b @ vendor-shared.js:356969
m @ vendor-shared.js:356979
w @ vendor-shared.js:356978
batchedUpdates @ vendor-shared.js:356981
tc @ vendor-shared.js:356864
vd @ vendor-shared.js:356881
sentryWrapped @ vendor-shared.js:242356
3CommonLazyChunk.js:5479 Uncaught (in promise) TypeError: Cannot read property ‘addEventListener’ of null
at new DomListener (CommonLazyChunk.js:5479)
at Object.addDisposableListener [as i] (CommonLazyChunk.js:5494)
at new StandaloneKeybindingService (0.js:29845)
at 0.js:44873
at ensure (0.js:44864)
at new DynamicStandaloneServices (0.js:44873)
at withAllStandaloneServices (0.js:93264)
at Object.create (0.js:93285)
at vendor-shared.js:118713

Hey @jan.lj.huangya

Thanks for the screenshots and the error log. We are able to replicate this error.

It looks like the GraphQL query autocompletion is causing the crash, when the GraphQL schema selected in the request has errors.

We have identified the cause and are working on a fix for this.

In the meantime you can continue working with the request by “No Schema” in the request body.

We will keep this thread updated once the fix is out.

We’ve released a fix for this on our Canary channel. We’ll be releasing this in the stable channel in the next version.

This fix should be available in stable channel as well now.