Insomnia: [Bug] Sub Environments Not Showing When Duplicated (But Still Work)

[eorroe]

Steps to reproduce

1. Make a workspace, with a sub environment.
2. Select the sub environment.
3. Create a request that uses one of the variables in the sub environment
4. Duplicate the workspace, notice the sub environment is still in use and the variables work.

But when you edit the environment the sub environment is missing and can still be used but not deleted

• Insomnia Version: 5.11.5
• Operating System: Windows 10

[rcrooks]

also seen on MacOS (10.13.1). In my case, I exported a workspace, then deleted it, and them imported it back into Insomnia. The sub environment in it then behaved exactly as described above.

[gschier]

Currently fixing the cause of this bug now. It's a tricky one :/

[gschier]

The problem is that sometimes an extra "Base Environment" gets created when there should only be one. You should be able to fix it manually with the following steps:

1. Export the workspace (be sure to include private environments)
2. Find all environments named "Base Environment"
3. If there are more than 1, delete the others
4. Update the parentId property of each sub Environment to be the same as the _id property of the "Base Environment"

[gschier]

Closed by #616

[gschier]

I just pushed an early beta version that prevents this from happening. It will also automatically fix the messed up environments when the app launches. If you give it a try, be sure to set the "update channel" to "stable and beta" in the settings, or else the app will automatically update to the previous stable release.

[rcrooks]

Thanks, @gschier -- will give it a try

[rcrooks]

@gschier all seems well with beta 3 -- thanks!

[gschier]

Awesome! Good to hear 👍 😄