mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-25 16:55:59 +03:00
[GH-ISSUE #5674] [bug]: Unable to open copied requests #2200
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#2200
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 @kishanr-prowork on GitHub (Dec 8, 2025).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5674
Is there an existing issue for this?
Platform
Desktop App
Browser
Chrome
Operating System
macOS
Bug Description
NOTE : Refreshed the hoppscotch window and killed the entire app and reopened too. still issue persists.
Deployment Type
Hoppscotch Cloud
Version
25.11.1
@Isuranga-2001 commented on GitHub (Dec 8, 2025):
I have the same problem. Also, can't open the requests which are imported.
Operating System
Windows 11
Platform
Desktop App
@dalirnet commented on GitHub (Dec 8, 2025):
I have the same problem. This issue is likely related to #5670.
Platform: Desktop App, Web App
Operating System: macOS
Browser: Safari
@AaronFortG commented on GitHub (Dec 11, 2025):
I experienced the same issue, when exporting from Postman and import to Hoppscotch I was not able to open the requests, but they appeared in the list.
Platform: Web App
Operating System: MacOS
Browser: Google Chrome
@jamesgeorge007 commented on GitHub (Dec 12, 2025):
Hi, apologies for the inconvenience. We've identified the root cause stemming from the BE implementation on the cloud offering, and a patch is being evaluated. Please track the further progress in #5670.
@jamesgeorge007 commented on GitHub (Dec 12, 2025):
The fix is now live. Please let us know if the issue persists.