Hi everyone,
I have a GraphQL request that I used to test successfully before. However, since yesterday, I’ve been getting an empty response even though the server logs show a successful response, and my teammate can receive the data normally.
Could you please advise what might be causing this issue?
Thank you.
@cryosat-specialist-3 Thank you for reporting this issue. We made a few changes to our execution layer that might have affected this. To be sure, could you please share the version of your Postman app? Additionally, can you provide any steps to reproduce this issue?
Hi @udit ,
I’m using Postman v11.69.2. I got this issue for all GraphQL requests
We have disabled the recent changes around the execution layer. The request should now work as expected.
Thanks for flagging this issue.
Thank you so much @parth-verma-1 ,
It’s working fine now.
Hi @cryosat-specialist-3 , we are re-enabling the underlying execution changes. We believe we have resolved the issue, but if you begin receiving an empty response body again, please let us know. A few things that would help us debug if you get it again:
Hi @timhallpostman ,
I receive an empty response now.
=> It looks like this
2. What authorization are you using?=> I’m using Bearer token
Please fix it soon @parth-verma-1 , @timhallpostman. Thank you.
FYI, I was still using Postman normally this morning; the issue seems to have appeared around 1 PM (GMT+7).
@cryosat-specialist-3 Sorry about that. A few more questions:
I tried using one of the demo servers from the repo that you shared and was able to make a GraphQL call successfully. I did have to import the schema manually as I was unable to get schema introspection working.
Can you share a minimal server that can help us reproduce this error?
I’m sorry to not make it clear, the example I gave is just an image from the internet. I want to share that the request and response structure look like that, I can’t share the real server to you.
I understand. Here ( GitHub - parthverma1/graphql-bearer-auth ) is a sample GraphQL API that I have created to test bearer auth and the server works for me.
Is this similar to how auth is configured for your server?
Since we are not able to reproduce the issue locally, it is hard to fix the bug without knowing the root cause. It would be helpful if you could help us understand how auth is setup in your implementation so that we can reproduce the issue and fix it.
Feel free to PR a change on the repo itself and/or share a snippet here on how to configure auth for this dummy server.
I’ve found the issue and the fix will be part of Friday’s release. I’ll update this thread once the fix has been released. Thanks for your help debugging!
Great to hear that, so you don’t need me to provide any additional information, right? @timhallpostman @parth-verma-1
Nope. Don’t need any more information.
Hi @cryosat-specialist-3 this issue should be resolved with Postman v11.70.6. Please update when you get a chance and let us know if it’s still showing the response as an empty object. Thanks!
I can receive the expected response now, thank you!
