Currently completely broken

[levrik]

Describe the bug

I can't see the response body of any request.
It shows the status correctly but the body is empty.
The developer console is showing this:

To Reproduce
Steps to reproduce the behavior:

1. Just send a request
2. It shows that the request succeeded with the correct status code but no body. content-length is correctly shown.

Expected behavior

To show the response body or at least an error that something went wrong.

Desktop (please complete the following information):

• OS: macOS
• Browser Chrome 83.0.4103.116
• Version v1.9.7

This is quite annoying right now because Postwoman is my main tool and I have to set up a different tool now to be able to continue to work.

[liyasthomas]

Possible duplicate of #764 , #979
Try this: #764 (comment)
or this: #764 (comment)

[levrik]

@liyasthomas Sadly I'm not allowed to use the proxy for data security reasons. Looks I'm gonna have to wait for the fix in the extension to get published. Will switch back to Postman in the meantime to get my work done.

[liyasthomas]

You can try in another browser (ex: Firefox).

[levrik]

@liyasthomas Already got my work done with Postman now (although their GraphQL support sucks...)
Will try Postwoman in Firefox the next time if the Chrome extension wasn't updated until then.

[AndrewBastin]

@levrik really sorry about the inconvenience. But we kinda hit a snag with the Chrome Web Store, they are kinda having troubles reviewing extension updates these days due to the whole global situation. I am getting in touch with the Chrome Web Store Dev Support to get it fixed.

[liyasthomas]

Fixed in latest release of Chrome extension v0.13.
Extension should update automatically on Chrome, if not do manual update form chrome://extensions.

Do let me know if the issue persists.

[levrik]

@liyasthomas @AndrewBastin The error from this ticket is gone with 0.13 of the extension. But it's still broken. Loading bar is shown endlessly, developer console shows the following.

[liyasthomas]

Can you try again after a force refresh Ctrl + Shift + R

[levrik]

@liyasthomas Already tried this. Didn't help.