mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-26 01:06:00 +03:00
[GH-ISSUE #4008] [bug]: Selfhosted Generate Code ist Broken #1413
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#1413
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 @RaHehl on GitHub (Apr 25, 2024).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/4008
Is there an existing issue for this?
Current behavior
When i select generate code to see the request including headers that should be send it shows an error message "something went wrong"
and i get this in the browser console:
we are using 2024.3.1 selfhosted
Steps to reproduce
Click generate Code and you get the error
Environment
Production
Version
Self-hosted
@amk-dev commented on GitHub (Apr 25, 2024):
Hey can you give me a sample request to reproduce this behaviour. you can use hoppscotch export to get the request. usually errors like this can happen due to invalid data, can you check if your headers/json request contains any malformed data.
@RaHehl commented on GitHub (Apr 25, 2024):
@amk-dev this happens in my case even with https://echo.hoppscotch.io in incognito mode without login
@liyasthomas commented on GitHub (May 11, 2024):
Thanks for your patience and valuable feedback. This issue has been resolved in the latest release.
Closing this ticket as the fix is now available in the recent version. Please feel free to reach out if you have any other concerns.