mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-26 01:06:00 +03:00
[GH-ISSUE #5104] [bug]: Environment variables / values missing after update #1939
Labels
No labels
CodeDay
a11y
browser limited
bug
bug fix
cli
core
critical
design
desktop
discussion
docker
documentation
duplicate
enterprise
feature
feature
fosshack
future
good first issue
hacktoberfest
help wanted
i18n
invalid
major
minor
need information
need testing
not applicable to hoppscotch
not reproducible
pull-request
question
refactor
resolved
sandbox
self-host
spam
stale
testmu
wip
wont fix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/hoppscotch#1939
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @AryaSvitkona on GitHub (May 28, 2025).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5104
Originally assigned to: @nivedin on GitHub.
Is there an existing issue for this?
Current behavior
With the latest Update to 25.5 all environment variable keys are persistent, but the values are gone.
I also receive a "schema validation error" while loading the App or the Chrome App on OSX.
Steps to reproduce
Logs and Screenshots
Environment
Production
Hoppscotch Version
Cloud
Interceptor
Not Applicable - Issue not related to network requests
Browsers Affected
No response
Operating System
MacOS
Additional Information
No response
@furai commented on GitHub (May 28, 2025):
#5055 - This is actually what caused the bug for me. It didn't migrate properly the values I had in my environment. It moved them to
initialValuewithout filling in thecurrentValue. And apparently onlycurrentValueis used in requests.I had to manually fix it by copying
initialValueintocurrentValuefield in all my environments. I'm using PWA locally without any sync to any cloud.I've also got the same schema validation error, no idea where that backup is located in PWA.
@ampere-code commented on GitHub (May 28, 2025):
I'm adding to this issue that in both exports and imports, the
currentValueis not being taken into account.@furai commented on GitHub (May 28, 2025):
That's actually how the feature was envisioned in the PR. No idea why it was done this way:
@jdndm commented on GitHub (May 29, 2025):
Confirming this is broken using the webapp with synced environments via shared workspace
@jdndm commented on GitHub (May 29, 2025):
Looks like it might be fixed in #5105
@jamesgeorge007 commented on GitHub (May 29, 2025):
Hi, we're actively investigating the issue and have opened a PR that resolves a subset of the identified scenarios. We're continuing to work on a comprehensive fix to address the remaining cases, and a hotfix release will be issued once a complete end-to-end resolution is in place.
@agu3rra commented on GitHub (May 29, 2025):
Perhaps this is relevant, so I will add here.
Show code issue
I also noticed that Send > Options > Show code will display an error message if I try to get the equivalent CURL of a request. Screenshot follows.
PS: I managed to get my ENV's to load successfully after creating a new
Environment(I had not many values to fill). The existing ones did not work even after I filled the newCurrent Valuefield manually.Test scripts issue
I also noticed my previous Test scripts that were setting up ENV's dynamically are no longer working. Example snippet:
Variables issue
I tried updating the variable contents to check if it would force it to update, but it didn't. I noticed the request works as expected despite the warning message stating the value is missing.

@jamesgeorge007 commented on GitHub (May 30, 2025):
Hi, this has been addressed in the latest release. Please let us know if the issue persists.
The code generation issue mentioned above should also be resolved. For any other concerns related to scripting or similar areas, feel free to open a new issue with steps to reproduce.
@furai commented on GitHub (May 30, 2025):
So how
initialValueandcurrentValueare meant to work when you don't have any online sync enabled in webapp? Am I supposed to just usecurrentValueand disregardinitialValue?@nivedin commented on GitHub (May 30, 2025):
An
initial valueacts as the default value you assign to a variable. This value is stored on Hoppscotch's servers and is accessible to your team. It's helpful for maintaining consistency when working with shared environments.A
current value, on the other hand, is applied when making a request or executing a collection run. These values are local to your device and aren’t saved to Hoppscotch’s servers. Updating a current value won’t modify the original environment state in the server.@AryaSvitkona commented on GitHub (May 30, 2025):
Not sure if this is the right place to discuss the feature but ...
So if I leave
currentValueblank, since I'd like to use the same value (akainitialValue) as my team colleagues, the request I submit will use theinitialValueuntil I override this value with setting acurrentValue?@ampere-code commented on GitHub (May 30, 2025):
Is anyone else experiencing that
initialValueis not taken into account ifcurrentValueis not populated? If this is the expected behavior, how can I automatically populatecurrentValueusing the value frominitialValue, without having to manually fill incurrentValueevery time I open Hoppscotch on another device?@agu3rra commented on GitHub (May 30, 2025):
I am having the same issue. I'd assume the desired behavior would be that if
currentValueis absent theninitialValueis used. Otherwise I can't see any real purpose for having these 2 distinct fields.I also noticed that in my "older" environment, the calls work as expected, but the UI no longer shows the value of
currentValuewhen you mouse over a variable.@scottym5797 commented on GitHub (May 30, 2025):
I'm still facing this issue. I set up the shared environment, so it seems to work for me even when throwing the Schema error. But someone else accessing the shared ENV has issues and can't access the variables.
@rintaaaa commented on GitHub (Jun 1, 2025):
I also updated to v25.5.1, but I'm experiencing the same situation. Additionally, I can no longer import.
@AbhishekPrajapati commented on GitHub (Jun 2, 2025):
We are getting the same issue all of sudden, leaving all our saved requests changed to Untitled - I think they are lost now. When reloading the page, getting below errors:
We got some exported collection(exported from Hoppscotch only, which has saved responses too) but when importing it, they are still showing
Untitledrequests, any thoughts on this?@swotiendang commented on GitHub (Jun 3, 2025):
Most of issues in this thread happened to my team, we start using Hoppscotch from March 2025, and 3 months later lots of AI failed, waiting for the fix from team.
@nivedin commented on GitHub (Jun 3, 2025):
@AbhishekPrajapati can you please share your'e exported collection, this can help us with debugging the issue.
@AbhishekPrajapati commented on GitHub (Jun 6, 2025):
Sorry @nivedin I cannot share my collection due to my company's security policies.
@agu3rra commented on GitHub (Jun 6, 2025):
@AbhishekPrajapati if you have your collection previously saved in Hoppscotch's JSON form, not all is lost. I had a peer simply download an older version of Hoppscotch and it opened fine (all the
Untitledrequests/responses were there).@imrinzzzz commented on GitHub (Jun 11, 2025):
I have a similar issue, but I don't have a backup. Does that mean I cannot get the values back?
@agu3rra commented on GitHub (Jun 11, 2025):
I don't know, but I suggest you simply try to leave it as it is and install the older version without removing the current one. Alternatively, try to export the current messed up ENV before you do that. Perhaps I shows all requests as "Untitled", but the JSON has the actual data in there?
@imrinzzzz commented on GitHub (Jun 11, 2025):
Heyyy, so I just installed an older version and almost everything was still there. The only things that couldn't be restored were the changes made in the new version of the app.
@tanardi94 commented on GitHub (Jun 16, 2025):
Is there any progress for this bugfix?
I kinda move to postman til this bug is fixed, Love this app bro
@keliansb commented on GitHub (Jun 16, 2025):
We still have this issue after upgrading to v2025.5.2
@nivedin commented on GitHub (Jun 16, 2025):
@keliansb are you facing this issue with personal or a shared workspace environment
@keliansb commented on GitHub (Jun 16, 2025):
@nivedin with shared workspace environment
I don't know if personal workspace is impacted by this issue because we don't use it
@nivedin commented on GitHub (Jun 16, 2025):
@keliansb was there any error popup you saw with persistance error ?
@keliansb commented on GitHub (Jun 16, 2025):
@nivedin yes, indeed:
@nivedin commented on GitHub (Jun 16, 2025):
@keliansb can you try clearing cache and try again.
@keliansb commented on GitHub (Jun 16, 2025):
@nivedin just tried in a private window. No popup but environment variables are still empty.
@nivedin commented on GitHub (Jun 16, 2025):
@keliansb thank you for the information, need some more info for debugging this issue.
Can you please send me the value from the network tab of
GetTeamEnvironments@keliansb commented on GitHub (Jun 17, 2025):
@nivedin sure, here it is:
@nivedin commented on GitHub (Jun 17, 2025):
@keliansb Thank you for the info, just one more thing. Can you send the response object of this network call, like this. You can hide the values if any secrets exists.
https://github.com/user-attachments/assets/3da66005-b755-4f0c-8339-284e0bab30cd
@keliansb commented on GitHub (Jun 17, 2025):
@nivedin it looks like the values from
ProdandTestenvironments are still there, but nothing forStaging.Also please note that I can see the values for the environment
Testin Hoppscotch, but not forProd.@chanhh01 commented on GitHub (Jun 18, 2025):
are there any existing pre-request script that can help to paste whatever written in initial value to current value?
developers without editor role didnt have locally saved current value in environment in the first place, and somehow the environment variables didnt even try to get initial value when current value is empty..
@nivedin commented on GitHub (Jun 18, 2025):
@chanhh01 we have a fix for this issue in the coming patch release.
@AryaSvitkona commented on GitHub (Jun 18, 2025):
I register three pull request, a new version but the issue is still open.
May I kindly ask what the expected status should be with latest version 25.5.2, from the perspective of a Hubspot product owner?
As creator of the Issue I also still can't access to my environment variable values although using latest version.
@nivedin I just checked the mentioned (a few comments above) response object for our team and there I can still see the values we should see in the app.
@nivedin commented on GitHub (Jun 19, 2025):
@AryaSvitkona sorry for the delayed response, yes you can upgrade to the latest version 25.5.3 without the lose of environment value.
We have fixed all the existing bug's like response getting lost and team environment values missing. Most of the issue was with version migration.
Also we have made a small change in the environment execution flow where the initial value is picked up in request execution time if the current value is empty.
We did an internal testing and everything is working fine from our end. Please try it from your end an let me know.
@AryaSvitkona commented on GitHub (Jun 19, 2025):
Thank you for your effort!

I can confirm, that after update to 25.5.3, the environment variables are back and requests are working like before.
Also the values from initial_value are copied to current_value.
@chanhh01 commented on GitHub (Jun 20, 2025):
what about initial value as default when current value is empty?
I had ady reloaded hoppscotch after the new version found prompt.
and i also found out that project environment variable (idk if they count as global environment variable), initial variable is still not copied to current value (tried this on both editor and viewer role) as per mentioned by AryaSvitkona for me
@liyasthomas commented on GitHub (Jun 20, 2025):
The initial value won’t be automatically copied to the current value. Instead, when the current value is empty, it will fall back to its initial value. The tooltip displays the current value. If it’s empty, it shows an empty placeholder but falls back to the initial value. Once the current value is populated, the tooltip displays the actual or modified value. We’ll strive to display both the initial and current values in the tooltip.
This ticket can be closed as a fix, as it’s already available in the recent release.