mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-26 01:06:00 +03:00
[GH-ISSUE #4934] [bug]: Unable to save response body into file #1862
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#1862
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 @mak-42 on GitHub (Mar 25, 2025).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/4934
Originally assigned to: @CuriousCorrelation on GitHub.
Is there an existing issue for this?
Current behavior
Hoppscotch desktop application does not save binary response body into a file.
Steps to reproduce
The application does not save a file.
Logs and Screenshots
Environment
Production
Hoppscotch Version
Local
Interceptor
Not Applicable - Issue not related to network requests
Browsers Affected
No response
Operating System
Windows
Additional Information
Desktop v2025.2.3
@UyCode commented on GitHub (Mar 26, 2025):
same issue, the error from the api is:
Command plugin:fs|write_file not allowed by ACL@UyCode commented on GitHub (Mar 26, 2025):
I think the
fsplugin should have a permission scope:@jakfalter commented on GitHub (May 5, 2025):
We are experiencing the same issue with HS Desktop self-hosted on macOS (version 2025.3.0)
@CuriousCorrelation commented on GitHub (May 28, 2025):
Hi there, this should be fixed in release
v25.5.0-0. Please update to the latest version and let me know if you can confirm it's working for you!