Skip to content

Conversation

peter-scholtens
Copy link
Contributor

Resolves error when trying to log in with with incorrect credentials: "Uncaught (in promise) TypeError: Response.clone: Body has already been consumed."

Resolves error when trying to log in with with incorrect credentials: "Uncaught (in promise) TypeError: Response.clone: Body has already been consumed."
@peter-scholtens
Copy link
Contributor Author

Unfortunately, the test logging in with incorrect credentials shows an error doesn't reveal the error. It is only visible as missing in the browser (Firefox 137.0.1 / Chromium 135.0.7049.52) itself.

@peter-scholtens
Copy link
Contributor Author

As a reminder: using responseJSON is not futureproof, see issue 2923.

@BobrImperator
Copy link
Collaborator

Well spotted! I'd like to hold off on this though because using the responseJSON property would be incorrect just as per the comment you've linked.

I've been thinking about a migration path for a while but it's not exactly as easy as I initially thought because we rely on the response internally and simply cloning it leads to a very weird API.

Let's leave this PR open as a reminder, I probably won't merge it however.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants