You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This corrupts the collection. Whenever the collection is loaded again, the app freezes. On macOS, the "unresponsive app" warning dialog shows.
Sometimes "\" alone will not freeze the app. Sometimes there must be a \ somewhere else in the string, or a - immediately before it. I'm not sure what other characters or patterns cause this.
One way to fix it is to manually edit insomnia.Environment.db to remove the backslashes. Then the collection will load just fine
Insomnia Version
8.6.1
What operating system are you using?
macOS
Operating System Version
macOS Sonoma 14.2.1 (23C71)
Installation method
homebrew
Last Known Working Insomnia version
No response
The text was updated successfully, but these errors were encountered:
Expected Behavior
Double-backslash at end of environment JSON key should be valid
Actual Behavior
Double-backslash at end of environment JSON key freezes entire app and corrupts collection
Reproduction Steps
-\\
, resulting in the following JSON:Note that shortly after typing the two backslashes, the app will freeze
Is there an existing issue for this?
Additional Information
Screencap: https://imgur.com/jD6c4S4
This corrupts the collection. Whenever the collection is loaded again, the app freezes. On macOS, the "unresponsive app" warning dialog shows.
Sometimes "\" alone will not freeze the app. Sometimes there must be a \ somewhere else in the string, or a - immediately before it. I'm not sure what other characters or patterns cause this.
One way to fix it is to manually edit
insomnia.Environment.db
to remove the backslashes. Then the collection will load just fineInsomnia Version
8.6.1
What operating system are you using?
macOS
Operating System Version
macOS Sonoma 14.2.1 (23C71)
Installation method
homebrew
Last Known Working Insomnia version
No response
The text was updated successfully, but these errors were encountered: