-
Notifications
You must be signed in to change notification settings - Fork 837
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error in "Tests": Something Went Wrong - stops the user from doing anything due to code error #7848
Comments
This looks serious. We are on it. |
Hey @vdespa, I'm unable to reproduce this bug. This is what happens when I follow your steps (tried deleting both the Are you reliably able to reproduce this? If yes, it would be awesome if you could help us reproduce this! Cheers. |
I have reported this back in December. I can't reproduce this anymore in Version 7.16.0. |
I recently encountered this issue again. As you can see, the request is not part of a collection. But I did manage to catch an error in the DevTools. "xml.js:22 Error: Minified React error #31; visit http://facebook.github.io/react/docs/error-decoder.html?invariant=31&args[]=object%20with%20keys%20%7Badditionalneeds%2C%20bookingdates%2C%20depositpaid%2C%20firstname%2C%20lastname%2C%20totalprice%7D&args[]= for the full message or use the non-minified dev environment for full errors and additional helpful warnings." |
I think I got it. @vdespa Can you confirm that you have a global variable with key of type |
Yes, I do have one of type object @coditva |
@arlemi - still crashes in Version 7.19.1 |
@vdespa Yep my bad, we fixed an issue that was similar but not exactly the same. Will keep updating when we pick it up. :) |
@vdespa Hi! This is now fixed in Postman |
Great to see this fixed! Thank you. |
Describe the bug
While using the editor, it seems that the error Something Went Wrong prevents the user from doing anything.
To Reproduce
Steps to reproduce the behavior:
pm.response.to.have.jsonSchema(schema:Objec);
Expected behavior
No error
Screenshots
App information (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: