mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-25 16:55:59 +03:00
[GH-ISSUE #5129] [bug]: pw.response.body parse json error #1952
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#1952
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 @ChenLuoi on GitHub (Jun 6, 2025).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5129
Originally assigned to: @AndrewBastin, @jamesgeorge007 on GitHub.
Is there an existing issue for this?
Current behavior
The output of pw.response.body in Tests, return a map object, but actually it's an array.
original response:

pw.response.body:

Steps to reproduce
Logs and Screenshots
Environment
Production
Hoppscotch Version
Self-hosted
Interceptor
Not Applicable - Issue not related to network requests
Browsers Affected
Chrome
Operating System
Windows
Additional Information
deploy with aio docker image hoppscotch/hoppscotch:2025.5.1
@RaHehl commented on GitHub (Jun 6, 2025):
+1
@jamesgeorge007 commented on GitHub (Jun 9, 2025):
Thanks for reporting. We'll be looking into it. In the meantime, you can opt out of the experimental scripting sandbox from
Settings > Experiments.@ChenLuoi commented on GitHub (Jun 10, 2025):
Thanks! Disable experimental scripting sandbox resolved it. Looking forward to a complete fix in the future.
@jamesgeorge007 commented on GitHub (Jun 13, 2025):
Hi, we've identified the root cause. This will be addressed in the upcoming patch release.
@jamesgeorge007 commented on GitHub (Jun 15, 2025):
This is now resolved in v2025.5.2.