[GH-ISSUE #5205] [bug]: Environment variables get overridden after updating the application #1985

New issue

Open

opened 2026-03-16 22:45:36 +03:00 by kerem · 1 comment

kerem commented

2026-03-16 22:45:36 +03:00

Owner

Originally created by @the-robot on GitHub (Jun 27, 2025).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5205

Is there an existing issue for this?

I have searched existing issues and this bug hasn't been reported yet

Platform

Desktop App

Browser

Chrome

Operating System

macOS

Bug Description

What happened?

Environment variables get mixed up after updating the application. The application should work as normal before the update, with no changes made to environment variables.

Step to reproduce

Simply click update
Restart the application and check environment.
Environment variables are getting mixed up. Specifically, in my case, I have both staging and test environments, and the test environment variables are being overridden by those of the staging environment. As a result, I had to repopulate them.

This issue has been occurring randomly for a while now, since the last updates. A similar bug was raised (https://github.com/hoppscotch/hoppscotch/issues/5104), but this one is not entirely the same.

The problem with the bug is that users could accidentally call the wrong environment after updating the application, since variables do not disappear; instead, their values get overridden.

Anyway, awesome project and thanks.

Deployment Type

Hoppscotch Cloud

Version

No response

Originally created by @the-robot on GitHub (Jun 27, 2025). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5205 ### Is there an existing issue for this? - [x] I have searched existing issues and this bug hasn't been reported yet ### Platform Desktop App ### Browser Chrome ### Operating System macOS ### Bug Description ## What happened? Environment variables get mixed up after updating the application. The application should work as normal before the update, with no changes made to environment variables. ## Step to reproduce 1. Simply click update 2. Restart the application and check environment. 3. Environment variables are getting mixed up. Specifically, in my case, I have both staging and test environments, and the test environment variables are being overridden by those of the staging environment. As a result, I had to repopulate them. This issue has been occurring randomly for a while now, since the last updates. A similar bug was raised (https://github.com/hoppscotch/hoppscotch/issues/5104), but this one is not entirely the same. The problem with the bug is that users could accidentally call the wrong environment after updating the application, since variables do not disappear; instead, their values get overridden. Anyway, awesome project and thanks. ### Deployment Type Hoppscotch Cloud ### Version _No response_

kerem added the

bug

need testing

labels

2026-03-16 22:45:36 +03:00

kerem commented

2026-03-16 22:45:47 +03:00

Author

Owner

@liyasthomas commented on GitHub (Jun 27, 2025):

We recently added initial value and current value scope to environment variables. Current values are not synchronized with the team and are updated at runtime. Initial values are synchronized with team members and can only be edited by workspace owners and members with editor permission. When the current value is empty at runtime, it falls back to the initial value. Could you please confirm if this behavior is observed at your end, and if this flow has caused any unexpected errors?

@liyasthomas commented on GitHub (Jun 27, 2025): We recently added initial value and current value scope to environment variables. Current values are not synchronized with the team and are updated at runtime. Initial values are synchronized with team members and can only be edited by workspace owners and members with editor permission. When the current value is empty at runtime, it falls back to the initial value. Could you please confirm if this behavior is observed at your end, and if this flow has caused any unexpected errors?

kerem referenced this issue

2026-03-17 01:11:40 +03:00

[PR #1985] [MERGED] fix: code generators #3592