[GH-ISSUE #5118] [bug]: After Update to Version 25.5.1 Those saved APIs and responses appear to GET Untitled #1946

Closed
opened 2026-03-16 22:31:43 +03:00 by kerem · 26 comments
Owner

Originally created by @kwanjai-ob on GitHub (Jun 2, 2025).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5118

Originally assigned to: @nivedin on GitHub.

Is there an existing issue for this?

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

Current behavior

My collection has multiple apis which I have saved those in name, request body and response as well, But When I updated to version 25.5.1 Those saved response has appear to GET Untitled and inside of my api endpoint is appears to https://echo.hoppscotch.io as default value of hoppscotch.

Image

But APIs that does not have save response as example display as normal

Steps to reproduce

  1. Save respose as example of some api
  2. Update to lastest version 25.5.1
  3. Reopen the api that has saved as example

Logs and Screenshots


Environment

Production

Hoppscotch Version

Cloud

Interceptor

Native - Desktop App

Browsers Affected

No response

Operating System

None

Additional Information

No response

Originally created by @kwanjai-ob on GitHub (Jun 2, 2025). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5118 Originally assigned to: @nivedin on GitHub. ### Is there an existing issue for this? - [x] I have searched existing issues and this bug hasn't been reported yet ### Current behavior My collection has multiple apis which I have saved those in name, request body and response as well, But When I updated to version `25.5.1` Those saved response has appear to GET Untitled and inside of my api endpoint is appears to https://echo.hoppscotch.io as default value of hoppscotch. ![Image](https://github.com/user-attachments/assets/3dcb755d-a84b-4daf-bd95-71966d5bfa68) But APIs that does not have save response as example display as normal ### Steps to reproduce 1. Save respose as example of some api 2. Update to lastest version `25.5.1` 3. Reopen the api that has saved as example ### Logs and Screenshots ```shell ``` ### Environment Production ### Hoppscotch Version Cloud ### Interceptor Native - Desktop App ### Browsers Affected _No response_ ### Operating System None ### Additional Information _No response_
kerem 2026-03-16 22:31:43 +03:00
Author
Owner

@kondohiroki commented on GitHub (Jun 2, 2025):

I got the same bug too.

<!-- gh-comment-id:2928821624 --> @kondohiroki commented on GitHub (Jun 2, 2025): I got the same bug too.
Author
Owner

@Kailegh commented on GitHub (Jun 2, 2025):

Same bug here, I have lost my saved requests and now I have a lot of Untitled GETs where I had mine
I also lost the enviroment variables I had saved:

Image

<!-- gh-comment-id:2929564937 --> @Kailegh commented on GitHub (Jun 2, 2025): Same bug here, I have lost my saved requests and now I have a lot of Untitled GETs where I had mine I also lost the enviroment variables I had saved: ![Image](https://github.com/user-attachments/assets/1033ee90-4af0-43d5-8843-0ee9c178801e)
Author
Owner

@zyict commented on GitHub (Jun 2, 2025):

Same here. Luckily I kept one open before the update, when it reopens I can save it again and the saved response is back too.

<!-- gh-comment-id:2930011758 --> @zyict commented on GitHub (Jun 2, 2025): Same here. Luckily I kept one open before the update, when it reopens I can save it again and the saved response is back too.
Author
Owner

@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:

Image

We got some exported collection(exported from Hoppscotch only, which has saved responses too) but when importing it, they are still showing Untitled requests, any thoughts on this?

<!-- gh-comment-id:2932894409 --> @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: ![Image](https://github.com/user-attachments/assets/998149a9-91f5-40fc-8bd6-343ebf1c7a65) We got some exported collection(exported from Hoppscotch only, which has saved responses too) but when importing it, they are still showing Untitled requests, any thoughts on this?
Author
Owner

@Kailegh commented on GitHub (Jun 3, 2025):

Investigating a bit, I think it has happend in all my resquests which had a response saved

<!-- gh-comment-id:2935003873 --> @Kailegh commented on GitHub (Jun 3, 2025): Investigating a bit, I think it has happend in all my resquests which had a response saved
Author
Owner

@rizkydoang commented on GitHub (Jun 4, 2025):

I got the same bug :)

<!-- gh-comment-id:2938593221 --> @rizkydoang commented on GitHub (Jun 4, 2025): I got the same bug :)
Author
Owner

@agu3rra commented on GitHub (Jun 5, 2025):

In case anyone wishes to download a previous version until this gets sorted, they are all available at https://github.com/hoppscotch/releases/releases.

<!-- gh-comment-id:2945873909 --> @agu3rra commented on GitHub (Jun 5, 2025): In case anyone wishes to download a previous version until this gets sorted, they are all available at https://github.com/hoppscotch/releases/releases.
Author
Owner

@AbhishekPrajapati commented on GitHub (Jun 6, 2025):

In case anyone wishes to download a previous version until this gets sorted, they are all available at https://github.com/hoppscotch/releases/releases.

Can we use older version for web version?

<!-- gh-comment-id:2948184132 --> @AbhishekPrajapati commented on GitHub (Jun 6, 2025): > In case anyone wishes to download a previous version until this gets sorted, they are all available at https://github.com/hoppscotch/releases/releases. Can we use older version for web version?
Author
Owner

@SezerOzyurek commented on GitHub (Jun 14, 2025):

I have no idea how to fix this issue, please help me. I need to deliver the endpoints to the mobile team, and right now I've lost all of them!

<!-- gh-comment-id:2972322410 --> @SezerOzyurek commented on GitHub (Jun 14, 2025): I have no idea how to fix this issue, please help me. I need to deliver the endpoints to the mobile team, and right now I've lost all of them!
Author
Owner

@imrinzzzz commented on GitHub (Jun 16, 2025):

I have no idea how to fix this issue, please help me. I need to deliver the endpoints to the mobile team, and right now I've lost all of them!

I recovered most of them by installing the older version. However, anything that was created in the newer version (25.5.1) could not be recovered.

<!-- gh-comment-id:2975051343 --> @imrinzzzz commented on GitHub (Jun 16, 2025): > I have no idea how to fix this issue, please help me. I need to deliver the endpoints to the mobile team, and right now I've lost all of them! I recovered most of them by installing the older version. However, anything that was created in the newer version (25.5.1) could not be recovered.
Author
Owner

@david-danneker commented on GitHub (Jun 16, 2025):

I have the same problem. All of my routes are now GET Untitled regardless of if they were GET/POST/PATCH/DELETE before the update. I'm assuming it was an update, at least the app told me it updated and now nothing works. Please fix ASAP. Thanks.

<!-- gh-comment-id:2975278551 --> @david-danneker commented on GitHub (Jun 16, 2025): I have the same problem. All of my routes are now `GET Untitled` regardless of if they were GET/POST/PATCH/DELETE before the update. I'm assuming it was an update, at least the app told me it updated and now nothing works. Please fix ASAP. Thanks.
Author
Owner

@nivedin commented on GitHub (Jun 16, 2025):

@imrinzzzz @david-danneker a new version 25.5.2 was released last week, can you confirm if you are on that version and if the issue still persist

<!-- gh-comment-id:2975291400 --> @nivedin commented on GitHub (Jun 16, 2025): @imrinzzzz @david-danneker a new version 25.5.2 was released last week, can you confirm if you are on that version and if the issue still persist
Author
Owner

@david-danneker commented on GitHub (Jun 16, 2025):

For more information, I'm using the app version 25.5.2 but it seems like the web interface has the same problem after it auto updates. If I export my routes all the data appears to still be there (good news), so it may be a problem with the reading the routes into the browser.

<!-- gh-comment-id:2975292471 --> @david-danneker commented on GitHub (Jun 16, 2025): For more information, I'm using the app version **25.5.2** but it seems like the web interface has the same problem after it auto updates. If I export my routes all the data appears to still be there (good news), so it may be a problem with the reading the routes into the browser.
Author
Owner

@david-danneker commented on GitHub (Jun 16, 2025):

@imrinzzzz @david-danneker a new version 25.5.2 was released last week, can you confirm if you are on that version and if the issue still persist

yes, I tried the new version this morning. It does not seem to help, Version 25.5.2 (20250613.104909).

<!-- gh-comment-id:2975294459 --> @david-danneker commented on GitHub (Jun 16, 2025): > [@imrinzzzz](https://github.com/imrinzzzz) [@david-danneker](https://github.com/david-danneker) a new version 25.5.2 was released last week, can you confirm if you are on that version and if the issue still persist yes, I tried the new version this morning. It does not seem to help, Version 25.5.2 (20250613.104909).
Author
Owner

@nivedin commented on GitHub (Jun 16, 2025):

@david-danneker are you facing this issue with personal or a shared workspace, and were you getting any error popup

<!-- gh-comment-id:2975296135 --> @nivedin commented on GitHub (Jun 16, 2025): @david-danneker are you facing this issue with personal or a shared workspace, and were you getting any error popup
Author
Owner

@david-danneker commented on GitHub (Jun 16, 2025):

@david-danneker are you facing this issue with personal or a shared workspace, and were you getting any error popup

with a shared workspace, on a self served server
error popup:

Image

<!-- gh-comment-id:2975299756 --> @david-danneker commented on GitHub (Jun 16, 2025): > [@david-danneker](https://github.com/david-danneker) are you facing this issue with personal or a shared workspace, and were you getting any error popup with a shared workspace, on a self served server error popup: ![Image](https://github.com/user-attachments/assets/31e2ce33-c9e0-474b-b9c4-27a80d0baa08)
Author
Owner

@nivedin commented on GitHub (Jun 16, 2025):

@david-danneker thank you for the information, if possible can you share the exported collection with the secrets removed this can help with the debugging

<!-- gh-comment-id:2975365017 --> @nivedin commented on GitHub (Jun 16, 2025): @david-danneker thank you for the information, if possible can you share the exported collection with the secrets removed this can help with the debugging
Author
Owner

@skarab42 commented on GitHub (Jun 16, 2025):

Experiencing the same bug here, in a self hosted instance with team workspace.

Here are some errors I've collected :

  • Login Complete page (console error) : Failed parsing persisted REST_TABS: {"lastActiveTabID" ... } (Can't share the full payload due to private data)

  • Online or local client (Snackbar on connexion) :

Image

  • Online client when connected :

Image

Image

<!-- gh-comment-id:2975380137 --> @skarab42 commented on GitHub (Jun 16, 2025): Experiencing the same bug here, in a self hosted instance with team workspace. Here are some errors I've collected : - Login Complete page (console error) : `Failed parsing persisted REST_TABS: {"lastActiveTabID" ... }` (Can't share the full payload due to private data) - Online or local client (Snackbar on connexion) : ![Image](https://github.com/user-attachments/assets/10ba7934-f549-4e7b-95ac-b52cd9ae5c24) - Online client when connected : ![Image](https://github.com/user-attachments/assets/04cec33b-91d0-40e1-930e-6827504b75a8) ![Image](https://github.com/user-attachments/assets/3a6af26f-fd22-40cb-8789-fe935735be74)
Author
Owner

@rdavaillaud commented on GitHub (Jun 16, 2025):

I've just refreshed the web version, CTRL+R the page, got the 2025.5.2, and all seems to be returned to normal, no more "schema validation failed" nor "Untitled" endpoint.

<!-- gh-comment-id:2975398585 --> @rdavaillaud commented on GitHub (Jun 16, 2025): I've just refreshed the web version, CTRL+R the page, got the 2025.5.2, and all seems to be returned to normal, no more "schema validation failed" nor "Untitled" endpoint.
Author
Owner

@david-danneker commented on GitHub (Jun 16, 2025):

@david-danneker thank you for the information, if possible can you share the exported collection with the secrets removed this can help with the debugging

No, unfortunately I can not.

I can only export the original data if I click on the import/export button on top of all the collections. If I try to export just one of the collections, the export also has only has GET Untitled routes listed. I can also tell you that some collections to no appear to have problems.

<!-- gh-comment-id:2975417511 --> @david-danneker commented on GitHub (Jun 16, 2025): > [@david-danneker](https://github.com/david-danneker) thank you for the information, if possible can you share the exported collection with the secrets removed this can help with the debugging No, unfortunately I can not. I can only export the original data if I click on the **import/export** button on top of all the collections. If I try to export just one of the collections, the export also has only has `GET Untitled` routes listed. I can also tell you that some collections to no appear to have problems.
Author
Owner

@nivedin commented on GitHub (Jun 16, 2025):

@david-danneker thank you for the information, can you share the value of persistence.v1:restTabs and persistence.v1:restTabs-backup

<!-- gh-comment-id:2975536078 --> @nivedin commented on GitHub (Jun 16, 2025): @david-danneker thank you for the information, can you share the value of `persistence.v1:restTabs` and `persistence.v1:restTabs-backup`
Author
Owner

@skarab42 commented on GitHub (Jun 16, 2025):

It seems to be fixed for me after reloading :)

<!-- gh-comment-id:2975619075 --> @skarab42 commented on GitHub (Jun 16, 2025): It seems to be fixed for me after reloading :)
Author
Owner

@david-danneker commented on GitHub (Jun 16, 2025):

@david-danneker thank you for the information, can you share the value of persistence.v1:restTabs and persistence.v1:restTabs-backup

I could not find those values in the app, however in the web interface they were not complete json files.

I deleted the -backup and removed all of my open tabs except the default unknown. The app seems to be working again after this modification.

The json in persistence.v1:restTabs ended abruptly at the HTTP 200 response param order, after 'Optional parameter*':

{
  "key": "order",
  "value": "",
  "active": true,
  "description": "*Optional parameter* that define the default sort order<br />\nPart of the `sort` capacity\n"
}
<!-- gh-comment-id:2975819430 --> @david-danneker commented on GitHub (Jun 16, 2025): > [@david-danneker](https://github.com/david-danneker) thank you for the information, can you share the value of `persistence.v1:restTabs` and `persistence.v1:restTabs-backup` I could not find those values in the app, however in the web interface they were not complete json files. I deleted the -backup and removed all of my open tabs except the default unknown. The app seems to be working again after this modification. The json in `persistence.v1:restTabs` ended abruptly at the HTTP 200 response param order, after 'Optional parameter*': ``` { "key": "order", "value": "", "active": true, "description": "*Optional parameter* that define the default sort order<br />\nPart of the `sort` capacity\n" } ```
Author
Owner

@nivedin commented on GitHub (Jun 16, 2025):

The app seems to be working again after this modification

Were you able to retrieve the team requests that were lost

The json in persistence.v1:restTabs ended abruptly at the HTTP 200 response param order, after 'Optional parameter*':

@david-danneker can you share the full persistence.v1:restTabs json that you are mentioning here

<!-- gh-comment-id:2976068405 --> @nivedin commented on GitHub (Jun 16, 2025): > The app seems to be working again after this modification Were you able to retrieve the team requests that were lost > The json in persistence.v1:restTabs ended abruptly at the HTTP 200 response param order, after 'Optional parameter*': @david-danneker can you share the full `persistence.v1:restTabs` json that you are mentioning here
Author
Owner

@david-danneker commented on GitHub (Jun 23, 2025):

I never lost any team data. It was always there just not visible.

Looks like it was a caching issue. The persistence.v1:restTabs was truncated and did not contain a full JSON file. I would imagine that when reading in the tabs data that was not complete causing the error, the application to not finish updating the routes data which is why all the routes were displayed with the default data. After deleting the cache in chrome and restarting the app everything seems to be working fine.

<!-- gh-comment-id:2994952311 --> @david-danneker commented on GitHub (Jun 23, 2025): I never lost any team data. It was always there just not visible. Looks like it was a caching issue. The `persistence.v1:restTabs` was truncated and did not contain a full JSON file. I would imagine that when reading in the tabs data that was not complete causing the error, the application to not finish updating the routes data which is why all the routes were displayed with the `default` data. After deleting the cache in chrome and restarting the app everything seems to be working fine.
Author
Owner

@nivedin commented on GitHub (Jul 2, 2025):

Closing this issue since it's been fixed in v2025.5.3

<!-- gh-comment-id:3026807274 --> @nivedin commented on GitHub (Jul 2, 2025): Closing this issue since it's been fixed in v2025.5.3
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/hoppscotch#1946
No description provided.