Kong
Response Error
Expected Behavior
loginResp.json Hi, I have this attached response. Insomnia returns error "Cannot convert undefined or null to object" for this. Do you have any comments on this?
Actual Behavior
loginResp.json Hi, I have this attached response. Insomnia returns error "Cannot convert undefined or null to object" for this. Do you have any comments on this?
Reproduction Steps
No response
Is there an existing issue for this?
- [x] I have searched the issue tracker for this problem.
Which sync method do you use?
- [ ] Git sync.
- [x] Insomnia Cloud sync.
- [ ] Local only
Additional Information
No response
Insomnia Version
11.1.0
What operating system are you using?
Windows
Operating System Version
Windows 11
Installation method
Exe
Last Known Working Insomnia version
No response
@FatihEnes58 Can you check if you're using any plugins? If so, could you please disable the plugins and try it again.
Hello @cwangsmv , I have downloaded the program recently, and I did not install any plugin. In addition, when I send this request and get this response on Postman, it successfully returns the response.
@FatihEnes58 I've tried to mock the same response as your uploaded one but could not reproduce that. Could you join the slack channel: https://chat.insomnia.rest/ and I might reach out to you for more information to solve this?
I also have this issue. How I reproduced:
- I imported a Postman collection with a JSON POST body containing a {{variable}} - this used to work
- now it doesn't work
- if I recreate the POST request from scratch with hardcoded data, it works
- if I execute the imported request containing a {{variable}} again, neither the new nor the imported request work. The imported request used to have the {{variable}} highlighted in purple, but after the second time it is orange with an exclamation mark as it cannot be found in environment variables.
ex. POST
{"key": "value"}
works.
Imported:
{"key": "{{variable}}"}
used to work, not any longer
If I try to replace it inline with the insomnia style ._variable it still fails to my knowledge.
If I create a new body again, now using the dropdown using ._variable, it does work. This request also does not break if I execute one of the previous broken requests again.
